1. Navigate to Processes > Processes
2. Click Add New Process. A summary of the release management (RM) flow will appear, click OK close.
3. Enter process details and click Save.
| Field | Description |
| Process name | The title of the process. |
| Description | The introduction of the process. This appears at the process start point. |
| External reference identifier | An identification code/number for the item. This can be used if the item is being migrated from a different system or if a system of identifiers is required. This field is optional. |
| Relevant documents | Documents that are related to the process. These documents must first be uploaded to the Centro ASSIST web app. |
| Managing Business Unit | The Business Unit that needs access to this piece of content. |
| Related Stakeholders | Stakeholders responsible for the process. |
| Governing Obligations | Regulations related to the process. |
| Governing policies | Policies or policy sections related to the process. |
| Governing regulations | Regulations related to the process. |
| Related risks | Risks related to the process (only applicable for customers with risks and controls enabled). |
| Related controls | Controls related to the process (only applicable for customers with risks and controls enabled). |
| Summary | This is the short description that appears in the browsing menu. |
| Roles this is relevant to | Roles that have duties within the process. |
| Required reading | Tick this box to make this item required reading for all roles to which the item is relevant. |
| Category | The group to which the process belongs. |
| Keywords for 'Search' | Keywords that, when searched in the Centro web app, will make the item come up in search results. |
| Remove from view |
Tick the box to hide the item. This will make the item only visible to users with Administrator permissions. Hidden items will:
|
4. The process map editing will appear. Click on the plus icon to create a new step.
5. Add step details. Name and Performed by fields are the only mandatory fields. All other fields are optional.
| Field | Description |
| Name | The title of the process step, outlining the main action. |
| Auto step number | The number of the step within the process map sequence. This is generated automatically, but you can click Convert to Manual to enter custom step numbers. |
| Description | Details about the process step, including any additional relevant information. |
| Performed by | The role that is responsible for performing the step. |
| Interacting with | Any other role that interacts with the main performing role to complete the step. |
| Work instructions | Work instructions related to the process step. |
| Documents used in step | Documents required to complete the step (or any other relevant documents). |
| Systems used in step | Systems used to perform the step, for example, specific CRM or HR tools. |
| Governing Obligations | Legal obligations related to the process step. |
| Governing Policies | Policies that influence, inform or govern the step. |
| Governing Regulations | Regulations that influence, inform or govern the step. |
| Related Risks | Risks related to the step. |
| Related Controls | Controls for mitigating risks related to the step. |
6. Click Save
| Tip |
| As you continue creating your process, you can preview your process map on the right-hand side of your screen. |
7. Continue steps 5 and 6 for each process step. If your process includes a Gateway (also known as a Decision Point), click on the plus icon and select Gateway.
8. Write the title for the Gateway, ideally this should be text to prompt the performer to make a selection between different options. Select the Gateway type and click Save. The description below provides definitions and examples.
| Type | Description |
| Exclusive | An exclusive gateway is a decision point where the process can follow only one path. When the workflow reaches it, each path is checked in order, and the first path with a true condition is the one the process follows. |
| Inclusive | An inclusive gateway specifies that one or more of the available paths will be taken. They could all be taken, or only one of them. |
| Parallel | Parallel gateways let a process run multiple activities at the same time or wait for them to finish. As a fork, they send the flow down all outgoing paths in parallel. As a join, they pause the process until all incoming paths are completed. A single parallel gateway can do both, first waiting for all inputs, then splitting into multiple parallel paths. |
| Tip |
| To connect your Gateway, create all your Process Steps and Gateways first, then double click the gateway you created and change the path under Gateway Choices. |
9. Once you have created your process, click Send for Review. This initiates the Release Management Process.
10. Provide a summary of the process and click Send for Review.
11. Approve the process as per the standard Release Management process.