Modifying Objects

Batch Share Match Criteria

During batch sharing, the batch sharing match criteria are used to determine which non-shared, design-wide objects should become instances of the same shared object, and also to determine which non-shared, design-wide objects should become instances of existing shared object revisions.

You specify the matching criteria in the Project Preferences Dialog Box. The two types of matching criteria are object attributes and object properties. For each type of object, you can specify which attributes and properties should be used as matching criteria.

Use of Match Criteria During Batch Sharing

When you use batch sharing, the matching criteria are used to:

Match non-shared objects with each other When matching is performed, for each object type, objects that have the same values for each of the matching criteria are grouped together, and will become instances of the same shared object if you complete the batch sharing procedure.
Match non-shared objects with existing shared objects If any existing shared objects have the same values for each of the matching criteria as one or more non-shared objects, only the Share Into option will be available for those non-shared objects in the Action column in the Batch Share Dialog Box. If you complete the batch share procedure, those non-shared objects will become new instances of the existing shared object.

Note

When matching is performed, all the shared objects in the project are considered, including shared objects that do not have instances placed on designs in the build list that you are performing batch sharing on.

When properties are used as matching criteria, property type is not considered. For example, an integer property with value 1 and a string property with value “1” are considered to match.

Examples

By default, signals and messages are identified as candidates for the batch share action by use of their Name attributes. For example:

Figure 17: Batch Share Signal Attribute Example

If a non-shared signal has the same Name value as another non-shared signal, then they are candidates for creating one new shared signal.
If a non-shared signal has the same Name value as an existing shared signal, then it is a candidate to be shared into that existing shared signal.
The same applies when matching messages by use of the Name attribute.

In the following example, messages are identified as candidates for batch share by use of their ‘Dictionary Message Name’ and ‘Dictionary Message Revision’ attributes.

Figure 18: Batch Share Message Attributes Example

That means:

If a non-shared message has the same ‘Dictionary Message Name’ and ‘Dictionary Message Revision’ values as another non-shared message, then they are candidates for creating one new shared message.
If a non-shared message has the same ‘Dictionary Message Name’ and ‘Dictionary Message Revision’ values as an existing shared message, then it is a candidate to be shared into that existing shared message.

Parent Topic:

Modifying Objects