Advanced Conditions Use Case

This topic will walk you through an advanced conditions use case in detail.

WonderWeb Inc. wants to use advanced conditions to determine who should approve their document before it is sent out for signatures. They follow the steps below to define who their approvers are and when their approval is required.

WonderWeb Inc. also wants Legal’s approval to be needed only when the draft is not generated from the template (i.e., a draft uploaded by a Sales user). They follow the steps below to check whether or not their draft document was generated from their draft template.

Customize Launch Form Questions

WonderWeb Inc. wants to use advanced conditions to determine who should approve their document before it is sent out for signatures. WonderWeb Inc. wants the CFO to approve if the value of the contract is greater than or equal to $10,000.

1. Click on the Workflow Designer tab and select the workflow configuration you want to modify. Click the Create tab.
2. Create two questions: Which team are you on? and Contract Value.
3. In the Properties and Conditions panel, click the plus sign > Add Condition.
4. Name the condition CFO Should Approve. Select the Contract Value form property, change the comparison to is greater than or equal to, and set the monetary amount to $10,000.
5. Click Add Rule. To create a condition that is true when both rules are met, select And. To create a condition that is true if either rule is met, select Or.
6. Select the Which team are you on? form question and enter a value.
7. Click the Review tab. Set a conditional approver based on the condition you just created.
8. Add a secondary approver that approves when the CFO should approve condition is not met.
9. Click Save.

Draft Generation Condition

WonderWeb Inc. wants to use advanced conditions to determine who should approve their document before it is sent out for signatures. WonderWeb Inc. also wants Legal’s approval to be needed only when the draft is not generated from the template (i.e., a draft uploaded by a Sales user).

The draft generation condition allows WonderWeb Inc. to check whether or not their draft document was generated from their draft template.

This is triggered when there are redlines on the document, as well as including any new document uploaded via the Update Document function, updated from a reply to Share Document, or through the Editor. (If a document changes via Edit Info, it will not trigger the condition since the document is still generated through the template.) A use case for this would be where Legal’s approval is needed only when the draft is not generated from the template.

1. Click on the Workflow Designer tab and select the workflow configuration you want to modify. Click the Create tab.
2. In the Properties and Conditions panel, click the plus sign > Add Condition.
3. Name the condition Legal Approval is Required.
4. In the Select a property or condition, select Draft Document.
5. Select not generated from template, and then click Save.
6. Click the Review tab, and then click Add Approver.
7. Click Use advanced conditions. A new condition displays.
8. Click the When dropdown and select the Legal Approval is Required condition.
9. When the workflow runs, the draft is generated from the template, though you can make edits during the Review stage. If you do not make any edits, there are not approvers for the review, and therefore the workflow will skip the review stage, and directly send out the signature requests. To prevent this, add another approver labeled Owner/Requestor and assign it to the owner of the workflow. If you edit the draft, approvals are automatically triggered.