Yes, Release Coordinator is capable to track and trace T24 releases installed in several environments. A detailed report of the releases is generated.
Release Coordinator can manage Temenos Patches (coming as BCONs) or local releases which could be either directly developed with Validata ABC or coming as DL.DEFINE/BCON from the local development team.
Yes, Validata ABC keeps a full log of the release deployment process.
Capability to install a release to a T24 multi application server setup is available.
With Release Coordinator we can have any management process defined as a workflow in the tool. This includes a strict order of releasing packs (e.g. QA cannot be released unless TEST is released) and also control over which role is doing the release (e.g. the role doing the release in TEST won’t have access on UAT). So, a complete management of the release procedure is accomplished from the development stages to production.
Release Coordinator is featuring a versioning system making sure that you’re always working with the latest version of the programs. This way, release dependencies are checked.
Defining proper configuration rule(s), a rejected task can be/or not be included.
Yes, Release Coordinator contains both alerts at the interface of the tool and e-mail notifications.
The tool has integrated T24 import functionality with wizard-like UI to select the specific component (version, enquiry, etc.) to import and check it into a Validata source code repository.
Release Coordinator provides means to limit the access to deployment only to certain user roles. This includes also limiting access to certain areas (UAT, PROD) only to certain roles.
Release Coordinator provides public API, which allows interaction with the tool. There is also an option to schedule releases from 3rd party tools.
Release Coordinator has its own repository where the artefacts can be checked in/out. Release Coordinator has also visual wizards for extraction/release of artefacts from/to the target system. Two of these wizards were demonstrated last week: BCON import and Data Record import.
The tool provides a rollback mechanism for quick revert of some development, which proves to be faulty. This makes it very usable on a dynamic environment such as DEV or TST.