Moving a Core Item to Customized Layer

This section describes the initial steps required to move a completely new Form, Table or a Dialog window that has been developed under Core project, as a customization, to the Ext or Cust layer. Depending on the complexity of the customization, additional steps may be needed as well, which can not all be covered here.

Contents

 

Moving an item into customization layer

Complexity of moving an item that exists in core layer into customization layer depends on the complexity of the customization. This section describes minimal steps required to achieve the task. Depending on the situation developer may needs to perform additional manual steps. 

Prerequisites:

Prior performing the following steps, developers should possess a customization project that extends already available core project. To learn how create a customization project, please refer to Starting a New Client Customization. The offending item (Form, Dialog or Table window) should be uplifted in to IFS Applications 9 as mentioned in the Uplifting of a completely new form window guideline.

Procedure:

Updating the Navigator

Original Item should be removed from the original navigator-functional.xml and the re-named item should be added in to new navigator-functional_<layer>.xml available in client folder. To do this, use Edit Navigator functionality available with IFS Development Tools in Visual Studio. More information on updating the navigator is available here.

Updating the dictionary

After the move process, the client dictionary needs to be updated. It's done by running the Generate Dictionary functionality available with IFS Development Tools menu in Visual Studio. Make sure to add both core and customization projects to the scanning process. More information on generating the dictionary is available here.

Updating presentation object repository

Presentation object corresponding to the moved item and the renamed item should be updated by scanning both Core and Customization layers. After the scan, the updated presentation object and its dependency information will end up in <module>PresObjectRepository_<layer>.ins file. Old entries will get removed from <module>PresObjectRepository.ins. After running through this process, developer should carry out necessary updates to roles to reflect new changes and make sure that the functionality remains intact. More information on presentation object scanning can be found here.