Can Rev-Trac ensure developers are not unintentionally changing an object currently being tested in QAS?
Yes. Rev-Trac extends SAP’s own locking concept beyond the time of transport release, and extends the SAP locking concept to include configuration as well as workbench objects. Rev-Trac’s extended locking system ensures that a developer who starts to change an object or configuration that is currently awaiting testing in QAS is notified that the object or configuration is locked to a particular Rev-Trac request, and that all changes to this this object or configuration should be recorded against the same Rev-Trac request. A mechanism exists to loosen this restriction in specific circumstances, or on a case-by-case basis, if required. Locks are dropped when a change reaches production.
Related Questions
- We currently use tympanic (or electronic predictive, or digital electronic, or glass) thermometers. Why should I consider changing to single-use thermometers?
- How do we know the light is shifting as opposed to chemical reactions changing the chemical composition of the object?
- Can Rev-Trac ensure developers are not unintentionally changing an object currently being tested in QAS?
