Skip to main content
Mitratech Success Center

Client Support Center

Need help? Click a product group below to select your application and get access to knowledge articles, webinars, training content, and release notes or to contact our support team.

Authorized users - log in to create a ticket, view tickets status and check your success plan details.

 

Relationship Conditions

Learn how to configure relationships in TAP.

 

The Conditions property is a relationship-level property that lets you establish the condition rules under which a relationship is valid when two or more relationships are associated with a workflow stage. When multiple relationships exist for a workflow stage, one relationship is designated as the default relationship. The default relationship is considered valid when all other conditional relationships are invalid. The Conditions property cannot be applied to the default relationship.

Default and Conditions are used to create routing rules on a relationships following stage submission. If there is only one relationship following a stage, it will always be the default relationship and will not require any conditions. However, if there are multiple relationships which could be triggered after stage submit then one of those relationships will be the default, and the others will require conditions to be added. Users can select which relationship they would like to be the default by selecting that relationship and then clicking the default property. All other relationships must then have conditions added. This can be done by selecting the relationship and then clicking on the conditions property. Relationship conditions are configured in a similar way to stage conditions. The only difference is that users do not need to specify which fields are being acted on, since the relationship is what is being acted on.

When a workflow routes after a stage is submitted, it will always proceed down the conditional relationship which matches the values entered in the form. If no relationship conditions are met exactly, then it will proceed down the default relationship.

Note: Users should make sure that all relationship conditionals connected to a stage are mutually exclusive and that multiple conditions cannot be met at the same time. Otherwise, there could be unexpected routing.

To configure a condition rule for a relationship:

relationship conditions.PNG

  1. Select the workflow relationship for which you wish to configure a notification.
  2. Click the clipboard_ee9b946ea92d0d6a00f92e07d4bcc9d38.pngConditions button in the Workflow Page toolbar.
    • The Relationship conditions dialog displays.
    • The Relationship conditions dialog shows a list of all currently configured conditions for the relationship.
       
  3. Click the Add new condition rule button to display the condition entry fields.
  4. Select the form field on which to base the condition from the first Please select menu.
     
  5. Select the matching criteria for the condition from the second please select menu:
    • Equal to - the condition will be valid when the content of the form field is an exact match to the value specified
    • Not equal to - the condition will be valid when the content of the form field is not an exact match to the value specified
    • Contains - the condition will be valid when the content of the form field includes the specified value anywhere in the field
    • Does not contain - the condition will be valid when the content of the form field does not include the specified value anywhere in the field
    • Filled - the condition will be valid when the form field does contain a value (is filled)
    • Not filled - the condition will be valid when the form field does not contain a value (is empty)
       
  6. Specify the term against which the matching criteria will be applied.
    • Select the desired value from the drop-down menu, or, enter the desired value in the text box, as applicable.

      NOTE

      When a matching criteria of Filled or Not filled is selected, term options are not applicable.

  7. To add another rule to the condition, click the Add new condition rule button.
    • The Conditions dialog refreshes to display a new "select field" menu.
    • Choose the Boolean operator to be applied between the rules.
      • Select AND if both rules must be met to satisfy the condition.
      • Select OR if either rule must be met to satisfy the condition.
      • Repeat steps 4 through 6 to specify the conditions for the new rule.
      • Repeat step 7 to add additional rules to the condition, as desired.
         
  8. When all necessary values for the condition rule have been specified, click the Save button to save the rule.

 

To save a condition template:

 

NOTE

Condition templates let you use a previously created condition rule as the basis for creating a new condition. Condition templates are "workflow-specific,"  and are available only for the workflow to which they were saved.

To save a condition template, create and save a condition as described above, then click the Save as Template button to save the current condition rule as a template. Once a template has been saved, it can be accessed and modified to create a new condition for any stage in the active workflow.
 

To delete a condition rule:

  1. Select the workflow relationship for which you wish to configure a notification.
  2. Click the clipboard_e7085eb410be2d773b3ba0a3ed9264089.pngConditions button in the Workflow Page toolbar.
    • The Relationship conditions dialog displays.
    • The Relationship conditions dialog shows a list of all currently configured conditions for the relationship.
       
  3. Click the TAP - Setting Conditions Relationship (image 3).jpg icon for the condition rule you wish to delete.
    • The Relationship conditions dialog refreshes with the selected condition rule (and associated logical operator, where applicable) removed from the list

Use Case

  • Routing workflows based on values entered within a form.

  • Routing workflows after a eSignature step based on document status.

  • Routing conditional parallels based on values entered within a form.

  • Was this article helpful?