The GuardRails team has been diligently monitoring your feedback. As we introduce new features to keep your GuardRails experience smooth, we will update the below list and denote what are fixes or new features.
GuardRails Release Notes
March 31, 2025
This minor release of GuardRails includes numerous new features and enhancements designed to make user debugging easier and faster. Please review the release notes carefully as some changes may affect some customizations you may have configured for GuardRails.
New Additions
- Additional Alert Automations: Custom configurations that are reverted will check against definitions and update the corresponding alert. Deleted records from update sets will now close an associated alert.
Bug Fixes
- Out of the box tables that do not have audit enabled on will no longer display OOTB warnings.
- Deactivated scan check definitions will not be enforced.
February 24, 2025
This minor release of GuardRails includes numerous new features and enhancements designed to make user debugging easier and faster. Please review the release notes carefully as some changes may affect some customizations you may have configured for GuardRails.
New Additions
- GuardRails Pipelines: GuardRails Pipelines now supports App Repo. You can now sync application to your instance and push them to App Repo along with your update sets!
- New Roles: There are now two new roles in GuardRails
- GuardRails Fulfiller: This role can only update existing alerts, view definitions, and be assigned System Scan tasks. The perfect role for a fulfiller! Their access to Pipelines is restricted to view-only.
- GuardRails Pipeline: This new role can run pipeline instances, manage pipeline applications and update sets. They do not have the ability to create or modify an existing pipeline. The perfect role for a release manager!
- 3DES field deprecation: We are deprecating the ENVIRONMENT PASSWORD field in GuardRails Pipelines. Please migrate any existing environment configuration passwords to the new Environment Password2 field. Deprecation IS NOW COMPLETE and your old pipelines will FAIL if you do not migrate your configurations.
Bug Fixes
- Dashboards now visible to GuardRails Fulfillment Users
- Optimized GuardRails routes to reduce worker node congestion.
November 9, 2024
This major release of GuardRails includes numerous new features and enhancements designed to make user debugging easier and faster. Please review the release notes carefully as some changes may affect some customizations you may have configured for GuardRails.
New Additions
- GuardRails Support Agent: Support Agent – GuardRails will intelligently scan a form/config to fetch relevant support articles based on your instance meta data. This is different from the standard GuardRails Warnings as these are related to platform and not configuration. This feature will help customers accelerate their debugging process with end-users much faster than HI support.
This new feature is enabled by default for all customers.
- 3DES field deprecation: We are deprecating the ENVIRONMENT PASSWORD field in GuardRails Pipelines. Please migrate any existing environment configuration passwords to the new Environment Password2 field. Deprecation will occur on January 4, 2025 and your old pipelines will FAIL if you do not migrate your configurations.
- New GuardRails Properties: We have completely revamped our GuardRails Properties to be more verbose and flexible for customers.
Bug Fixes
- Optimized multi-instance collision detection to now use less query resources.
- Optimized GuardRails routes to reduce worker node congestion.
- Fixed issue where ATF would sometimes be tracked by GuardRails causing unnecessary noise and confusion.
October 4, 2024
Note: Some definitions have been disabled as the team works on addressing an issue in an upcoming patch.
New Additions
- Added new hint text to help users understand what each GuardRails field purpose is.
- Added new description field to Pipeline Instances.
- Performance improvement across the board with revised query engine.
Bug Fixes
- Corrected an issue with Deflections report having the incorrect URL being displayed.
- Corrected issue where pipeline update sets would display as UNDEFINED after a pipeline instance has started.
July 5, 2024
New Features
- New dashboard highlighting GuardRails deflections.
Bug Fixes
- Corrected an issue where sometimes alerts would not trigger for out of the box files.
- Corrected issue where some configs created by catalog builder would show up as out of the box.
May 22, 2024
Bug Fixes
- Corrected issue with instance version selector not choosing Washington DC.
February 10, 2024
New Features
- GuardRails Monitoring has now been extended to all tables in ServiceNow including data tables! Monitor data integrity and apply your own rules to how data can be modified.
- GuardRails Pipeline Changes:
- You can now preview update set errors and resolve them from production.
- New help text and styles have been added to fields to help users navigate pipelines.
January 21, 2024
Bug Fixes
- Fixed GuardRails URL not parsing correctly for some unique customers.
January 3, 2024
New Features
- Pipeline Update Sets:
Previously, update sets CREATED from the beginning of the current month would be fetched. Now, update sets UPDATED within the last 30 days will be retrieved. - Update sets that have been committed to production will no longer appear as a selectable update set within a pipeline instance by default.
- Additional filters have been added to only display update sets pertaining to the source environment by default.
- GuardRails Debug will now display clearer messages for missing read-access and scope privileges.
Bug Fixes
- Fixed GuardRails Debug numbering typo.
- Update Set Collisions will now trigger GuardRails Alert creations, without the need of additional known error/best practice violations.
November 20, 2023
New Features
- Linked Pipelines. You can now autogenerate a secondary pipeline upon completion of a Pipeline Instance. This allows you to have two independent pipelines for a single release. Example of usage: Dev -> QA (Pipeline 1), QA-> PROD (Pipeline 2). Experiment with new ways to approach your releases.
- Pipeline instances can now override ATF from your Pipeline configuration. When configuring a new pipeline instance, you can now specify an ATF override which will override the default ATF test plans with your own selection.
- Removed New/Edit button from Update Set picker in pipeline after build has started.
- Environment Configurations and GuardRails properties now autoformats URL field.
Bug Fixes
- Fixed Override ATF option from overriding existing ATF activities with blank ATF test suites.
- Added Cascade Delete to Pipeline Instances.
- Resolved various CORS errors.
- Fixed spelling error in GuardRails Verification Step.
- Build Requests for Complete/Retrieve Update Sets showed pending when there is no update set. Will no longer create a Build Requests for a Pipeline Instances that contains no update sets.
October 30, 2023
Bug Fixes
- Fixed issue where Pipelines could not be created because of missing environment while environments could not be created with a Pipeline.
October 23, 2023
New Features
- Pipeline instances can now import XML files in target instances. When configuring a new pipeline instance, you can attach XML files and select which instances you want to load these files into. This new feature harbors immense power to allow users to migrate changes without propagating to production (think Mid Server test configs!)
- Pipeline instances can now override ATF from your Pipeline configuration. When configuring a new pipeline instance, you can now specify an ATF override which will override the default ATF test plans with your own selection.
To take advantage of these new pipelines features, you must install the new GuardRails Pipelines v4.0 update set in all instances. This file can be found in our new interactive install guide page here:
GuardRails Installation Guide – Dyna Software Inc.
Bug Fixes
- Various stability improvements.
- Added new flavor text on fields to help usability.
- Pipelines cannot be saved unless source and target destinations are valid.