In order to perform changes in a lower configuration, items or documents must first be claimed or revised into that configuration. This claim can be performed interactively in the Desktop Client.
When you create new objects, or make changes to existing objects, this is done in the context of a create configuration. Before you can claim an item from one configuration into a lower configuration, you must first query for that item in the context of the lower configuration. This ensures that you have the most relevant configuration version of the object to work with.
When you run a query, the objects are retrieved into a list view that identifiers the query configuration, and all objects retrieved by this query have the query configuration recorded on the object. This ensures that the object selected for claim is not in a parallel or lower configuration than the active create configuration.
You must set the create configuration before you can run a query.
Conditional control for Claim method
The claim is initiated by a multi-select right-hand click method that is only available when the following conditions are met:
-
The class definition of the object is not configuration independent
-
The query configuration set for the object (QueryConfig property) matches the current create configuration
-
The current configuration of the object (CurrentConfig property) matches the current create configuration
-
The IsClaimExclusive flag on the object is set to False
-
The class definition of the object is claimable
This method ensures that the selected objects have been queried in the active create configuration, so do not already exist in the create configuration, and have not been exclusively claimed elsewhere.
Before using concurrent engineering, you should be familiar with the following types of claims:
-
Implicit claims - It is possible to implicitly claim items from the plant into an active project configuration when running commands that update these objects.
-
Explicit claims - The system can be set up for explicit claiming to force all users to claim objects, manually, before they can be edited.
-
Exclusive claims - Items can be exclusively claimed preventing them from being modified in another parallel configuration. The system can be set up to force all users to work in exclusive mode.
-
Non-exclusive claims - When working in a non-exclusive mode, parallel changes can be made to the same item. As a result the design basis of a claim may be changed by data merged from another parallel configuration or a change made to the design basis itself in a higher configuration. This makes the design basis of the first claim out of date.
Documents
Documents are claimed into a configuration by revising them, and as such they can only be explicitly claimed.
It is not possible to revise a document into a configuration and skip an intermediate configuration on the way. For example, you cannot revise a document from the plant configuration directly into a change configuration that is found below the project. You must first revise the document from the plant in to the project, sign off the revision in the project, and then revise it down into the change configuration below the project.
A document must be signed off before it can be claimed.