If additional attributes are added to the Work View, how can they be automatically updated from changes made to a corresponding Ticket and Work Order fields?

Question

Options

• Aby modifying the existing Crossover Domains TKT2WV or W02WV
• Bby adding a Crossover Domain to TICKETID or WONUM
• Cby updating the existing Cron Task UpdateWorkView that has two instances TKT2WV and
• Dby modifying the existing Object Launch Point automation script UpdateWV

• A
  6% (1)
• B
  69% (11)
• C
  6% (1)
• D
  19% (3)

Explanation

Adding a Crossover Domain to the TICKETID or WONUM field is correct because, in IBM Maximo, Crossover Domains define how field values are automatically copied from a referenced object (Ticket or Work Order) into the current object (Work View) when the key linking field is populated. When you add new attributes to the Work View, you extend the mapping by adding new entries to the Crossover Domain attached to TICKETID or WONUM - this is the native, event-driven mechanism that triggers automatically on field selection.

Option A is wrong because TKT2WV and WO2WV are not standard Crossover Domain names in Maximo - the crossover configuration lives on the actual key fields (TICKETID/WONUM), not on standalone named domains. Option C is wrong because Cron Tasks are scheduled batch jobs, not real-time triggers - they would not automatically update records as changes occur. Option D is wrong because while Object Launch Points and automation scripts can respond to object events, UpdateWV is a distractor; the standard, configuration-based mechanism for field crossover is the Crossover Domain, not custom scripting.

Memory tip: Think of "Crossover" as values crossing over from one record into another - the crossing happens when the linking ID field (TICKETID or WONUM) is set, so that's exactly where the domain must live.

No community discussion yet for this question.