Skip to content

Known Limitations

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

Supported Configuration Item Types

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

  • Custom Attributes
  • Custom Enumeration
  • Custom Entity
  • Custom Page
  • Projection Configuration
  • Custom Event
  • Custom Event Action
  • Quick Report
    • Supported types: SQL Statement
  • Mobile Application
  • Navigator Configuration
  • Configuation Context
  • Queries (Query Designer)
  • Workflow

The available configuration items listed in 'Add New Configuration Item'function in the Application Configuration Package page will show the configurations that are supported.

Removal of Configuration Items 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 configuration items 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".

Approve setting will remain unchanged on Enumerations and Custom Entities after Import

A Custom Enumeration or Custom Entity that is already published cannot be set to "Not Approved" through importing. A Custom Enumeration or Custom Entity needs to be unpublished first in the target environment. When importing a Custom Enumeration or a Custom Entity 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.

Important Considerations

Any configuration item can only be connected to one ACP at a time.

ACPs can be exported and imported by an end user account (with the necessary permissions) as opposed to the application owner account, for which most customers do not have the password. ACPs can be imported using the IFS Cloud Web interface.

There is a deployment sequence in some cases. For example, if we have a custom enumeration, a custom persistent field, and a custom read-only field that are all related, then they have to be published in that sequence. This sequence of publishing is automatically handled when importing an ACP.

Consider two environments, a build place environment and CFG. Configuration Items W, X and Y are developed in the build place environment, then exported via ACP & imported into CFG. Some time later, in the build place environment, object X is removed and new object Z is added. Then again ACP is exported and imported into CFG. However, the result is that CFG now contains W, X, Y and Z. This is because ACP import does not handle removal of objects that are no longer in the ACP. It only handles new and changed objects currently in the ACP. In this scenario, removal of object X from CFG would have to be done manually.

Another important point is that the configuration item pointer is based on the ROWKEY, not the object name. If we independently create the “same” configuration item in two environments, they will have differing ROWKEYs. If we try to export one and import it into the other environment, we will receive a conflict; basically the issue is that “another object already exists with that name but a different ROWKEY”.