|
Workflow is a mechanism developed by OneDealer development team and it is based in the machine state model.
OneDealer's workflow engine is a generic mechanism that only knows States and Transitions.
States
State is the current step of the workflow process and it has the following configuration:
- State Description
- To which workflow belongs to
- If it is initial or final state
- Notification configuration
- and some more
Transitions
Transition is the execution process from one state to another state. During the transition it can be displayed custom pages for user interaction or any automated process, e.g. to send a notification. Transition has the following basic configuration:
- From State
- To State
- Transition Description
- To which workflow belongs
- What page to open for user interaction. We call them Transition Required Data ( optional)
- Execution of automated process. We call them External Function (optional)
- Notification (optional)
- Transition Validation
Configuration
Workflow configuration is stored in several database tables and it is fully customizable by end users with a very powerful workflow editor.
Image of Workflow Editor
Workflow Editor - Product Documentation
You can read more about the workflow editor in the following page Workflow Setup
Refactoring
The following Workflow tools have been refactored from version 1.69 and 1.70 and after. This refactoring consists of removing these tools from the DB and the relevant tables and add them directly into the code.
- 1.4.1 Workflow Validations (version 2.70)
- 1.4.2 Workflow Approvals (version 2.70)
- 1.4.3 Workflow External Functions (version 2.69)
- 1.4.4 Workflow Transition Required Views (version 2.69)
- 1.4.5 Workflow Types (version 2.70)
- 1.4.6 Inquiry Interest Types (version 2.70)
Related Feature: ODP-4721 - Getting issue details... STATUS
Add Comment