Conditions & Actions
Add your business rules here
UniServe processes a template using the conditions and actions defined for it.
Business rules in UniServe 360 are conditions or logic that control how specific parts of a template behave. They help you decide when, how, or what content should appear based on the input data.
For example, showing a “Payment Due” message only when the outstanding amount is greater than zero
Conditions
In UniServe 360, conditions are defined globally and can be called at any level (Document / Group / Page / Layer / Object) in the Template Hierarchy by defining actions.
Let's look at adding conditions.
To add a condition,
Go to Tools > Condition Manager. The Condition Definition wizard appears.
In the Available Conditions pane, click '+'. Enter the condition name and select the level (File/Level1)
Now, define the condition. In the Atomic Condition Definition wizard,
Give the condition a unique name
Select the source (simple object/complex object). Based on the source selected, its datatype is auto populated.
Select the operator (condition)
Then, select the destination type - value (Text) or the data object (Object) and specify accordingly.
Enable "Evaluate always" to check this condition every time.
Then, click Ok to add.
To know the available list of conditions, click here.
<<IMAGE>>
The defined condition is now available under "Available Conditions". Click it, the condition you defined is available in the Group1 along with the condition's expression preview.
<<IMAGE>>
To check with multiple conditions, you can define conditions(s) within the group by clicking '+'. Then select the operands (AND/OR/NOT). For example, to check a combination of two conditions or a single condition, define conditions to build an expression like this: [(Condition 1 AND Condition 2) OR (Condition 3)]
<<IMAGE>>
Similarly, you can check a group of conditions with another group using the required operands and you can add as many conditions as required.
<<IMAGE>>
After defining the condition, click View Data to view the sample data with the conditions applied.
Add all the business following these steps.
Actions
An action tells the platform what to do when (default/conditional) a condition is met. Actions change how an object appears or behaves in the template.
Actions can be defined at Document / Group / Page / Layer / Object
In UniServe 360, pre actions and post actions are part of the rule execution flow. They help you control when an action should run while the system processes the template.
Init - This is used to initialize a data base.
Pre Actions - These are run to prepare the object before it appears. They are used for:
Setting or modifying values before showing the object
Formatting or adjusting the object based on conditions
Example: Before displaying the account balance, you can format the number, add currency symbol, replace null values with "0.00", etc.
Also, we can add rows for a process complex object on Group-level pre actions.
Post Actions - These are run to perform follow-up tasks after the object appears. They are used for:
Updating other objects based on what was displayed
Triggering additional calculations or formatting
Example: After the transaction table is rendered, you can calculate and display the total debit/credit.
Let's look at defining an action at different levels:
Document Level:
Go to Settings > Distributive Options > Define Actions tab.
Action Type - Init If the template includes fetching data from an external data source, use "Init" action. Click '+', select the condition, and set it True/False as per the requirement. <<IMAGE>> Now, define the action to be performed. To define,
select the Action Type,
Define the parameters if required and
Execution Mode (Continue / Break)
<<IMAGE>>