Review or set up the process-related definitions that are available to the relevant solutions.
Name | Responsible | Description |
---|---|---|
Create flow |
Architect |
You can create a flow centrally and, at another time, assign it to a business process in the business processes hierarchy or use it as sub-flow in another flow. |
Create activity |
Architect |
You can create an activity on the Activity page and later add it to a flow. |
Set up objects |
Architect |
An object is a data object, document or deliverable such as an item, invoice, physical document or product. An object can consist of other objects. For example, a sales order contains sales lines. Each object can have named attributes (fields). Objects can represent, for example, inputs and outputs of processes and activities, or the content of messages exchanged internally or externally. Objects are also used to relate application specific objects from different applications to each other. |
Set up keywords |
Architect |
You can set up a hierarchy of user-defined keywords. You can use these keywords to classify business processes, flows, and activities. |
Set up process |
Architect |
You can set up general available process definitions that you can re-use within or over solutions. Each process can have several flows. For example, you can create a separate flow for each different scenario of a process. |
Set up applications |
Architect |
Create an application that can play a role in one of your solutions. |
Name | Responsible | Description |
---|---|---|
Create flow |
Architect |
You can create a flow centrally and, at another time, assign it to a business process in the business processes hierarchy or use it as sub-flow in another flow. |
Create activity |
Architect |
You can create an activity on the Activity page and later add it to a flow. |
Set up objects |
Architect |
An object is a data object, document or deliverable such as an item, invoice, physical document or product. An object can consist of other objects. For example, a sales order contains sales lines. Each object can have named attributes (fields). Objects can represent, for example, inputs and outputs of processes and activities, or the content of messages exchanged internally or externally. Objects are also used to relate application specific objects from different applications to each other. |
Set up keywords |
Architect |
You can set up a hierarchy of user-defined keywords. You can use these keywords to classify business processes, flows, and activities. |
Set up process |
Architect |
You can set up general available process definitions that you can re-use within or over solutions. Each process can have several flows. For example, you can create a separate flow for each different scenario of a process. |
Set up applications |
Architect |
Create an application that can play a role in one of your solutions. |
Related to | Notes |
---|---|
Review process definitions |
  |
Review definitions |
  |