Modifying Objects

Batch Sharing Objects in a Function Build List

You can use batch sharing to share multiple objects at the same time. When you have a large number of objects to share, using batch sharing is quicker than sharing each object individually. 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.

For users importing their functional designs from SysML tools, this functionality simplifies the process of detecting and sharing signals and messages that are created from flow properties or connectors connected to the Internal Block Diagram (IBD) frames.

Restrictions and Limitations

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.
You cannot perform a “share into” action for unplaced objects.
Once you have selected which objects to 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. 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.

Prerequisites

You must have created the function build list containing the relevant functional designs. The designs can be ones that you have imported from SysML tools or ones in Capital that contain design-wide objects that you want to share. Note The Batch Share action will be disabled if a build list does not contain any designs.
You must have specified batch share match criteria in the project preferences for Capital Systems Modeler. These criteria specify the attributes and properties used to match the signals and messages that are candidates for sharing. See Batch Share Match Criteria for an overview and examples.
You must save and close any open designs.
The designs in the build list to perform batch sharing on must not be locked by other users.

Procedure

In the Project Browser Window on the top left of Capital Systems Modeler or Capital Systems Architect, right-click the function build list that contains the designs in which you want to share signals and messages. Choose Batch Share.
If you have any open designs, the Batch Share message box is displayed to save and close the designs. To continue, click Save & Close.

The Batch Share dialog box displays and lists non-shared, design-wide objects (signals and messages) that have matching values for the batch share criteria that you specified.

Note See Batch Share Dialog Box for details of the various filters that you can apply to the list and the information that you can view for the design-wide objects in that dialog box. If you have imported designs from SysML tools (see Importing a Design from a Systems Modeling Language Project), you may want to toggle whether the table displays only signals and messages with just one end connected .
In the Display section, ensure that the object type buttons for the objects to share are selected.
In the Selection column, select the design-wide objects that you want to share or share into an existing shared object revision.
(Optional) Click the Add columns () button to display additional attribute / property and design abstraction information to help make your selections.

Note You can click the View Details expander () to display port details and the attributes and properties of the object selected in the table. For objects that will become instances of existing shared objects (indicated by the value in the Action column being “Share Into” and being non-editable), if you hover over the cell in the Action column, a tooltip indicates which existing shared object, and which revision of that shared object, the object will become an instance of.
If you have selected objects from a group of matching non-shared objects that have no matching existing shared object, use the dropdown lists in the Action column to select which object will be shared to create a new shared object, and which will be shared into that new shared object.

Click Share.

             A Confirm Batch Share message displays and confirms how many objects will be
                 shared.

Click Continue & Save.

Results

In the Output Window, the Batch Share tab displays:

If an object was shared successfully the Message column shows whether the object was shared or shared into, the Design column shows the source design of the object that was shared and the Object column shows the object that was shared.

If an object could not be shared:

The Severity column indicates (error).

The Message column gives the reason sharing could not proceed.

The Design column shows the design into which the object could not be shared.

The Object column shows the object that could not be shared, unless the design in the Design column could not be accessed, in which case the Object column will be blank.
Objects that have been shared and those that have been shared into an existing shared object revision. For each, it tells you the design where it is located and provides a hyperlink that you can click to zoom to it in the diagram window.

Typical errors where Batch Share is unable to share objects are:

                      In the case of conflicting attribute or properties, check that values
                          match on the design-wide object to be shared and the target shared
                          object revision.

                  

                  
                      In the case of conflicting signals included in a message, check what
                          active signals are included in the message to be shared and in the
                          target shared message revision.

                  

                  
                      In the case of unplaced objects, you must place them.

Note

The property SYSML GUID is a special property that exists on all signals and messages that are imported from Rhapsody. This property will have different values on different instances of non-shared, design-wide objects. However, this is a read-only property. Similarly to all read-only properties, the Batch Share action will not report conflicts in the values of the SYSML GUID property. The action will retain the property value from the one selected as ‘Share’, if there is no existing shared object revision matching the criteria. The action will retain the existing value on the shared object if there is an existing shared object revision matching the criteria.

Parent Topic:

Modifying Objects