This documentation supports the 22.1 version of Action Request System.
To view an earlier version, select the version from the Product version menu.

Importing object definitions

This topic describes how to import object definitions to a server. You can overwrite existing forms without deleting existing data or breaking links to workflow, and you can also import data along with a specified form.

When importing object definitions from files, remember the following points:

  • You must first create a file that contains the object definitions to import by using the procedure described in Exporting object definitions, views, and applications.
  • Before you begin importing, make sure that your database has adequate resources. Perform large imports during hours when users do not require access to the system.
  • A server cannot have two objects with the same name. If an object in the import file has the same name as an object on the destination server, perform one of these tasks:
    • Remove the object with the same name from the destination server
    • Rename the object with the same name on the destination server

      When you import an overlay that has inherited properties, those properties are inherited from the copy of the origin object that is on the server. If you import the origin object with the overlay, then the overlay will inherit properties from the imported object. If not, then the overlay will inherit properties from the object already on the server.

  • Developer Studio  cannot import definition (.def) files that are written in character sets other than UTF-8 or Western (Windows-1252) unless the charsets.jar file is installed in the JDKInstallationFolder\jre\lib folder.

To import object definitions from definition files

You cannot compare association objects in Remedy Migrator. You also cannot migrate association objects from .migrator or .def file to a server and from a server to a .migrator or .def file.

  1. Select File > Import.
  2. Expand Developer Studio  in the tree.
  3. Select Object Definitions, and click Next.
  4. Select the server to which to import definitions.
  5. Select the file (with a .def or .xml extension) that contains the definitions to import, and then click Open.
  6. Click Next.
  7. (Optional) If the object being imported is already on the destination server, complete the following steps:
    1. Click the Replace Objects on the Destination Server check box, which enables you to overwrite existing form definitions without deleting data or breaking workflow. 
      This check box informs the AR System server  to replace the display properties from the DEF file into the objects on the server. However, note that since it is the default behavior of the server, keeping this checkbox unchecked has no effect on server. This behavior is continued in version 9.x servers for backward compatibility reasons.
    2. Select any of the following options:
      • Delete Excess Fields — Deletes fields on the server that are not present in the file.
      • Delete Excess Views — Deletes views on the server that are not present in the file.
      • Replace Display Properties — Replaces the display properties of the object on the destination server with the display properties of the object being imported.
      • Replace Full Text options — Replaces the full text option of the object being imported with the value of the full text option for the object on the destination server.
      • Replace Application Owner — Replaces the Application Owner property of the object being imported with the value of the Application Owner property for the object on the destination server. This option is applicable for all objects within an application, except for free objects. When objects are added within an application, the property called AppOwner is set for these objects.

        For example, if the definition file contains an object for which the AppOwner property is set to A and there is a same object on the destination server for which the AppOwner property is set to B, then this option allows you to set the AppOwner property of the object being imported, to the AppOwner value of the object on the destination server.

        The objects within an application are expected to have the same value for the AppOwner property.

        Warning

        If you delete excess fields on the server, the associated data is deleted and any workflow might be broken.

        When importing a join form by using the Replace Objects on the Destination Server option, the new forms must meet the following requirements:

        • If Delete Excess Fields is not selected, all fields mapped from an old base form onto the join form must exist on one of the two new base forms. Also, the types of the fields cannot change. You can swap the primary and secondary base forms, redefine the join criteria, and switch between outer and inner joins.
        • If Delete Excess Fields is selected, any fields that are missing from a base form will be deleted from the join form, and the deletion will propagate upstream through any multi-level joins. Where possible, the audit and archive properties of join forms will be retained.
          For auditing to be enabled on a join form, the audit property must be enabled on the base forms. If an unaudited base form is imported, auditing on upstream joins is disabled.
    3. Select a Handle Conflicting Types option.

      This option lets you decide on what path to take if field IDs are the same on the server and in the file, but the data types are different.

      • Display Conflict Error (default) — Check for conflicting data types and report errors. The import not performed.
      • Take No Action — Leave the field as it is on the server. Data is not overwritten during import.
      • Replace with New Type— Replace the field with the new type during import.

        Warning

        If you replace the field with the new data type, the original data stored in the field is deleted and workflow might not work.

  8. Click Finish.
    If you attempt to import an application that is reserved by another user, the import operation fails with an error message. When you import objects that are reserved by another user, the reserved objects are skipped.
    When the import is completed, an Import Complete message appears.
  9. Click OK.

Sequence of object import

The following table shows the sequence in which the objects will be imported:

ObjectsRank

Regular Form, Image, Archive Form

0
Archive Main Form, Audit Form1
Audit Main Form2
View Form3
Join FormBase form Ranking + join levels
Menu Highest form rank + 1
FieldHighest form rank + 2
EscalationHighest form rank + 3
FilterHighest form rank + 4

Active Link

Highest form rank + 5
ContainerHighest form rank + 6

Packaging List

Highest form rank + 7
AssociationHighest form rank + 8

Flashboards and its related objects

Highest form rank + 9
ApplicationHighest form rank + 10
Was this page helpful? Yes No Submitting... Thank you

Comments