Interface MaxIntObject

Identifies the integration object. This value must be unique.

Describes the integration object. To enter or view additional information, click the Long Description button.

SELFREFERENCING

Specifies whether the corresponding object was predefined (MEA-supplied) or added by a user. If the check box is selected, a user created the object.

CHANGEBY

CHANGEDATE

DESCRIPTION_LONGDESCRIPTION

Unique Identifier

XML representation of the selected integration object. It reflects the included and excluded persistent, non-persistent.

Language Column

Boolean flag to indicate if there is any long description for this record

Path to a Java class file that contains outbound processing and filtering code. This is a processing class that is typically used to filter the content of any MOS created by Maximo. It is applicable only for Publishing and/ or filtering query responses. This class is not always required

Path to a Java class file that contains Inbound processing code. This is a processing class that facilitates the creation/ update of the MBOs that constitute the MOS. Note that this class does not contain any processing logic for query support it is only for facilitating Content Management (Create/ Update/ Delete) Services. This class is not always required.

This is a Boolean indicator identifying if the MOS can be used to create/ update Maximo MBOs

Identifies if the MOS is configurable i.e. if the user can Add/ Modify any of the MOS properties.This flag will always be 'Y' for all user-defined MOSs.

This is a Boolean indicator identifying if the MOS supports Flat File/ Interface table processing. This defaults to 'N

Indicates from where in Maximo the Maximo Object Structure is accessible. Possible values include: ALL, INTEGRATION and DEPLOYMENT MGR. If you choose ALL, the MOS can be used from any Maximo application. If you choose INTEGRATION, the template is available from the INTEGRATION applications, but cannot be used in other app. Chosing either DEPLOYMENT MGR or someother app limits the use of the MOS to within that specific application. Click the Select Value button to indicate from where the MOS can be accessed.

Identifies the status of the Alias Validation Process

UseWith Description

Message type. The Value of this field comes from SYNONYMDOMAIN "MESSAGETYPE"

XML representation of the selected integration object. It reflects the included and excluded persistent, non-persistent.

The application using this object structure. Only applies to report object structures.

The specified application can authorize inbound queue-based or synchronous integration messages to this object structure. The application can also authorize export of data from this object structure.

Search Attributes.

Copy from Application.

Copy Group Authorization

Use Object Structure for Authorization Name

Load Query From All Apps

Auto Paging Threshold

Time-Line Attribute

Data restriction condition

Query Apps

Tags

Indicates whether this object structure is for a primary API. A primary API is provided with your Maximo system and is the preferred API for the associated Maximo business objects. If an object structure that is designated as a primary API exists, use that object structure for all interactions with the associated Maximo business objects.

The name of the module. The name must match the name of the module that is used for the associated Maximo application.

Indicates whether the object structure is internal. An internal object structure is typically used for system-level features and data, such as administrative and configuration data. You cannot configure an internal object structure for integration.

For self-referencing Object Stuctures publish complete hierarchy when unchecked data is published in a two level hierarchy.

Graph Type

Graph Type Name

Child object details for this integration object