Object types

Some object types are supported by Object Migration while other object types are not.

Attention: IBM® TRIRIGA® does not support the customization of platform-managed objects, such as, but not limited to, Document and Group objects. As a result, data that is added to any customized fields on platform-managed objects will not be supported by Object Migration import or export. For more information on core platform-managed objects, see Core objects.

The following object types are supported by Object Migration:

  • Alternate Form List
  • Application
  • Associations
  • Budget Token
  • Business Object
  • Calendar Set
  • Document
  • Form
  • Group
  • Hierarchy Structure
  • List
  • Module
  • Navigation Collection
  • Navigation Item
  • Object Label
  • Portal (post 3.0)
  • Portal Section
  • Query
  • Record Data
  • Scorecard (post 3.0)
  • Styles
  • Web Component
  • Workflow

For more information about an object type, see the Application Building for the IBM TRIRIGA Application Platform collection of user guides.

You can select the Application or Web Component object type to search for and add applications or web components to your export package. By default, all metadata that is related to the application or web component, including dependent metadata, is automatically selected for inclusion in the package. You can use the search parameters to limit the dependent data.

You can use the Record Data option only for moving setup data, templates, and other items that are imported once and used as a template.

The following object types are not supported by Object Migration:

  • Action item
  • Manager
  • Portal (pre 3.0)
  • Scorecard (pre 3.0)
  • Query list
  • Query portal section
  • Quick add list
  • Shortcut list
  • Site Style
  • State Family
Note: Images that are stored in Record Data are not moved from the source to the target during the Object Migration export/import process. During export, Object Migration includes a simple path to the image file (in the source system’s userfiles folder) in the Record Data XML. During import, this path is saved in the target system’s record but the image is not visible to the user. For images to be available in the target environment after import, copy the image files from the source userfiles folder into the target userfiles folder.