---

Here are the key features of Deltanji. Note that certain features are only available in specific Deltanji editions.

• Flexible configuration options allow different levels of control to suit the company culture and size of the teams.
• Web-based interface for object transfers.
• All development work is linked to a change request recording the reason for the change.
• Concurrent development can be supported, ensuring that changes are not lost or inadvertently overwritten as a consequence.
• An object-based approach allows different components which form a natural unit to be managed together.
• Components managed include binary or text files and many types of Caché, Ensemble and HealthShare components. The extensible architecture supports custom component types.
• A centralized library stores reference copies of all versions of an object in an immutable repository.
• Old versions of objects are always available for comparison or for re-instatement if this becomes necessary.
• Logical locations mean users need not be concerned about where the code components are actually stored.
• Status of objects (e.g. 'for test' or 'approved') is easily tracked by means of multiple logical locations, typically all mapping to the code repository .
• Deltanji identifies one master location for each version of an object. The nature of that location controls whether the version is editable or read-only.
• By recording the version of each object at each location Deltanji tracks and controls the movement of objects.
• Variants of objects can be tracked simultaneously (e.g. customer-specific code variants, or English and French language variants).
• Systems can be defined to allow easy control of objects belonging to different applications. Deltanji tracks the system membership of objects and the locations handling each system.
• Transfers provide a powerful, configurable and flexible mechanism to move or copy objects from one location to another.
• Transfer route dependencies allow the system manager to control the conditions under which code moves.
• Multiple objects can be transferred in a single step using the change request ID.
• Automatic transfers can be defined which effortlessly keep multiple locations in sync.
• Networking capabilities enable code management across multiple environments.
• Packaging and deployment features support the controlled transfer of objects to isolated remote sites such as live servers.
• Access security gives control over who can view which locations, make which transfers etc.
• Reports inform project managers of the progress of projects, work which is overdue, and any concurrent development which is in progress.
• The audit trail for each object shows every movement and status change which has happened to it. Change request operations are also audited.
• SQL tables enable ad-hoc querying of Deltanji for reporting purposes.