PLM Developer
Development

The Claim Mechanism in Aras Innovator: Why Your Edit Button Just Did Nothing

Letisha Luimes •
#locking#collaboration#troubleshooting#workflow#claims
Aras Innovator edit interface showing claimed items

When you click Edit on a Part in Aras Innovator and nothing happens, the silence can be more frustrating than an error message. This behavior typically indicates the item is already claimed by another user—a fundamental but often misunderstood aspect of Aras’ collaboration model that affects teams working with shared items.

Aras Innovator’s claim system provides lightweight locking to prevent edit conflicts, but its implicit nature can create confusion in multi-user environments. Unlike explicit check-out systems in other PLM solutions, claims are automatically created on edit attempts and persist until manually released. Understanding this mechanism is critical for maintaining smooth team workflows.

What You Will Learn

Resolving Silent Edit Failures

Identifying Claimed Items

Aras provides built-in filters to surface locked items. In any search grid:

  1. Click the filter icon in the grid header
  2. Select “Claimed by” from the filter dropdown
  3. Choose between:
    • “Me” (items you’ve claimed)
    • “Others” (items locked by teammates)
    • “Anyone” (all claimed items)
<!-- Example AML to find items claimed by current user -->
<Item type="Part" action="get" select="id,name">
  <claimed_by condition="eq">@0</claimed_by>
</Item>

Releasing Claims

For items you’ve claimed:

  1. Open the item and use either:
    • Done: Saves changes and releases claim
    • Discard: Reverts changes and releases claim

For items claimed by others:

  1. Request the claiming user release it via:
    • Their open edit forms (Done/Discard)
    • The Unclaim action in the item’s context menu
// Programmatic unclaim via IOM
var item = innovator.getItemById("Part", "A3A45B6C789D4E5");
item.unClaim();

Common Pitfalls

Key Takeaways

The claim system balances flexibility with collision prevention, but requires awareness of its persistence characteristics. For teams experiencing frequent claim conflicts, consider implementing custom UI indicators or supplementing with workflow-managed locks for mission-critical items. The Aras Community forums offer additional patterns for managing complex collaboration scenarios.

← Terug naar blog