SPS01 strengthens Release Management Workbench, expands support for SAP S/4 HANA,
and deepens integration with the Salt custom code database
Melbourne, AU - November 15, 2016 – Revelation Software Concepts Pty Ltd (RSC), a pioneer and market leader in simplifying SAP change control, today announced the release of their first major enhancement (SPS01) to version 7 of their flagship SAP change control automation software, Rev-Trac. The SPS01 update includes many features that strengthen Rev-Trac 7’s Release Management Workbench, supports all aspects of SAP S/4 HANA change management and further leverages the custom code database of RSC’s Salt SAP change intelligence software.
“This service pack provides important foundational improvements to Rev-Trac’s popular Release Management Workbench, but it’s Rev-Trac’s expanded integration with Salt’s custom code database that excites our Rev-Trac customers,” said David Drake, RSC Founder and CEO.
“The current release introduces Peripheral Object Dependency Checking and includes API integration points for further Salt and Rev-Trac Java integrated enhancements we’ll make available in the foreseeable future.”
- Updates to the Release Management Workbench focus specifically on release and change status synchronization, and adds the capability of synchronizing any request type including non-SAP requests.
- Request level explicit dependencies will allow for an organization to define the sequence of migration for entire Rev-Trac change requests, treating each of their subordinate transports as a group that can be sequentially controlled.
- Source-specific cloning allows a single request to manage the replication and retrofit of changes to multiple applications, using a single Rev-Trac clone request.
- SPS01 expands Rev-Trac’s SAP S/4 HANA support by including both native and non-native (non-ABAP) changes.
- As the first in a series of Rev-Trac features improving the integrity of changes delivered across multiple complex or hybrid SAP landscapes, the new Peripheral Object Dependency Check, or POD Check, helps teams avoid problematical outcomes from moving changes or releases forward without required dependent object versions.