Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
76:releasenotes [2021/02/23 19:34] – emr | 76:releasenotes [2024/02/15 00:00] (current) – external edit 127.0.0.1 | ||
---|---|---|---|
Line 23: | Line 23: | ||
Any user can participate in a review or approval step. | Any user can participate in a review or approval step. | ||
- | If your system has been upgraded from a previous Stages version and does not contain any pre-defined automations yet, you can download //**a sample automation | + | A sample automation |
[[https:// | [[https:// | ||
Line 36: | Line 36: | ||
All users can see who reviewed and approved a process, even in complex process landscapes using multiple layers of process modules. | All users can see who reviewed and approved a process, even in complex process landscapes using multiple layers of process modules. | ||
+ | |||
+ | See [[: | ||
===== Process Execution* ===== | ===== Process Execution* ===== | ||
- | To assure that processes are actually applied in practice, the defined process activities need to be planned, executed, and monitored. The latter typically happens in task management tools (also known as Application | + | To assure that processes are actually applied in practice, the defined process activities need to be planned, executed and monitored. The latter typically happens in task management tools (also known as Application |
With Stages version 7.6, modelers can extend the processes that should be executed with the new “activator” elements and deploy the resulting executable models directly into those task management tools. | With Stages version 7.6, modelers can extend the processes that should be executed with the new “activator” elements and deploy the resulting executable models directly into those task management tools. | ||
- | TODO: process execution infographic | + | [[https:// |
In contrast to BPMN and similar modeling techniques, the business process logic can be separated from the technical task execution and platform details. With the Stages approach, the same process can be executed in Jira in one project and IBM Engineering Workflow Management in a different project, each with its individual tailoring. Both processes can be derived from the same organizational standard process, which assures compliance with all required standards and reference models. | In contrast to BPMN and similar modeling techniques, the business process logic can be separated from the technical task execution and platform details. With the Stages approach, the same process can be executed in Jira in one project and IBM Engineering Workflow Management in a different project, each with its individual tailoring. Both processes can be derived from the same organizational standard process, which assures compliance with all required standards and reference models. | ||
- | Stages comes with different predefined activator types. The " | + | Stages comes with different predefined activator types. The " |
+ | |||
+ | See [[: | ||
===== Workspace Collections ===== | ===== Workspace Collections ===== | ||
Line 65: | Line 69: | ||
===== Direct Compliance Mapping ===== | ===== Direct Compliance Mapping ===== | ||
- | Compliance mappings to reference models and standards is normally started via '' | + | Compliance mappings to reference models and standards is normally started via '' |
[[: | [[: | ||
Line 73: | Line 77: | ||
When importing a process module into a workspace, the modeler can now choose if future updates of the imported module should be pushable into the Working Version. To push a process module into all workspaces that have the module imported and push-update enabled, go to '' | When importing a process module into a workspace, the modeler can now choose if future updates of the imported module should be pushable into the Working Version. To push a process module into all workspaces that have the module imported and push-update enabled, go to '' | ||
- | {{ https:// | + | [[https:// |
When importing modules that have interfaces with each other, the import of the first module always causes warnings because of missing interfaces. With the new refresh update, the modules with warnings can be updated to the same version again. This should resolve all interfaces and result in a warning-free process landscape. | When importing modules that have interfaces with each other, the import of the first module always causes warnings because of missing interfaces. With the new refresh update, the modules with warnings can be updated to the same version again. This should resolve all interfaces and result in a warning-free process landscape. | ||
- | ===== New Style for Headings and Tables ===== | + | [[: |
- | + | ||
- | The default headings and table styles in the description editor have been updated | + | |
===== Other Changes ===== | ===== Other Changes ===== | ||
+ | |||
+ | The default table style in the description editor has been updated to include borders for more clarity and easier process understanding. | ||
A banner can be configured to inform users of sensitive environments about restrictions, | A banner can be configured to inform users of sensitive environments about restrictions, | ||
- | Project | + | Project-scope attributes will be imported |
Encrypted SAML Assertions are now supported for Single Sign On. | Encrypted SAML Assertions are now supported for Single Sign On. | ||
- | The maximum number of parallel background operations can now be configured via the new '' | + | ===== Start without Root Privileges on Linux ===== |
- | + | ||
- | ==== Start without Root Privileges on Linux ==== | + | |
Normally Stages is started by the " | Normally Stages is started by the " |