Rules Usage
Rules Usage can encompass the automation of workflows within Eccentex AppBase. This involves defining rules that dictate the sequence of actions or tasks to be performed when specific conditions are met. For example, when a new customer inquiry is received, a rule can trigger an automated process that assigns it to the appropriate team member, sends an acknowledgment email, and sets a follow-up reminder.
Eccentex AppBase allows users to define custom business logic using rules. This means that unique business processes and decision-making criteria can be encoded into rules, ensuring that the platform adapts to an organization's specific needs.
List of Usages
The following table lists available rule functions and their meanings.
| Rule Usage | Description |
|---|---|
| Bookmark | This rule type is used for letter generation, email generation, or to generate some other type of content. For this type, you need a template that references a bookmark. A template contains standard placeholders. Placeholders are areas that a system must fill with some additional information. A placeholder is then linked to the bookmark. You define a bookmark name and link it to a rule. The rule specifies how to extract the data from the system. |
Business Constraint | This rule allows you to define some business constraints. For example, you could say that this account must contain a minimum of 10,000 dollars, or this account must have at least two customers, or this account must exist in some area or zip code. A constraint is always either True or False. The system, at runtime, calculates whether the condition is true or false. The result is always Boolean. |
Business Event | Rules that interact with background processing events. |
Business Object Attribute Constraint | Same as for Business Object but applies to attributes. |
Business Object Create | Most commonly used. Creates a business object. |
Business Object Delete | Deletes a business object. |
Business Object Insert | Inserts a business object |
Business Object Update | Updates a business object |
Business Relation Constraint | Constrains a business Relationship. For example, you might want a Customer-to-account relationship to contain no more than five accounts. |
Business Relation Link | Creates a link between business objects |
Business Relation Unlink | Removes the link between business objects |
Capture | This rule is used for processing data that comes from outside the system. It specifies how you want to capture and bring data into the system. |
Empty | Empty rule type |
Field Calculation | This means you can define the logic for a specific field value calculation. |
General | This is a general configurable rule type |
Scheduled Task | Scheduled tasks inside a task scheduler will use this rule. For example, suppose a case must be processed within 30 days of a service agreement. You can schedule a task that iterates through all cases and locates any cases not processed within 30 days. If not processed within the time period, the system might send an email or other communication. |
Workflow Activity Finalized Event | Use this rule to create functionality when a Workflow Activity Finalize event is fired. This event occurs when a work item leaves the activity. |
Workflow Activity Initialized Event | Use this rule to create functionality when a Workflow Activity Initialize event is fired. This event occurs when a work item arrives to the activity. |
Workflow Activity Routing Event | Use this rule to create functionality that executes when a work item moves from one Activity to another. |
Workflow Activity Validate Send | Use this rule to create functionality that determines and checks the criteria needed to move the work item from one Activity to another. |
Workflow Create Workitem | Use this rule to create functionality that executes when a work item is created. |
Workflow Delete Workitem | Use this rule to create functionality that executes when a work item is deleted. |
Workflow Finalize | Use this rule to create functionality that executes when Workflow for a specific work item is completed. |
Workflow Initialize | Use this rule to create functionality that executes when Workflow for a specific work item is initialized. |
Workflow Load Workitem | Use this rule to create functionality that executes when a work item is loaded for processing. |
Workflow Transition Send | Use this rule to create functionality when a Workflow Transition event is fired. This event occurs when the work item is sent from one activity to another through a specific transition. |
Workflow Transition Validate Send | Use this rule to create functionality that determines and checks the criteria needed to move a work item from one Activity to another through the selected Transition. |
Workflow Update Workitem | Use this rule to create functionality that executes when a user or workflow updates a work item. |