Applications in UDeliver
An application is a software solution built entirely or partially using USoft tools, or a tool delivered by USoft to assist in building such solutions. An application integrates three levels: data storage, business rules automation, and interfaces for communication with humans or other systems.
The concept of an application in Delivery Manager mirrors other USoft tools. For example, it matches:
- Applications listed in USoft Authorizer.
- Applications defined in USoft Binder, USoft Web Designer, USoft Service Definer, and USoft Windows Designer.
Like USoft Authorizer, Delivery Manager includes both custom applications and applications shipped by USoft:
| Name | Title |
|---|---|
| USAUTH | USoft Authorizer |
| UDELIVER | USoft Delivery Manager |
| USD | USoft Definer |
| USERVICE | USoft Service Definer |
| USTESTER | USoft BenchMark |
To define or view applications in Delivery Manager, select Define > Applications from the menu.
An application defined in Delivery Manager has the following properties:
Application
The name of the application as recognized in USoft Authorizer, USoft Binder, and other USoft tools.
Application type
Specifies the type as either "User application" or "USoft application":
- User application: Among the applications that you build yourself, you must designate exactly one as the "User application" in Delivery Manager.
- USoft application: These are applications shipped by USoft.
Version
The version of the application refers to:
- The version currently under development (for the User application).
- The version last shipped by USoft (for USoft applications).
Delivery Manager automatically sets the user application version to the current release name. If the current release has "Include packing slip" set to Yes, this version information is automatically copied to the packing slip during release actions.
Note: The "Version" property is not registered for USoft applications; it is automatically set to NULL.
USoft version
The version of the USoft tools used to develop the user application. You can retrieve this information in tasks by calling the Extract USoft version action.
If the current release has "Include packing slip" set to Yes, this version information is automatically copied to the packing slip during release actions.
Note: The "USoft version" property is not registered for USoft applications; it is automatically set to NULL.
Source for pre-upgrade check
The database account used to verify the correctness of SQL statements in pre-upgrade scripts.
If you have a way of working where the previous state of the application (the state of the previous release) is still available in a repository, you want to have pre-upgrade scripts checked against this state. In this case, set this property to the database account hosting that repository.
This property is required for the user application. It is relevant only for pre-upgrade scripts, meaning scripts where Processing Order is set to Pre-upgrade. Until such time, you can set it to the same database account as "Source for post-upgrade check", namely, the database account where the application is currently being developed.
Source for post-upgrade check
The database account used to verify the correctness of SQL statements in post-upgrade scripts.
This property is relevant only for post-upgrade scripts, meaning scripts where Processing Order is set to Post-upgrade.
This property is required for the user application. Set it to the database account where the application is currently being developed.
Description
An optional field for notes regarding the application.