Skip to main content

Summary of Changes for new Publish

Add a summary of changes when publishing a process or value stream — what it records, where it appears, and the company setting that makes it compulsory.

Written by Hylet Pistorius

As a stakeholder in a process or value stream, you can add a summary of changes when publishing for the first time or publishing again after changes.

To add a summary of changes, follow the normal publishing steps. Click on the request approval or publish button in the actions tab of the diagram content menu. A pop up will appear for you to add a summary of changes to the version to ensure that changes are tracked. By default this is optional. See screenshots below.

When an approver opens the approval task, they will see the summary of changes in the pop up that appears. The approver will then have full access to the new information before choosing to either decline or approve the approval request. If no information has been added, then it will reflect 'No changes recorded' on the approval task pop up.

Once the process has been published, the summary of changes can be found under the history tab, below the version number the changes belong to. If no information was added nothing will be reflected under the version.

Requiring a summary of changes

Administrators can make the summary of changes compulsory for the whole company using the Require Summary of change on Publish company setting. When it is enabled, users must enter a summary before the save or publish completes — an empty or whitespace-only summary is rejected.

The setting is switched off by default and does not retro-fit historical change log entries.


Note

  • The summary of changes text field has a character limit of 500.

Did this answer your question?