Default language.

AR System definitions


In , a definition is the description of the structure in which objects, views, and applications are organized, identified, and manipulated in the . Object definitions contain no user data or entries.

You can use two methods for exporting and importing definitions:

  • You can move  objects from one server to another by exporting object definitions to a file, and importing the definition file to a server on the same or a different computer. You can export object definitions by type (for example, all menus), or those for a specific server.
    •  version 9.1 and later does not support the encrypted object definitions from  version 8.1.
    • If the version 8.1 object definitions are locked, the  handles the object definitions as unlocked.
    • We recommend using the latest  version to avoid problems that may arise due to locked object definitions.
  • You can export and import deployable applications from one server to another. Exporting and importing a deployable application automatically includes all the forms, workflow, menus, web services, packing lists, localized messages, reports, application roles, support files, and the form data (if specified) that are referenced by the application. For more information, see Exporting-and-importing-a-deployable-application

    To learn about exporting and importing data, Importing data into AR System forms

    When you export object definitions to a file, you select a file type — either  definition or  XML.

The definition file type

The  definition type is the default for exporting object definitions. It is a proprietary format for storing the definitions of  structures. You can include several applications within the same .def file.

The XML file type

The  XML type for exported objects produces an XML document that is comparable to the Remedy AR System definition file format. It follows the syntax of the XML specification 1.0. Specifically, every  object type has an associated structure definition in XML, which is specified by the XML Schema Definition (*.xsd) file. The *.xsd files reside on the  and are used to validate the  object definitions as valid XML. 

Exported objects in XML format comprise an XML document, which might also be referred to as an instance of a particular XML schema definition for that object. If the XML schema definitions are loaded into an XML editor, someone who is knowledgeable about  objects and XML can edit the XML document. 

The XML schema definitions are designed to be similar to the definitions in the *.def files. You can include only one application inside an .xml file. For more information about the XML Schema definitions of  objects, see the data structure information in XML-transformation-routines.

Warning

If you are exporting an object that contains XML text (for example, a form with a data visualization field that holds a flashboard), you must use a .def file. Because of an XML parsing limitation, exporting and importing XML text in XML files is not supported.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*