Custom Attribute Missing From Application and Integration
An administrator adds a three-character attribute CUSTOMERSEGMENT to the WORKORDER object in Database Configuration. The attribute uses a new domain CUSTSEG with values A, B, and C. The administrator runs Apply Configuration and restarts the Maximo server. CUSTOMERSEGMENT is visible in Database Configuration, but it does not appear in the Application Designer palette for Work Order Tracking. A developer also reports that the MXWO object structure does not expose the field, so the nightly integration cannot populate it. The desktop users see no field, and no error is logged. The administrator did not use admin mode, and two other administrators were logged in during the change. The environment has a single JVM and no cluster. The customer segmentation pilot starts in two days.
1. What metadata and cache checks would you perform first, and what would each result tell you?
Read the worked answer
Check the metadata layer in this order. In Database Configuration, confirm CUSTOMERSEGMENT exists on WORKORDER with the correct length, domain, and object name. Then confirm Apply Configuration completed successfully; a restart alone does not prove the metadata was applied. Because other administrators were logged in and admin mode was not used, look for blocked or incomplete configuration changes and check whether the attribute exists in the metadata tables used by the application.
If the attribute exists in Database Configuration but not in Application Designer, suspect an application cache that has not reloaded or an incomplete apply. If it appears in Application Designer after a reload but not in MXWO, the desktop metadata is fine and the object structure needs attention. If it appears nowhere outside Database Configuration, return to the apply step before touching Application Designer or the integration.
2. What is the correct order of changes for desktop, mobile, and integration?
Read the worked answer
Use a controlled order so each layer sees the previous layer. First create or validate the CUSTSEG domain. Second add CUSTOMERSEGMENT to WORKORDER in Database Configuration with the correct type and domain. Third enter admin mode, run Apply Configuration, and confirm success before restarting or reloading caches.
Fourth add the control to Work Order Tracking in Application Designer, bind it to the domain, and test as a normal user. Fifth regenerate or update the MXWO object structure so the attribute is included, then refresh the enterprise service or publish channel that depends on it. Sixth configure the mobile channel if it uses a separate object structure, and test a round trip. Do not skip the object-structure step just because the desktop field is visible; integration metadata is separate.
3. The desktop field appears after a cache reload, but MXWO still omits it. What is the likely cause and fix?
Read the worked answer
The likely cause is that MXWO was not regenerated after the WORKORDER attribute was applied. Object structures keep their own attribute lists, so a new WORKORDER attribute does not automatically appear in every structure. Open the MXWO object structure, inspect its attributes for CUSTOMERSEGMENT, and regenerate or update it. Then check whether the integration uses MXWO or a custom structure; if it uses a custom structure, the same update is needed there.
After regeneration, refresh the enterprise service or integration cache and replay a test message that includes CUSTOMERSEGMENT. Confirm the value is persisted and visible on the work order. If the structure still omits it, check for an exclude rule or a processing rule that filters attributes. Document the order of operations: database attribute, apply configuration, application control, object structure, integration refresh.