The Folder Hierarchy
SimQ organizes agreement files into a logical hierarchy or “tree” for easy access. The users adds folders that correspond with the types of documents they might need in completing their agreement package. New folders can be added under existing folders to create different branch levels by clicking on the existing folder and then clicking add new folder. This will make the new folder a “branch” off of the existing folder.
The workflow of the application will follow the branch structure of the tree, moving from higher level branches to lowest level branches. In Agreement Manager, the user can change the folder type by right clicking on the folder and selecting Change Folder Type. Once a user selects a transaction folder from the dropdown, the folder becomes orange under the document tree. Every folder in the transaction tree must be set as a transaction folder and each folder can only contain one landing page or template.
Steps to Create a Transaction Folder
On the Folder Type window, by setting the folder type to a Transaction folder, the user can control all the variables they need to create a transaction.
- Transaction: the administrator can set up the kind of transaction by selecting it from the menu. This could range from a Card Services Web Application to a KYC Update.
- Theme: Allows a custom *.css file uploaded as a company asset to be referenced. This will allow you to apply a predefined stylesheet to your agreements. You can have one theme for your landing pages and another for your signing agreements.
- Publisher/Recipient Previous/Next: These allow you to control the behaviour of the previous/next buttons for the Publisher and Recipient(s). For instance if Publisher Next is set to 'Open Signing Package P' this will complete the landing page and open the linked signing template in publisher mode.
- Publisher/Recipient on Load WS: a web service can be called after the templates in the next transaction folder have been added.
Recursive Condition and Entry Conditions
Recursive Condition: The system keeps looking for examples that meet the criteria for that template type on the current folder level until the criteria isn’t met (an If/Else example). If the Recursive condition is met, then another set of all the templates in this transaction folder is added to the current Agreement.
Entry Condition: The Entry condition is set up on the landing page in Agreement Manager. If the Entry condition is met, then an instance of all the templates in this transaction folder is added to the current Agreement one time.
This must be written in the following style:
Field Name, Operator, Value
The Operator can take one of the following forms:
=, !=, <, <=, >, >=
Linking Transaction Folders to Landing Pages
Within a transaction folder, the user can set parameters that link the folders to other documents in the transaction tree. By opening a template inside the folder and opening the Signature and Form tools section for the button, the user matches the conditions set above with conditions in the actual document to create links.
For example, by adding a button to the document page and changing the field name to ‘AEXTransactionNext’, this tells the system what to look for when a user clicks this button.
Additional Transaction Options
Other commands for a button:
Using these commands creates ‘behind the scenes’ logic for all the templates a user can add/include in the transaction and links transaction template folders with landing pages to form signing agreement packages.
By adding form fields to an agreement through the Signature and Form Tools blade, combined with setting conditions with the AEXTransaction field name functions and Entry conditions on the Folder Type dropdown, the system follows a set of defined rules to link appropriate document packages for the user.