Batch Sharing Overview

Batch sharing is performed at the build list level; that is, when you use batch sharing, you select a build list on which to perform batch sharing, and only objects in the build list are considered as candidates for sharing.

In project preferences, you can specify “Matching Criteria” for batch sharing. These criteria are used to group non-shared objects together so that they become instances of the same shared object when you share them using batch sharing. The matching criteria are also used to decide if non-shared objects should become instances of existing shared objects when you share them use batch sharing. All the existing 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.

Batch sharing is not available for non-shared objects that match an existing shared object that is frozen, or for non-shared objects that match multiple existing shared objects. Additionally, you can only share objects into an existing shared object in the following scenarios:

• There is only one revision of the shared object. (In this case, you can share objects into the existing shared object even if it currently does not have any instances placed on designs in the build list you are performing batch sharing on.)

• There are multiple revisions of the shared object but only one revision has instances placed on designs in the build list you are performing batch sharing on.

Note

You cannot share objects into an existing shared object that has multiple revisions if none of the revisions have instances placed on designs in the build list you are performing batch sharing on. To share objects into such a shared object, you must add an instance of the shared object into a design in the build list. You can place an instance of an existing revision of the shared object, or create a new revision and place an instance of that.

Once you have selected which objects o share and clicked Share in the Batch Share Dialog Box, the following considerations determine whether or not the selected objects can actually be shared:

• If any option, attribute or property conflicts exist between objects that would become instances of the same shared object, sharing will not proceed.

• If sharing would create a new shared object with the same name as an existing shared object, sharing will not proceed.

• If you are sharing objects into an existing shared object that is non-editable due to restrictions such as read-only domains, sharing will not proceed.

• For Multicores and Overbraids, objects that are matched (according to the matching criteria) must meet the following requirements in order for sharing to proceed:
  
  The matched objects must all be the same type of multicore or overbraid and must have the same type of indicators. For example, a shielded multicore with coax indicators cannot be shared into a shielded multicore with oval indicators.
  
  The inner core structures of the matched objects must be the same. For example, a multicore that has only two wires as its inner cores cannot be shared into a multicore that has three inner core wires. If the inner cores are themselves multicores, their type, indicators and structure must also be the same, otherwise sharing will not proceed. There is one exception to this rule: for overbraids, the presence or absence of shield terminations is not subject to this requirement - that is, overbraids can be shared into each other regardless of whether they have shield terminations.
  
  The names of the inner cores of the matched objects must match. For example, a multicore with two wires, named WIRE1 and WIRE2, cannot be shared into a multicore with wires named WIRE3 and WIRE4. There is one exception to this rule: the names of shield terminations do not have to be the same.
  
  If the multicore or overbraid has a library part number, all inner cores must be placed.

• Sharing will not proceed if merging pins would cause an instance of a pin to violate the pin's pin reservation status. This can happen if a reserved pin on an existing shared object has the same name as a pin on a non-shared object that is being shared into the existing shared object, and the two objects are placed on different designs.

The results of the batch share action are displayed in the Batch Share tab in the Output Window. For objects that could not be shared the Severity field indicates (error). You can click the hyperlinks in the Object column to navigate to the objects that could not be shared.

Note

You cannot access the Batch Share dialog box if any of the designs in the build list are open. When you right-click a build list and select Batch Share, if any designs in the build list are locked by another user a message in the Batch Share tab in the Output Window tells you which user has the lock on the design.

Parent Topic:

Batch Sharing

Capital Logic Designer User Guide, 2512

Unpublished work. © 2025 Siemens