Deltanji 7.0 Release Notes


Version 7.0 was released on 3rd April 2019.

Pre-Upgrade Steps


There are no pre-upgrade steps required by this release.

Post-Upgrade Steps


There are no post-upgrade steps required by this release.

Enhancements


Give Change Request context menu an option to remove parent object from CR (VCM-D-0575)

Better way of doing ad-hoc transfers from Atelier and Studio (VCM-D-0611)

A generic 'Transfer' option has been added to the source control menus alongside 'Check Out', 'Check In' etc.

Allow audit messages of deleted CRs to be viewed (VCM-D-0613)

A new subfolder of the top-level Audit Trail folder provides this.

In GraphML diagrams, add route node text documenting change of master location (VCM-D-0620)

Support for Serenji 3.0 (VCM-D-0623, VCM-D-0657, VCM-D-0669, VCM-D-0671)

This includes a new 'Namespaces' view of the server, exposed through the Beyond Compare interface. It also makes INT component compilation errors log in the audit record.

List unused physical addresses with strikethrough to aid cleanup (VCM-D-0624)

Implement $$%WholeCR dependency (VCM-D-0627)

When $$%WholeCR is included in the dependencies of a route, the transfer must be a by-CR one, and any dependencies that follow $$%WholeCR in the comma-separated list will be tested for every transferrable member of the CR before any transfers occur.

If you don't already have a pre-init or a post-term transfer callout defined, set the preinit callout to "preinit^%vc1xvf" which is a stub callout whose presence causes Deltanji to create the data needed by the $$%WholeCR dependency. Without this the dependency will always fail, even if the transfer is of a single CR.

Allow backup route to locations that don't store in F or FX format (VCM-D-0638)

In browser component view, suppress folders with no content to expand (VCM-D-0641)

Folders that contain nothing apart from generated items used to be listed. This no longer happens.

Implement an editCheckOutValidation to test CR ownership (VCM-D-0660)

This can be used as an alternative to the constraint that restricts editing of a checked-out object's components to the person who performed the checkout. Instead this callout restricts editing to owner(s) of CR(s) the checked-out object is a member of.

Install via Setup\Properties\Editor Integration, setting the callout field to: ownerOfCR^%vc1edt

Implement the -*lcode multi-version deactivation syntax (VCM-D-0673)

This is useful for workflows in which multiple versions of an object may accumulate in a location for onward release. When one of the later versions is released from there a -*%FROM deactivation will also remove predecessors.

Corrections


In multi-monitor environments make popup windows appear on parent's monitor (VCM-R-0368)

Merge dialog lacked some down-lines when a version was on multiple CRs (VCM-R-0387)