vsmStudio - Signal Paths

Available Columns:

• "Signal Path Name": The system wide unique identifier name that is set when the Signal Path is created.
• "VM": Shows the location of the Signal Path on the Primary Virtual Matrix layer.
• "Layer": Shows the physical layer that the Signal Path is assigned to.
• "Moor": Shows the configured ID/ position of the Signal on the respective physical layer. The abbreviations “S:” or “T:” as well as the background color of the respective row indicate if the Signal Path is configured as Source (purple) or Target (green).
• "Pool": Indicates if the Signal Path is assigned to a Pool. The respective Pool name is displayed (related to “Pooling”).
• "Source Tag": Future function.
• "Target Tag": Future function.
• "Info": Indicates if the Signal Path contains secondary functions or is “synced” with another Signal Path.
• "Fam.": Shows the assigned Signal Family.
• "Label Parent": Indicates if the label is derived from another Signal Path. The identifier label of the respective Signal Path is displayed.
• "Primary": Shows the primary label, set for the Signal Path. (Displayed label may be switched between Default and User label, dependent on the top selection of the window.)
• "Secondary A": Shows the Secondary A label, set for the Signal Path. (Displayed label may be switched between Default and User label, dependent on the top selection of the window.)
• Secondary B, Protocol, and following columns are further label levels per Signal Path.

All Label levels, except the Identifier (=Signal Path Name), can be renamed which may change the appearance/headlines of the respective columns. Only named label levels appear as columns in this view. Some label levels may be used for incoming external label information via protocol, depending on their ID.

It is possible to modify or add labels to Signal Paths in the Assignment view, except the Identifier (=Signal Path Name). To do so, select a Signal Path, click into the respective cell, and add or overwrite the label accordingly.

To modify the label for multiple Signal Paths, within the same column, select the respective cell of the first Signal Path, hold down shift and select the cell of the last Signal Path. Now you can enter a label in the first cell and quickly jump to the respective cell of the following Signal Path by just hitting Enter on your keyboard.

Available Columns:

• "Signal Path Name": The system wide unique identifier name that is set when the Signal Path is created.
• "VM": Shows the location of the Signal Path on the Primary Virtual Matrix layer.
• "Layer": Shows the physical layer that the Signal Path is assigned to.
• "Moor": Shows the configured ID/ position of the Signal on the respective physical layer. The abbreviations “S:” or “T:” as well as the background color of the respective row indicate if the Signal Path is configured as Source (purple) or Target (green).
• "Label": Shows any assigned Primary Label.
• "Bandwidth": Shows the configured Network Bandwidth (related to SDN configuration).
• "Essence": Shows the selected Media Essence Filter.
• "SDP A": Shows the assigned, primary SDP parameter.
• "Host A": Shows the primary Host IP address.
• "Multicast A": Shows the primary Multicast IP address and Port.
• "Interface A": Shows the primary Network Switch Port (related to SDN configuration).
• "SDP B": Shows the assigned, secondary SDP parameter.
• "Host A": Shows the secondary Host IP address.
• "Multicast A": Shows the secondary Multicast IP address and Port.
• "Interface A": Shows the secondary Network Switch Port (related to SDN configuration).

Available Columns:

• "Signal Path Name": The system wide unique identifier name that is set when the Signal Path is created.
• "Primary Source": Shows the current connected Source of Target.
• "Primary Source[Internal]": Shows the current connected Source of Target.
• "Layer": Shows the physical layer that the Signal Path is assigned to.
• "Moor": Shows the configured ID/ position of the Signal on the respective physical layer. The abbreviations “S:” or “T:” indicate if the Signal Path is Source (purple) or Target (green).

1. Set a Description name for the new Signal Path(s). Each Signal Path name must be unique within one vsmStudio configuration and is used and displayed as the Identifier label in all other dialogues. Multiple Signal Paths can be created in one go by using Iterators. A pop-up window with examples shows when hovering with the cursor over the Description textbox. 
2. Alternative to the use of Iterators in the Description field, you can also manually set the Amount of Signal Paths to be created. Consecutive numbers will be automatically added to the set Description name.
3. A Preview of the resulting Signal Paths that will be created is displayed.
4. Location is an optional, informative text field for the user.
5. Comment is an optional, informative text field for the user.

6. Signal path Family is an optional setting. Mainly informative for the user. Assigning Families also provide the possibility to sort respective Signal Paths in the respective Signal Path list, as well as in Matrix views. 

    See here how to configure Signal Path Families.

   • Select an existing Signal Path Family (1) from the pull-down menu or enter the editor via "Modify" (2).
   • Edit an existing Signal Path Family by selecting and clicking "Edit" (3) or create a new one by clicking on "New Family" (4).
   • Assign a "Name" (5) and "Short" name (6) for the Signal Path Family and select a background color (lower arrow) and text color (upper arrow) (7). The selected color scheme will only be visible in Matrix views. Confirm with "OK".
   • Select the desired Signal Path Family from the list and confirm with close (8).

   

7. Conflicts will show if any of the resulting Descriptions/Identifiers are already existing within the current vsmStudio configuration. Please make sure to correct the Description accordingly until no Conflicts are displayed anymore.
8. Navigation controls. Proceed to the next step with "Next" or in Edit mode proceed with "Cancel", "Apply" or "OK".

1. Signal Type Standard Signal Path: As its name implies, this is the standard Signal Path type, to be selected for any physical Signal representation, no matter if baseband or network resource. 

    Standard Signal Path detail

   Standard Signal Paths may represent a Source, a Target or even both. An example for a Standard Signal Path with Input and Output would be the representation of a loop-through resource like a Framesynchronizer where, the Signal at the output of the Device is, aside the processing, always the same Signal that was fed into the Device.

   • Before being able to make any Connections in this view, the respective Layers need to be created and will be listed in this view accordingly.
   • When creating a Signal Path representation of a physical crosspoint matrix, the location ID which is selected on the respective layer in vsmStudio, needs to match the appropriate location ID within the device configuration and the respective control protocol.
   • When creating Signal Path representations of Network Stream essences, the location ID which is selected on the respective layer in vsmStudio, has no specific hardware dependency and therefore can be freely chosen.
   • Click in the respective Input or Output cell of the respective layer row and select the ID to be assigned.
   • An assignment can be reverted by selecting the blank field, top left of the selection pop-up, in front of "V".
   • When creating multiple Signal Paths in one go, based on the Iterator or Amount setting in the Information view, please note that you only have to select the first ID and the system automatically will allocate the following IDs, up to the total amount of Signal Paths that is required. If the required slots are all or partially already in use, this error will be indicated with a red marker (1). Although you may be able to proceed to the following views, the overall Signal Path creation process cannot be finalized. In this case please first check your configuration and/or your settings in the Information view.
   • Optionally you can drop a GPIO trigger for a Signal Path "Hard Lock" (2), "Disable (and Blind) Target or Tie-Line" for Targets (3) or "Disable Source" for Sources (4).
   • Proceed to the next step with "Next" or in Edit mode proceed with "Cancel", "Apply" or "OK" (5).

   

   

   A dedicated "Blind" Signal Path is mandatory to be created for each router layer. On physical routers usually a Video Black or Audio Mute Source signal is defined as "Blind" Signal. On Network Layers, any Source ID may be chosen and defined as "Blind" Signal. Devices that provide an Ember+ interface may provide an internal Disconnect Source. In this case please select "D/C" instead of any other ID from the selection window. In addition the specific "Blind" attribute has to be set in the following "Attributes" window/tab.

2. Signal Type Virtual Signal Path: Virtual Signal Paths may be used, e.g. as an abstraction layer between physical resources and their production and workflow related usage. Virtual Signal Paths are also a great helper tool for any kind of workflow and business logic, without any dependency on physical resources. Virtual Signal Paths are independent of the size of any physical layer and can even be used across Tie-lines to transfer assignments across physical layers. Virtual Signals with "Blind", or no physical assignment on their Input leg are displayed with square brackets [ ] around the Signal name on Panels and UMDs. "Empty" Virtual Signal Paths cannot be routed to Signal Path Targets.

    Virtual Signal Path detail

   Virtual Signal Paths are usually set-up with an Input and Output, like a loop-through resource. This allows them to be assigned to physical signals dynamically and basically being "inserted" in any workflow.

   • Before being able to make any Connections in this view, any Layer needs to be created, that will be listed in this view accordingly.
   • Virtual Signal Paths have no physical dependencies as such, so no specific location ID is required to be configured but only the layer reference, that the Virtual Signal is supposed to be used with in context.
   • Click in the respective Input or Output cell of the respective layer row and assign it with "V". The Virtual Signal assignment is indicated with a yellow fill color (1).
   • If there are any Tie-Lines configured between layers, these "second layers" are indicated by a pale yellow fill color (2).
   • An assignment can be reverted by selecting the blank field, top left of the selection pop-up, in front of "V".
   • Optionally you can drop a GPIO trigger for a Signal Path "Hard Lock" (3), "Disable (and Blind) Target or Tie-Line" for the Target leg (4) or "Disable Source" for the Source leg (5).
   • Proceed to the next step with "Next" or in Edit mode proceed with "Cancel", "Apply" or "OK" (6).

   

   

   Please note: A direct physical crosspoint has a higher priority than the same assignment routed via a virtual-physical crosspoint. Therefore, a physical crosspoint will always overwrite a virtual-physical crosspoint.

3. Signal Type Tie-Line: vsmStudio offers an integrated, dynamic Tie-Line management. For switch requests across routers, the dynamic Tie-Line management looks for a free Tie-Line and connects the respective Source and Target accordingly. If the requested Source was already assigned to a Tie-Line based on a previous action, this same Tie-Line will be used and no new Tie-Line will be allocated. Label and Tally information are concealed and transferred through Tie-Lines. In case that all Tie-Lines are already in use, new route requests between the respective layers cannot and will not be executed. On panels this is indicated by a remaining red Source button. Tie-Lines may also be cleared manually by user action via a panel. Instead of a dynamic usage, Tie-Lines may be Preassigned on their Source side to allow specific Source Signals being available via Tie-Line at any time while their usage on targets is still managed on request by VSM. To set up a Preassigned Tie-Line, the respective attribute has to be checked (3a).

    Tie-Line detail

   Tie-Lines represent a physical connection between two layers, e.g. two Routers. Therefore they have an Input leg on one layer and the Output leg on a different layer.

   • Before being able to make any Connections in this view, the respective Layers need to be created and will be listed in this view accordingly.
   • The location ID, which is selected on the respective layer in vsmStudio, needs to match the appropriate location ID within the device configuration and the respective control protocol.
   • Click in the respective Input (1) or Output (2) cell of the respective layer row and select the ID to be assigned.
   • An assignment can be reverted by selecting the blank field, top left of the selection pop-up, in front of "V".
   • When creating multiple Tie-Lines in one go, based on the Iterator or Amount setting in the Information view, please note that you only have to select the first ID and the system automatically will allocate the following IDs, up to the total amount of Tie-Lines that is required. If the required slots are all or partially already in use, this error will be indicated with a red marker. Although you may be able to proceed to the following views, the overall Tie-Line creation process cannot be finalized. In this case please first check your configuration and/or your settings in the Information view.
   • For Tie-Lines only, Input and Output cells will be marked with a purple border color.
   • Optionally you can drop a GPIO trigger for the "Disable (and Blind) Target or Tie-Line" for Targets (3) function and/or set a time for "Blind unused after" (4).
   • Proceed to the next step with "Next" or in Edit mode proceed with "Cancel", "Apply" or "OK" (5).

   

   

   A dedicated "Blind" Signal Path is mandatory to be created for each router layer. On physical routers usually a Video Black or Audio Mute Source signal is defined as "Blind" Signal. On Network Layers, any Source ID may be chosen and defined as "Blind" Signal. Devices that provide an Ember+ interface may provide an internal Disconnect Source. In this case please select "D/C" instead of any other ID from the selection window. In addition the specific "Blind" attribute has to be set in the following "Attributes" window/tab. Without "Blind" signal, Tie-Lines cannot be cleared and the status of the Tie-Line with respect to its recipients cannot be reported properly!

   

   Please note that Tie-Lines cannot be connected directly, e.g. via a Matrix view. The system prevents this action as the allocation is exclusively handled by VSM.

4. Signal Type Bridge: Future Option including the additional attribute Bridge Identifier (4a).
5. Concealed: If the option Concealed is checked, the label of this specific Signal Path will not be displayed as Source of Target on Panels and UMDs. Instead, the label of the preceding Source in the Signal Path chain will be displayed. This option is applicable for Signal Paths with Source and Target side.
6. Signal Path Input: Shows the Physical location ID on the respective layer. The Input of a Device/Resource = A Target from a Router perspective and in vsmStudio.
7. Signal Path Output: Shows the Physical location ID on the respective layer. The Output of a Device/Resource = A Source from a Router perspective and in vsmStudio.
8. Layer Name: Shows the respective layer name, the Signal Path is assigned to.
9. Hard Lock: Applicable for Target Signal Paths only. A GPIO can be dropped into the drop-zone. As long as this condition is true, the respective Target Signal Path will be operationally locked to its current Source and cannot be switched anymore. Can only be unlocked again if Hard Lock trigger gets false.
10. Disable (and Blind) Target or Tie-Line: Applicable for Target Signal Paths and Tielines only. A GPIO can be dropped into the drop-zone. Once this condition becomes true, the respective Target Signal Path will be automatically switched to its layers Blind Source, will be operationally locked and cannot be switched anymore. Can only be unlocked again if the trigger gets false.
11. Disable Source: Applicable for Source Signal Paths only. A GPIO can be dropped into the drop-zone. As long as this condition is true, the respective Source Signal Path will be operationally locked and cannot be switched anymore. Existing Crosspoints containing this source will remain in place and functional until switched. Can only be unlocked again if the trigger gets false.
12. Blind unused after: Related to Tie-Lines only. If a Tie-Line was used by the system once, the respective Source assignment will remain in place. Even if no Target requests the specific source anymore. Aside of the option to manually free up Tie-Lines via user panels, The "Blind unused after" function allows for a timed, automated clean-up where the Tie-Line would get freed up if not used for the specified timeframe..  
13. Navigation controls. Proceed to the next step with "Next" or in Edit mode proceed with "Cancel", "Apply" or "OK".

1. No loopback: This attribute is checked by default. It prevents that this Signal Path is switched onto itself. 
2. Is "Blind" Signal Source: A dedicated "Blind" Signal Path is mandatory to be created for each router layer. On physical routers usually a Video Black or Audio Mute Source signal is defined as "Blind" Signal. On Network Layers, any Source ID may be chosen and defined as "Blind" Signal. In addition, this attribute has to be set. One "Blind" Signal per layer only!
3. Is "Cardinal" Source: If this attribute is set on a Signal Path Source allows the system to identify and locate this Source via "Dynamic Attachment Scripts". The cardinal attribute is used to mark signals that have a special significance to the workflow making it easier to locate them with DAS.
4. Cardinal Identifiers: An optional attribute that can be used in combination with the Is "Cardinal" Source attribute for even more granular system identification via "Dynamic Attachment Scripts". Multiple Identifiers are possible to be set for the same Signal Path that then allow DAS to find this Source by any of its defined Cardinal Identifiers.
5. "Talk Back" Source: If this attribute is set on a Signal Path Source it allows to toggle between this and the previous Source of the selected Target, by simply selecting this "Talk Back" Source Source again.
6. 4-Wire*: This attribute requires in addition a specific Pseudo Device rule (Ports) and, in combination, allows for a 4-Wire switching behavior.
7. Check this box to define that the Signal Path Target can only be switched to source when it is currently connected to a Blind Source. Only applicable on Signal Path Targets.
8. ...or if Source is currently unused**. An optional attribute that can be used in combination with Target can only be switched to source when connected to a Blind Source. Only applicable on Signal Path Targets that are located on 1:1 layers.
9. Connecting the already connected source again returns to Blind Source allows to toggle between a Source and the defined Blind Source.
10. Invert "1:1 switch behavior" on Source: This attribute has to be used in combination with Invert "1:1 switch behavior" on Target. In combination, all Signal Path marked with this attribute will switch and behave like resources on an 1:1 router.
11. Invert "1:1 switch behavior" on Target: This attribute has to be used in combination with Invert "1:1 switch behavior" on Source. In combination, all Signal Paths marked with this attribute will switch and behave like resources on an 1:1 router.
12. Any source switched to this target is placed into queue: This attribute is required on any Signal Path Target that is intended to be used in combination with the Panel function "Queue Control". Only applicable on Signal Path Targets.
13. Disable CPC (where applicable): Only applicable on Network Signal Path Targets. This attribute may be used if it is intended that the respective Target can be switched from a 3rd control instance or within an end-device itself.
14. Has Access to Head Pool: Only applicable on Signal Path Targets and in combination with the "Distributed Multi Viewer" module. Head Pools have to be created beforehand in the "Monitor Management" section and then be selected accordingly via the drop-down menu.
15. Conflicts: will show if any of the resulting Descriptions/Identifiers are already existing within the current vsmStudio configuration. Please make sure to correct the Description accordingly until no Conflicts are displayed anymore.
16. Navigation controls. Proceed to the next step with "Next" or in Edit mode proceed with "Cancel", "Apply" or "OK".

This section contains all specific settings to configure Network Source Signal Paths.

1. The window is divided in two sides, one for Red Network Information Provision and one for Blue Network Information Provision. Dependent on the Network system and controlled device, even in -7 there may be no need to enter any separate information on the Blue Network Information Provision. For instance, if the primary and secondary Stream information may be embedded within onea single SDP Parameter.

2. You can drag the SDP from Device from the respective node in the Gadget tree and and drop it here.

    More detail

   

3. Optionally the Essence pre Augment Filter settings can be set. Please refer to the respective Media Essence Filter documentation for further details.
4. Alternative to the direct assignment of a SDP parameter, a valid SDP by User can be manually pasted.
5. This section may show the SDP by User or SDP information provided via the SDP from Device.
6. If the connected device does not provide any SDP information but only separate Network information, here you can either drop the respective Parameter or enter a static Host Address.
7. If the connected device does not provide any SDP information but only separate Network information, here you can either drop the respective Parameter or enter a static Multicast Address.
8. If the connected device does not provide any SDP information but only separate Network information, here you can either drop the respective Parameter or enter a static Multicast Port.
9. For SDN application only, the Network Bandwidth is specified here. Please refer to the specific Arista CVX interface documentation for further details.
10. For SDN application only, the Switch is specified here. Please refer to the specific Arista CVX interface documentation for further details.
11. For SDN application only, the Interface (Switch Port) is specified here. Please refer to the specific Arista CVX interface documentation for further details.
12. For SDN application only. The Chassis ID, as provided via the online Arista CVX will be displayed here. Please refer to the specific Arista CVX interface documentation for further details.
13. For SDN application only. The Port ID, as provided via the online Arista CVX will be displayed here. Please refer to the specific Arista CVX interface documentation for further details.
14. For SDN application only. Here you can define if the controlled resource is "Moveable". Please refer to the specific Arista CVX interface documentation for further details.
15. Navigation controls. Proceed to the next step with "Next" or in Edit mode proceed with "Cancel", "Apply" or "OK".

This section contains all specific settings to configure Network Target Signal Paths.

1. The window is divided in two sides, one for Red Network Information Provision and one for Blue Network Information Provision. Dependent on the Network system and controlled device, even in -7 there may be no need to enter any separate information on the Blue Network Information Provision. For instance, if the primary and secondary Stream information may be embedded within one single SDP Parameter.
2. If the connected device supports a direct SDP Parameter to receive Stream data, but only separate Network information, here you can either drop the respective Parameter or enter a static Host Address.

3. If the connected device supports a direct SDP Parameter to receive Stream data, select the operational mode SDP, then drag the SDP parameter from the respective node in the Gadget tree and and drop it here (1).

    More detail

   

4. Optionally the Essence pre Augment Filter settings can be set. Please refer to the respective Media Essence Filter documentation for further details.
5. If the connected device does not support a direct SDP Parameter to receive Stream data but separate Stream information, select the operational mode Multicast.
6. If the connected device does not support a direct SDP Parameter to receive Stream data but a Source Host parameter, you can drag this parameter from the respective node in the Gadget tree and and drop it here.
7. If the connected device does not support a direct SDP Parameter to receive Stream data but a Multicast Connect IP and Port parameter, you can drag these parameters from the respective node in the Gadget tree and and drop it here.
8. If the connected device does not support a direct SDP Parameter to receive Stream data but a Multicast Feedback IP and Port parameter, you can drag these parameters from the respective node in the Gadget tree and and drop it here.
9. If the connected device does support a Take parameter, you can drag this parameter from the respective node in the Gadget tree and and drop it here.
10. If the connected Device Supports Internal Loopback, please check this option accordingly.
11. For SDN application only, the Network Bandwidth Limit is specified here. Please refer to the specific Arista CVX interface documentation for further details.
12. For SDN application only, the Switch is specified here. Please refer to the specific Arista CVX interface documentation for further details.
13. For SDN application only, the Interface (Switch Port) is specified here. Please refer to the specific Arista CVX interface documentation for further details.
14. For SDN application only. The Chassis ID, as provided via the online Arista CVX will be displayed here. Please refer to the specific Arista CVX interface documentation for further details.
15. For SDN application only. The Port ID, as provided via the online Arista CVX will be displayed here. Please refer to the specific Arista CVX interface documentation for further details.
16. For SDN application only. Here you can define if the controlled resource is "Moveable". Please refer to the specific Arista CVX interface documentation for further details.
17. Navigation controls. Proceed to the next step with "Next" or in Edit mode proceed with "Cancel", "Apply" or "OK".

1. Label level ID: Up to 32 Label levels may be used per Signal Path.  ID08, 09 and 10 are reserved to receive Labels from external, e.g. via Probel sw-p-08 protocol.
   • ID00 is dedicated to the unique Signal Path Label. 
   • ID01 is the Primary label displayed on Panel buttons and UMDs. If no Label is set for ID01 Primary, the Identifier will be shown on Panel buttons and UMDs.
2. Usage level: Name to indicate the specific Usage per Label level. All names, except Identifier, are customizable. "Identifier" is locked and dedicated to the unique Signal Path Label and identity. All and only labeled Usage levels are displayed as Columns in Signal Path list and are selectable in any Displayed-Label-Selector drop-down menu within other views.
3. User Label: Customizable Label, that can be set in this view, via the Signal Path list and also via Panels. The User Label is displayed on Panel buttons and UMDs with a higher priority than the Default Label. Since the Label for ID00 Identifier has to be unique and identifies the Signal Path as such, it is static and can only be set in the Information tab.
4. Default Label: Customizable Label, that can be set in this view and via the Signal Path list. The Default Label is displayed on Panel buttons and UMDs with a lower priority than the User Label. Since the Label for ID00 Identifier has to be unique and identifies the Signal Path as such, it is static and can only be set via the Information tab.
5. Overlay User with: In this cells, any of the 32 Usage levels other than the currently edited, can be selected via drop-down menu. The User Label content of the so selected Usage level will then overlay the User and Default Label of the currently edited Usage level.

6. Reflect from: This feature may be used on Signal path Sources. In this cells, any of the 32 Usage levels can be selected via drop-down menu (1). The respective local Source User Label will be reflected from the currently connected Signal Path Target and replaced accordingly, if the Label cells on the respective Usage level on the Target side are not blank.

    More detail

   

7. Match: This feature may or may not be used on Signal Path Targets in combination with the Reflect from feature on Signal Path Sources. In these cells you can select the following conditions via drop-down menu (1) that may affect the switching behavior.

    More detail

   

   • == Equals: The selected Signal Path Target will only be connected with Signal Path Sources where the Label on the respective Usage level is existing and the same. 
   • != Not Equal: The selected Signal Path Target will only be connected with Signal Path Sources where the Label on the respective Usage level is blank or not the same. 
   • 0= Empty or Equal: The selected Signal Path Target will only be connected with Signal Path Sources where the Label on the respective Usage level is existing and the same. 

   • !0 Not Empty: The selected Signal Path Target will only be connected with Signal Path Sources where the Label on the respective Usage level is not blank.

8. Send/Receive Label: A Gadget Parameter from the "Gadgets" view may be dropped into the cells of this column, to write the User label from external or send the User label to an external device via protocol (1).

    More detail

   

9. Special character appendix &: If the assigned Label is started with this character (1), the system will Append this label to signal's source label (Only when first character). The resulting Label text is only visible and displayed on Panel buttons and UMDs, not within Matrix or Signal Path views.

    More detail

   

10. Special character set appendix %P%: By typing this character set in any of the Label cells (1), the respective label will be Substituted with inherited label from label parent (2). A label parent is defined by the Trigger signal of a Pseudo Device rule (3), the children are the respective attachments (4). Adding additional text behind this character set is still possible (5), e.g. to identify Audio Channel numbering added to the Label inherited from a Video Parent. The resulting Label text is only visible and displayed on Panel buttons (6) and UMDs, not within Matrix or Signal Path views.

     More detail

    

11. Special character set appendix %S%: By writing this character set in any of the Label cells, the respective label will be Substituted with the signal's source label. Adding additional text behind this character set is still possible, e.g. to display the current Source label in combination with the local Target Label. The resulting Label text is only visible and displayed on Panel buttons and UMDs, not within Matrix or Signal Path views.
12. Navigation controls. Proceed to the next step with "Next".