Extract module names

Previous Next

This action is only supported for the top-level application. Passing any other value for "Application" is an error.

Summary: This action performs a number of preparatory actions that are necessary to make the release of a top-level application with modules a success.

Details: Extracts from "Database account" :

The names of modules (if any) declared in the Definer of the top-level application.

The Active attribute of each declared module. This attribute corresponds to the Load Module flag in the Modules window of the consumer application.

The filepath to each module's .CON file, as registered in Definer as being the file used for synchronisation (if any is specified). If no filepath is specified but only a filename, then this filename is expanded to a filepath by prefixing the \APP subfolder of the local USoft installation folder. The .CON file used for synchronisation is NOT the same as the .CON file that is used when performing a release.

The extracted information is registered in Delivery Manager's Extracted Module Names table, overwriting any previously extracted information.

Checks that, for each module, a .CON file and an .ESI file are available in the location implied by the module's "Module Delivery Policy" setting. Choose Define, Applications in Delivery Manager to view this setting. An error is raised if this check is not passed.

Copies, if this check is passed for each module, the available .CON and .ESI files to the \APP subdirectory of the USoft installation folder. The reason for this action is that:

Delivery Manager needs the .CON file in this location in order to generate an .ESI flatfile for the top-level application.

Delivery Manager needs the .ESI file in this location in order to release deliverable appdata for the top-level application.

Ignores UDELIVER, USAUTH, USD, USERVICE and USTESTER as potential module names candidates.

Raises an error in case of a mismatch between the set of active module names found in "Database account" and the modules registered in Delivery Manager´s Applications table.

If the optional "XML folder" is not passed, it is set to the \udeliver subfolder of the local USoft Temp Dir. "XML folder" acts as an interim location where the extracted information is output before it is imported into Delivery Manager. This folder is only relevant during the extraction process. It is NOT cleared on completion.

Parameters

Name

Type

Optional?

Application

Application

No

Database account

Database account

No

XML folder

Folder or file

Yes

Rules

"Application" must be the top-level application.

Errors

An error is raised in case of a mismatch between the set of active module names found in "Database account" and the modules registered in Delivery Manager´s Applications table.

For example, it's an error if "Application" has a declared Module that does not appear in Delivery Manager's Application list at all, or that appears with an application type other than "Module", ie., "Top-level" or "USoft".

 

See Also

Create synchronisation file

Synchronise