Starting with version 1.14, customize or recreate the DevOps Model Change
Request flow based on your requirements using a flow or a script.
In the DevOps Model Change Request flow, the state of step execution is changed based on the
change approval. However, you can customize or recreate this flow based on your requirements.
After the change request state is moved to approve, canceled, or rejected (either manually or
by using a change policy), call the Update state of step execution based on change
approval
Flow Designer action to update the State field of step
execution record.
You can use either a flow or a script to call the action.
Calling the Flow Designer action using a flow
Calling the Update state of step execution based on change approval
Flow Designer action is required to update the state of the step execution record
according to the approval field in the change request record.
This action serves as a trigger for the Change Control Callback flow,
which is used to notify the change decision to the orchestration tool.
Calling the Flow Designer action using a script
Method to call the
Flow Designer action from a
script:
sn_fd.FlowAPI.executeAction('sn_devops.name_of_FD_action’, inputs);
Default Change Handler subflow
Use the Default Change Handler subflow to populate these change request fields with default
values.
- Requested by
- Justification
- Implementation Plan
- Backout plan
- Test Plan
- Short Description
- Description
- Start Date
- End Date
- Risk Impact Analysis
The Default Change Handler subflow overrides the field values that were populated using a
template while creating the change request record.
If desired, you can write a custom subflow in place of this flow by modifying the
[sn_devops.change_request_handler_subflow]
DevOps property.
DevOps Demo Change Automation flow
When demo data is installed, Flow Designer DevOps Demo Change
Automation flow is available where normal type change requests can be
auto-approved based on the decision policies.
As a part of demo data, the decision policies available are:
- Low risk auto approval policy, where the failed test count is zero .
- High risk manual approval policy, where the failed test count is greater than zero .
As a part of the demo flow, Flow Designer actions available are:
- DevOps Set Change Window
Action used to set the change request start date.
- Get Change Policy User/Group
Action used to fetch the user/group based on the change
request approval policy.
- DevOps Create Auto Approval Record
Action used by the user to create
Auto-Approve/Auto-Reject approval records.
