Chapter 10 Application Manager Enhancements

Version Renaming

Ever named a version incorrectly by mistake and wished you could change it? Ever wanted to base-line your app and adopt a common set of version names before sending it out? Ever wanted to rename a Configuration Map without having to create a new one and purge the old one? If so, you're going to love these.

These commands are protected via ENVY security. The Library Supervisor must enable the “Allow Special Features” command in an image before the user will be able to rename classes and applications or re-use names when versioning.

Applications Menu Commands

View | All Applications

View all of the loaded applications.

View | All Visual Applications

View all of the visual applications. These are applications containing WindowBuilder or Composition Editor view definitions.

View | Applications Managed by “Current User”

View all of the applications managed by the current user.

View | Applications Matching Prefixes

View all of the applications matching a set of user selected prefixes.

View | Applications Needing Versioning

View all of the applications needing to be versioned.

View | Set Application Prefixes

Set the list of prefixes used to filter the applications list. The list of prefixes is dynamically determined from the list of loaded applications.

View | Add Application Prefix

Add an arbitrary string to the list of prefixes used to filter the applications list.

View | Set Open Edition Prefix Character

with thanks to S. Sridhar

Specify the character to use to prefix open and scratch editions of applications. Only available when enhanced list support is turned off.

View | Change User

Change to a different user. Only users that manage applications will be listed.

Import/Export

Consolidates all of the import/export commands.

Import/Export | Import New Names

Sets the policy used when encountering new application or class version names during import. If the version names in the import library differ from the names already present in the current library, the new version names may be “Always Accepted”, “Always Rejected”. If set to “Always Ask”, the system will prompt the user for how to proceed.

Import/Export | Export Library Format

Defines the default export file format. Choices include “16GB (New Format)”, “1GB (Old Format)” and “Always Ask”. VA 4.5 or above only.

Subapplications | Release To Existing Configs

Releases the new editions of the selected subapplications to the same configurations as the existing editions. For example, if a subapplication appears in two out of four platform dependent configurations, this command will release the new edition into only the two configurations that it had previously been released to. This eliminates the need to open an Application Editions browser to examine the configurations before releasing the subapplications into the appropriate ones.

Configuration Maps | Locate Selected Applications

Find the current (e.g., most recent) config maps containing the selected applications by name.

Configuration Maps | Locate Maps For | Current Edition

Find the specific config map editions containing the selected application edition.

Configuration Maps | Locate Maps For | Any Editions

Find all of the config map editions containing any editions of the selected application.

Configuration Maps | Release Selected Applications

Release the current editions of the selected applications into their containing config maps and optionally propagate the changes throughout the entire config map hierarchy.

Configuration Maps | Release Other Editions

Release the other editions of the selected applications into their containing config maps and optionally propagate the changes throughout the entire config map hierarchy.

Configuration Maps | Propagate Changes

Indicates whether config map changes should be propagated throughout the entire config map hierarchy.

Configuration Maps | Create New Editions As Necessary

Indicates whether new config map editions should be created in the event that no open edition currently exists.

Configuration Maps | Update Required Map Lineups

Indicates which required map lineups should be updated when config map changes are being propagated. If set to “All”, all lineups will be update. If set to “Valid”, only currently valid lineups will be updated. If set to “Current”, all lineups that are currently up to date will be updated. If set to “Filtered”, only lineups not matching any expressions in the filter list will be updated. Additional options are also presented to allow the use to edit the current filter list, add a filer or clear all of the filters.

Create & Release New Edition

Combines the Create New Edition and Release To Existing Configs commands. When creating a new subapplication edition, this is the ideal command to use. This command will recursively create and release editions of any parent applications if necessary.

Rename Version | Classes

Provide new version names for all of the classes within the selected applications that have changed since a specified cutoff date.

Rename Version | Applications

Provide new versions names for all of the selected applications.

Rename Version | Both

Provide new versions names for all of the selected applications and the classes within them.

Rename Version | Include Subapplications

Provide new versions names for all of the selected applications, their subapplications and the classes within them.

Rename Version | Reset Cutoff Dates

Reset the default cutoff date to 1-1-93.

Version | Include Subapplications & Classes

Recursively version all of the selected applications, their subapplications and the classes within them.

Version | Allow Any Name

When turned on, this command allows you to specify any version name for an edition regardless of whether the name has been used in the past. This makes it easy to correct naming mistakes or create new versions with the same name as a prior version.

Groups | Add Users

Add a user to all of the selected applications.

Groups | Delete Users

Delete a user from all of the selected applications.

Groups | Replace Users

Replace one or more users in all of the selected applications with another user. If the original users owned any classes or managed any applications, the new user will become the new owner of those classes and the new manager or those applications.

Groups | Include Subapplications

Apply the above changes to all of the subapplications within the hierarchies of the selected applications.

Privileges

Enhanced all of these commands to apply to multiple selected applications (as opposed to only one application at a time).

Classes Menu Commands

Locate

Find all of the applications defining or extending an arbitrary class regardless of whether the applications are loaded in the image or not.

Add

Add subclasses and class extensions to the application without needing to access an Application Browser or a Classes Browser.

Rename Version

Provide a new version name for all of the selected classes. If multiple classes are selected, names may be specified for each class or all classes as a unit. If a version name template has been specified, it can be applied retroactively to the selected classes as well.

Version | Allow Any Name

When turned on, this command allows you to specify any version name for a class edition regardless of whether the name has been used in the past. This makes it easy to correct naming mistakes or create new versions with the same name as a prior version.

Version/Release All | Allow Any Name

When turned on, this command allows you to specify any version name for a class edition regardless of whether the name has been used in the past. This makes it easy to correct naming mistakes or create new versions with the same name as a prior version.

Version/Release Selected

Version and release the selected classes using a different name for each class, one name for all classes or the default names for all classes.

Prerequisites & Dependents Menu Commands

Delete

Delete the selected prerequisite (if possible).

Path

Discover why an application is either a prerequisite or a dependent of the selected application. This command displays the shortest paths between the selected application and the selected prerequisite or dependent (starting with the applications immediate prerequisites or dependents).

Why?

Discover why an application is either a prerequisite or a dependent of the selected application. This command displays a textual description of the reasons that the application is a prerequisite (or not).

Find

Find the selected application in the application list.

Group Menu Commands

Change To “Selected User”

Change the active user to the user currently selected in the Group Members listbox.

Replace

Replace the selected user with another user. If the selected user owns any classes of manages the application, the new user will become the owner of the classes and the manager of the application.

Select Owned Classes By

Select the classes owned by a specified user.

Become Manager

Change the manager of the application to the user currently selected in the Group Members listbox.

Browse Unreleased Classes

Quickly view the unreleased classes owned by the selected user. Version and release them in place. With thanks to Sherwood Zern.

Super User

Become a Super User who can leap tall buildings with a single bound. Super Users are designated by a '+' appended to their names in the title bar of the Application Manager.

Miscellaneous Enhancements

Visual Hinting of Open & Scratch Editions

When the application names are long or the window is narrow, you can never tell simply by looking if an application is an open or scratch edition. This is even more difficult for subapps that are indented. We have added a minor visual enhancement that puts a dash before the application name, if it is an open or scratch edition (or if one of its subapps is a scratch edition). This feature is only active when extended list support is turned off.

Class Double Click Preference

Select Double Click operation in Application Manager (Browse Hierarchy, Browse Class, Test, Edit).

Revision Notes

Add optional revision notes when versioning applications and classes (stored in notes field of the application or class edition).