Less than a year after launch, Melbourne-based Revelation Software Concepts (RSC) has released the first service pack update to Rev-Trac 7, providing key capability enhancements for organisations using their SAP change control automation software.
The SPS01 update improves integration with RSC’s Salt intelligent database, improves release management workbench capabilities and improves support for SAP S/4 HANA change management to enable more error-free database change coordination. This provides coordination for all changes made, even those made by teams working in parallel or those working in hybrid systems outside the direct HANA environment. Alerts are provided if conflicts are detected.
The improvements are expected to build on Rev-Trac’s already high satisfaction levels. According to research conducted by TechValidate, 94 per cent of RSC customers surveyed report that Rev-Trac has improved their efficiency by more than 50 per cent, while 64 per cent say that Rev-Trac has helped them simplify or improve their ability to manage change within SAP by more than 70 per cent.
“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,” he said.
The peripheral object dependency (POD) checking feature leverages Salt’s custom code database to index and map technical relationships and dependencies between object versions. This feature helps users assess probable results when moving changes or releases forward and alerts them if required technical object versions are missing from the target system.
The workbench updates allow for the synchronisation of any request type. Request level explicit dependencies enable an organisation to define the sequence of migration for entire Rev-Trac change requests or can be used with explicit transport dependencies to provide a more granular level of control. Source-specific cloning allows users to make a single Rev-Trac clone request to manage the replication of changes to multiple applications.
