Change Requests

For companies, it's important to manage which users can publish changes or deploy releases. GoRules BRMS allows you to configure approval workflows to ensure that changes are reviewed and authorized by different groups before being deployed. The system keeps track of approvals through Change Requests, providing a structured audit trail.

Change Requests are available in the two key touchpoints:

• Decision Model Change Requests: Manage requests to publish or unpublish decision model versions.

• Release Deployment Change Requests: Control and track the deployment of releases to different environments.

Configuring Approvers

By default, new projects have approvals turned off. To enable approvals, navigate to:

Settings > General > Protection Rules, and update the approval settings.

The following approval options are available:

• None: Publishing/unpublishing of decision versions is allowed without approvals.
• None (Create Request): No approvals are required, but a pending Change Request is created for final check.
• Require: any: Any user from the approval groups can approve the Change Request. Once approved by at least one user, deployment can proceed.
• Require: 1 per group: At least one user from each listed group must approve before deployment.

After configuring approvers, click Update.

Configuring Approvals for Environments

For environment deployments, a similar approval process applies. Navigate to Environments > Edit Environment to access the approval configuration menu. Each environment is separately managed and configured.

---

Creating a Change Request

When an approval workflow has been configured, by publishing or unpublishing decisions or deploying/undeploying releases, Change Requests will automatically be created.

Change Requests act as safeguards for tracking, approving, and publishing rule changes. Each Change Request provides a structured overview similar to GitHub, including:

• Overview: Tracks who approved, unapproved, commented, or requested changes. Shows pending groups, approval mode, and list of approvers.

• Changes: Displays differences between versions of decision models or releases. This will show a visual comparison of the version you're requesting relative to the version deployed at the time the Change Request was created.

Note: Only one pending Change Request can exist per single decision model or per environment at a time. To create a new one, the current request must be resolved, canceled or rejected.

---

Managing Change Requests

Once a Change Request is created, it will appear under the Requests menu.

Note: You can also access Decision Change Requests in the Decisions/Rules list, where a "Needs Review" label will appear next to decisions with pending publishing/unpublishing requests.

• If all required approvers click Approve, the Change Request status updates to allow final completion.
• Any approver can also unapprove if necessary.
• Approvers can add and edit comments within the request.
• If an approver clicks Reject, the Change Request will be marked as rejected, and a new request must be created for further progress.

Important: Users cannot approve their own Change Requests. If an approval user is part of multiple groups in the approval list, their approval counts across all groups.

📘

Any user can Complete Change Request after it has been approved

---

Canceling Change Requests

If a Change Request is no longer needed, it can be canceled at any time, even after receiving approvals. To cancel:

1. Select the Change Request.
2. Click Cancel Request at the bottom of the overview page.

---

By implementing Change Requests in GoRules BRMS projects, companies can ensure that all changes are properly reviewed, approved, and deployed with confidence, maintaining governance and auditability throughout the process.