C1000-183: IBM Maximo Manage v9.0 Functional Deployment — Professional

Veeva Vault objects include a configuration option to "Audit data changes in this object." Enabling this Audit setting on the Object is what causes Vault to automatically record data changes (creates, edits, deletes) for that object's records in the audit trail/audit log. This setting is off by default and must be explicitly turned on for the object; without it, record-level data changes are not captured in the audit trail.

In IBM Maximo workflow design, the Manual Input node is specifically used to present users with a list of selectable options during workflow execution — for example, letting a user choose among three possible actions or values, such as selecting one of three owners for a record. This differs from a Task node, which typically offers only two choices (such as approve/reject) and is used for routing assignments, and from an Interaction node, which presents Maximo UI dialogs, applications, or tabs to trigger actions between applications rather than a multi-option selection list for the user.

IBM Maximo stores data at four levels: System, Set, Organization, and Site. Calendars are Organization-level records — each calendar is created for a single organization and is shared by every site within that organization, where it defines shifts, work periods, and non-working time used by labor, crews, assets, locations, preventive maintenance, and SLAs. A calendar cannot be shared across organizations (so it is not System-level or cross-site data), and it is not restricted to an individual site.

In IBM Maximo Application Suite's AI architecture, Object Structures define the exposed data model (fields, attributes, and relationships) that the AI features consume, and the Saved Queries attached to an object structure apply the WHERE-clause filters that determine which records are included. These object structure saved queries are what is configured to select the record set used to train a model, to control which records are pulled for inferencing, and to define the shape/structure of the data fed to the model - distinct from the AI broker (which orchestrates the overall AI workflow), the AI model runtime (which executes training/inference), and external systems (such as watsonx.ai, which perform the actual model training/hosting).

Domains are defined in the Domains application, but the actual linkage between a domain and a specific object's attribute is performed in the Database Configuration application. There, you select the object, open the attribute record, and set its Domain field to the desired domain. This action validates that the domain's data type is compatible with the attribute before the association can be saved.