Similar to the Process Automation content, when importing Live Process content, you are importing templates that need to be adjusted to your specific needs afterward. In a typical scenario, you will retrieve a process template, a decisions project, and a process visibility project. These artifacts might be complemented by additional material like SAP Cloud Application Programming Model applications. Each of these artifact types can be adjusted to your needs.
Once you have added a Live Process from the Store, it will appear in your projects overview. From here, you can access the process.
Within the process, you can see all available artifacts. Usually it includes a Process Template, Decisions, and a Visibility Scenario.
- Process Template
- Consists of process steps and a preconfigured process variant, which represents a minimum viable process.
- Can be used to configure any number of so called process variants. Process variants represent individual use cases of a process (for example, when the total request amount is lower than 10,000 Euro, only one approval is required but when the total request amount is higher than 10,000 Euro, two approvals are required. (these will be explained in more detail soon).
- Decision
- Contains business rules that are relevant for the process flow. For example, Determine Process Variant contains a rule that determines the process variant to be executed, depending on the request data (for example, process variant 1 when the total request amount is lower than 10,000 Euro, process variant 2 when the total request amount is higher than 10,000 Euro).
- Is configurable based on business requirements.
- Visibility Scenario
- Contains a preconfigured Process Visibility Scenario for the underlying process template.
- Can be adjusted based on business requirements.
The dropdown on the Process Template reveals all existing process variants. They can be accessed by selection.
A no-code editor lets you configure the process variants from the process template.
A process template consists of process steps and a preconfigured process variant, which represents a minimum viable process. The delivered process steps can be used to configure custom process variants from the preconfigured process variant.
The Capital Expenditure Approval Live Process, for example, contains a preconfigured process variant with only one approval step for a local manager. Via the delivered process steps, it is possible to configure custom process variants that contain additional approval steps.
Process Variants - Concept
A delivered process template contains process steps and a preconfigured process variant. Process steps act as building blocks that can be put together in a modular way into a process. Each step can have constraints. These constraints specify the minimum and maximum number of occurrences of a process step within a process variant. Also, the position of a process step within a process variant can be subject to constraints. Thus, certain steps can only be placed at the beginning or the end of a process.
Any number of variants can be configured within the specified conditions. Process templates and the configuration of process variants provide a framework for business process experts within which they can flexibly adapt to changing business requirements with no code. Also, it hides the complexity of the underlying processes. These might contain many more steps, conditions, or flow controls that are actually visible in the modular process variants.
The available steps can be added to the process variant via drag and drop. When your process variant is finished, you need to save and activate it.
The available steps can be added to the process variant via drag and drop. When your process variant is finished, you need to save and activate it.