Installation Changes You May Need to Review

When reviewing changes that an installation has made, look primarily for changes that may conflict or that are not needed because of customizations that you have made.

Related Topics
Changes that an Installation Makes
Important Installation Considerations
Preparing to Install to a Production Environment
Installation Change Description
Event triggers If you are using neither emxTriggerManager nor the naming conventions recommended by the ENOVIA Business Process Services documentation, then there is a good chance that your trigger will be overwritten.

If you do not have a trigger on a given event, then there is a chance that one might be added. If you do not want a particular trigger to run, you can deactivate the trigger by demoting the corresponding eService Trigger Program Parameters object to the Inactive state.

Note: Business objects are not captured in an XML compare. This is currently a manual process. It is recommended to back up all eService Trigger Program Parameter objects.
Access privileges ENOVIA Business Process Services or the application installation may add or remove some access privileges.
Properties files New installations typically add new properties that let you configure features and contain string resources for on-screen text display and internationalization. All properties files are stored in the ematrix/properties/ directory. When ENOVIA Business Process Services or any other application is installed, the installation copies all files in ematrix/properties/ to ematrix/properties.sav/ and then overwrites ematrix/properties/. The properties.sav/ directory is overwritten with each new installation, so make sure you back up this directory if you want to preserve it.

Properties files are intended to be configured, so any changes that you make need to be merged back into the newly installed properties files using any file comparison tool. The comparison should be between the newly installed properties file (located in ematrix/properties/) and the "old" properties file (located in ematrix/properties.sav/).
New administrative objects If you use ENOVIA Studio Modeling Platform Rich Clients, you may want or need to "hide" types that are not used so that the Type Chooser is not cluttered. Take care not to hide types that any ENOVIA products you are using may use. You may want to consider subtyping as an alternative.
New attributes You may see new attributes added to a type or relationship.
Administrative (schema) properties Most installations add schema properties.
Customized UI components Some installations may add customized UI components.