Enterprise Routing Feature. Primary and secondary codes can be used to check off task completion results, mark upselling opportunities or track any other results you want reflected in your Power BI historical reporting.

(lightbulb) Aside from their naming, primary and secondary codes have no technical difference. You can define freely decide how you name them. 

(lightbulb) Codes can be accessed from either Nimbus Portal (Frontend) or the Administration (backend) UI.

Defining the list of available Cross Selling Codes

The related Use Case - Defining and using Codes shows the usage of codes context with other Nimbus features.

Primary and Secondary codes

(tick) Codes are configured via Configuration > Codes section. By clicking "Create New" you can add new primary or secondary codes → a dialogue will open to configure your new code.

  • Note that codes are Organization Unit specific, so Nimbus users will only see codes that are made available to their respective team.
  • Define a short code name. (lightbulb) This is how the entry will be shown in the Nimbus UI, e.g. when assigning the code to a service and using it in 
  • Add an optional description. (lightbulb) Will be used in listings and tables to tell the code apart.

    Creating a new code

Codes in reporting

  • Codes will be part of the OData interface used for historical Power BI reporting.
  • Removing codes deletes them from the Nimbus UI, preventing further selection, but existing codes in the reporting tables will remain unaffected.

Usage of codes

(tick) In order to use your defined codes they must be assigned within the individual service's settings. Afterwards they will e available (e.g. My Sessions view) by all Nimbus users of that service. As long as no codes are assigned 

Selecting previously defined codes in the UI