Configuring Field Linkage Rules

By configuring linkage rules for template fillable fields, you can achieve logical associations between multiple input contents. For example, based on a specific radio button or dropdown result, you can dynamically control the show/hide or required/optional status of other fillable fields. This feature can greatly simplify the contract filling process, reduce invalid inputs, and improve standardization.

Configuring Field Linkage Rules

1. Create Linkage Rules

   On the contract template settings page, select the field you want to use as the trigger condition, and click “Create Rule” in the right-hand properties panel.

   

2. Set Trigger Conditions

   Configure this in the “When the following prerequisites are met” section. You can set the trigger condition to a specific “Option Value” or to other “Field Values” of the same type.

   

3. Set Linkage Results

   In the “Trigger the following linkage” section, select the action to be executed after triggering (Show, Hide, Set as Required, Set as Optional), and select the affected fields. You can add multiple execution actions to control the changes of multiple fields at once.

4. Validate and Save Rules

   If conflicting actions are configured under the same trigger condition (for example, setting the same field to both Hide and Show, or Hide and Required simultaneously), the system will automatically prompt a rule conflict. In this case, please adjust your configuration according to the prompt.

Linkage Effects on the Filling Page

1. Controlled Prompts and Filling Guidance

   When a signer enters the page to fill it out, fields controlled by linkage rules will display a tooltip upon mouse hover or selection, informing the user which prerequisite fields are affecting it.

   

2. Actual Effects of Linkage Hiding

   After the signer completes the relevant trigger fields, the system will automatically show or hide the corresponding items. When the contract is finally submitted, the content of hidden fields will not be rendered into the generated contract document, nor will mandatory validation be performed on that item (however, previously entered data will be retained in the records for easy tracing).

Frequently Asked Questions (FAQ)

1. During template configuration, I only set a linkage rule on one field. Why do other fields have the same rule?

   This is because these fields are merged for filling. When multiple fields are merged, their input values on the filling page are identical, thus triggering the same linkage rules. During configuration, pay attention to whether multiple fields are part of a merged fill. Check if the trigger rules still meet expectations when new fields join or historical fields leave the merged fill group.

2. During template configuration, why does the linkage rule act abnormally after the name of an option in a dropdown field changes?

   When a dropdown field’s value equaling a specific option is set as a trigger rule, and the option name is subsequently adjusted, the option condition in the linkage rule will not automatically update. You will need to reselect and configure it again.

3. Why does the execution result on the filling page not match the configured rules?

   The execution of field linkage rules follows these principles:

   • First, when the trigger conditions are not met, the field’s behavior and status will revert to the template’s default settings.
   • Second, there is an execution priority sequence for linkage rules. When a field is triggered by multiple rules, the later rules in the sequence (those executed last) have a higher priority.

   Example: As shown in the figure, when [City of Responsibility] equals [Service Region], [Explanation of Breach of Contract] is shown. Does this mean that when the values of these two fields are not equal, [Explanation of Breach of Contract] should be hidden? Not exactly. According to the implementation principles, when the condition is not met, the field reverts to the template’s default settings. Since the field is set to show by default in the template configuration, it will still be shown and will not automatically change to its opposite status.

   Solution: If you need strict negation logic, you can add an additional dedicated configuration in the linkage rules: “When [City of Responsibility] does not equal [Service Region], [Explanation of Breach of Contract] is hidden.”

   

4. Why do linkage rules not take effect when using bulk send with templates and pre-filling content via an Excel sheet?

   Because API interface filling and Excel pre-filling do not currently support field linkage rules. Currently, linkage rules are only triggered during manual page filling. In scenarios of bulk sending or API filling, please ensure the accuracy and completeness of the pre-filled content yourself.