Known Limitations

Application Configuration Packages do not support all kinds of configurations that can be made in IFS Applications, nor all possible uses.

Contents

• Supported Custom Object Types
• Removal of Custom Objects when importing a Application Configuration Package
• Custom Fields of type Local cannot be added to a package
• Approve setting will remain unchanged on Enumerations and Custom Logical Units after Import

Note: This page lists a number of situations that is important to be aware of in order to work efficiently with Application Configuration Packages. There are actually more situations that can be considered as a limitation than listed here.

Supported Custom Object Types

There are many configurations that can be done in the system. Many of them are not supported by Application Configuration Packages. The Custom Object types that can be added to a package are the following:

• Custom Fields
• Information Cards
• Custom Menu
• Custom Enumeration
• Custom Logical Unit
• Custom Page
• Custom Tab
• Conditional Field Action
• Custom Event
• Custom Event Action
• Quick Report
  • Supported types: SQL Statement and Query Builder
• Mobile Application

The available custom objects listed in Add To Package function in the Application Configuration Package page will show the configurations that are supported.

Removal of Custom Objects when importing a Application Configuration Package

When importing a package, the items defined in the package are imported to the target environment. There is no support for delivering a package that will remove custom objects that has been created by previous versions of the package and now are considered obsolete. Items that are obsolete needs to be manually removed in the target environment. The Export Comment could be used to provide such communication.

Example:

1. Environment DEV defines a package "Cars" containing two enumerations "Engine Type" and "Vehicle Type".
2. The package "Cars" is installed in Environment PROD.
3. Next version of "Cars" developed in the DEV environment contains the enumeration ""Engine Type" and the Custom Menu "Check Engine Type". But the "Vehicle Type" enumeration is removed.
4. Installing "Cars" in the PROD environment will update the "Engine Type" enumeration and add the "Check Engine Type" menu. The "Vehicle Type" will remain and still be in the package "Cars".

Custom Fields of type Local cannot be added to a package

A custom field can be of type Local. This is typically used for attributes defined in the Logical Unit but which is not an existing field in the client window. These Custom Fields are not supported by Application Configuration Packages and cannot be added to a package.

Approve setting will remain unchanged on Enumerations and Custom Logical Units after Import

A Custom Enumeration or Custom Logical Unit that is already published cannot be set to "Not Approved" through importing. A Custom Enumeration or Custom Logical Unit needs to be unpublished first in the target environment. When importing a Custom Enumeration or a Custom Logical Unit as "Not approved" to an environment where it already exists and is published, it will still be "Approved" in the target system if after import.