Additional Information

AdminStudio 2023 | 25.0 | Application Manager | Rules Wizard

Edition:Application Manager is included with AdminStudio Professional and Enterprise Editions.

From the Additional Information panel, you can provide information for categorizing the ACE in relation to other ACEs in Application Catalog.

Additional Information Panel Option

Option

Description

Category

Either select an existing category for this new rule, or enter the name for a new category. These categories are displayed in the Conflict View and the ACE Tests tab of the Options dialog box. Ideally, any user-defined ACEs should be put in their own category.

Rule Type

Specify the type of ACE you are creating:

• Custom - Source Only Packages ACEs allow you to quickly test any column or any value of a table to support your business logic. For example, you could use a user-defined ACE to identify packages that create a desktop icon. To define a Source Only Packages ACE, you must define an SQL “Where” clause.

Application Catalog supports external package conflict checking for Custom - Source Only Packages ACEs. The Source package can be selected from the Application Catalog Database or from an external MSI package.

See Creating a Custom/Source Only Packages ACE for more information.

• Custom - Source and Target Packages ACEs allow you to compare columns or values of Source package tables (new packages that you want to install onto a user’s system) to columns or values of Target package tables (packages already installed on a user’s system).

For example, you could use a Source and Target Packages ACE to determine if the installation of a Source package onto a Target system would overwrite or conflict with an existing entry in the .ini file in the System directory of the Target system.

To define a Source and Target Packages ACE, you must define a SQL “Where” clause, and specify a Join Column—a table column in the Application Catalog database that has a matching value for both the Source and Target packages. Rows in each of the packages that have a matching value in the Join Column are selected and those rows are checked against the Source and Target Packages.

Application Catalog does not support external package conflict checking for Custom - Source and Target Packages ACEs. Both the Source and Target Packages must be selected from the Application Catalog Database.

See Creating a Custom/Source and Target Packages ACE for more information.

• DLL - User Provided DLL Based ACEs allow you to run more complex tests—testing many tables in any combination. For example, you could use a DLL-Based ACE to confirm that a source product language is the same as all target product languages. To define a DLL-Based ACE, you use SQL and various programming languages to construct a Windows DLL. With DLL-Based ACEs, you can use a Conflict Application Resolution Definitions (CARDs) to fix the conflict. See Creating a User Provided DLL-Based ACE.

Click Next to proceed to the Custom Options panel or the DLL-Based ACEs panel; click Back to return to the General Information panel.