Creating new set of screens for new document type

Creating a new set of screens for a new document type involves accessing the Order entity resource ID order from the Resource Hierarchy tree.

1. From the Resource Hierarchy tree, navigate to the Order entity (resource ID order).
2. Select Save As to create the new set of resources from the Order entity, including its sub-resources.

   When you save the entity, give it a unique prefix that does not conflict with any resource IDs that might ship with future releases. recommends that you choose any prefix except one that begins with the letter Y (which is reserved for use by ).

   Note that when copying resources for a new document type, you must copy all entities (including sub-resources) for the existing document type.

   1. Determine which resources to copy using the following SQL script:

      select resource_id from yfs_resource
      where resource_type='ENTITY' and document_type='0001'

   2. Change the view group IDs for any Icons, Actions, Links and JavaScript functions that call the views. The view group ID should be changed to the new entity prefix and the view group ID that already exists.
3. Modify the description of the new entity resource to the description of your new document type. For all the sub-resources also, make appropriate modifications to the descriptions and create entries for these newly created resource keys in the INSTALL_DIR/extensions/global/resources/extnbundle.properties file, and in the corresponding properties files for each locale.
   Note: Ensure that the following file does not exist:

   INSTALL_DIR/resources/extn/extnbundle.properties

   This file must be removed because it will conflict with the extensions build process for bundle entries.

4. Modify the Document Type for the new resources of resource type entity to the new Document Type.
5. Update the Related Entities Resources under the newly created entity resources to point to the newly created resources.
6. In order to make all links point appropriately to your new view, follow the steps in "Incorporating Customized Views Across the Application."