ServiceGrid Article - PossibleCallSystemMappings

From DocWiki

Jump to: navigation, search

Overview

Along with the new license management, there will be restriction on the configuration of mappings (Priority codes, CallStates, Severity codes, ...). For the new license management, you must specify which callsystems, you want to map before you can configure the mapping. To do this, you must switch to SD.basicdata > MyCompany. Select the company for which you want to edit the PossibleCallSystemMappings and then click on the node "> Setups > PossibleCallSystemMappings" of the tree on the left side. On the right side, a list of already existing PossibleCallSystemMappings appear. You can sort and filter the entries of the table as usual.

To change an existing PossibleCallSystemMappings click on the triangle at the beginning of the row and select Change Possible CallSystem Mapping master data. To create a new PossibleCallSystemMapping, you can use the top function Create new PossibleCallSystemMapping. In both cases, the following form is shown for editing the existing or new PossibleCallSystemMapping.

Snapshot possiblecallsystemmappings list-22071001.png


You can select the bridge type (Service, B2B, SD2), the CallSystem of the service provider, the CallSystem of the service customer and the company which pays (not necessary if bridge type is SD2). With the activation of the new license management, the selection of the CallSystems will be restricted to those for which a PossibleCallSystemMapping is defined with the current CallSystem as customer or provider, in all mapping configurations.


Bridge Types

The three different bridge types are:

  • B2B: This is default bridge type. Use this setting for Bridge connecitons, connecting one system outside SD with another system outside SD. Note that this also demands the paying company to be selected. That is, whose licensing agreement is affected by this bridge.
  • 'Service': Use this setting for Bridge connections where one partner user SD2, while the other partner uses a different system independently from SD. Note that this also demands the paying company to be selected. That is, whose licensing agreement is affected by this bridge.
  • SD2: Use this to map two workflows in SD2. This contains no bridge functionality.


For a complete list of Cisco ServiceGrid Articles, go to the List of Articles page.





Rating: 0.0/5 (0 votes cast)

Personal tools