Decision Overview
Getting Started: Before building decisions, ensure you have been onboarded to OPUS.
See Quick Start for Administrators or Quick Start for Developers to get access.
A Decision defines a set of rules and logic used to evaluate the input and return an output. It is typically represented by nodes like Decision Table, Expression, Function, Switch or reference to existing Decision. With that, each decision service could reflect rules in a structured and reusable manner.
Important: Decisions have a maximum nesting depth of 5 levels. This means a decision can reference other decisions up to 5 levels deep to prevent circular dependencies and ensure optimal performance.
Before creating your first decision, familiarise with the Decision Editor interface and its nodes. Understanding the drag-and-drop interface, node palette, and test panel will help you build decisions more effectively.
Follow these steps to build and release your decision:
Creation
- Create New Decision - Add a new decision to your project
- Configure Decision Input - Set up the decision entry point
- Configure Decision Nodes - Set up decision logic nodes
Testing
- Test Decision - Test with sample data before testing in staging environment
- Create Regression Test - Create and run test cases in staging environment
- Monitor Execution - Track and debug executed decisions
Life Cycle Management
- Publish Changes - Commit and publish your decision
- Perform Regression Test - Validate changes with all the other decisions
- Release Management - Create versioned releases
- Execution - Execute decision via API endpoints
Decision Editor
The Editor is a Drag and Drop interface for modeling rules within a Decision. Below is an overview of the main components, as annotated in the accompanying screenshot.
Decision Title The title of the current Decision being modeled.
Status of the Decision Indicates the current status.
| Status | Description |
|---|---|
| Draft | The Decision has not been committed, with or without new changes. |
| Published | The Decision has been published, and no new changes have been made. |
Decision Version and Locking:
- When created, decisions are automatically assigned a Draft version
- Any changes saved to the decision will override the existing Draft version
- Once saved, the decision becomes locked by the user who made the last update
- Only that user can continue making changes until the decision is Published
Decision Test Panel Opens the test panel to test your decision before release. See Test Decision for details.
Save Saves the decision as a draft, allowing users to continue working on it later.
Drag and Drop Modeling Panel This is the main canvas where you drag and drop nodes to build your decision.
Remember to link the nodes to ensure the model functions correctly.
- Add Node Opens the node palette where you can search and select rule nodes to add to your decision. Each node type serves a specific purpose. See Configure Decision Nodes for details on all available node types.
Next Steps
Ready to start building? Begin with step 1:
Create New Decision - Add a new decision to your project and start building your decision service with the drag-and-drop interface.
