For the list of all supported Decision Insight downloads and releases, see the Downloads page.

Dashboard browsing URL format

Introduction

As you work with Axway Decision Insight (DI), the browser URL is updated to reflect the current application state. Every time you navigate within DI, the browser URL is updated to reflect your current user context. This makes it very handy for bookmarking specific DI contexts.


You can easily configure URLs that contain all the information necessary to display a configured dashboard and call these URLs from external tools. For more information, see How to build URLs to access a dashboard from external tools.

URL format

The format of a URL to access a dashboard with preset parameter values is as follows:

<adi url>/ui/<perspective key>/dashboards/dashboard-<dashboard UUID>?<runtime parameters>

Where:

  • <adi url>/ui is built as follow: https://mycompany.int/decisioninsight/myapplication/ui
  • <perspective key> is the identifier of the perspective. See Perspectives.
  • <dashboard UUID> is the identifier of the dashboard
  • <runtime parameters> is built as follow: <param1 URL identifier>=<value for param1>&<param2 URL identifier>=<value for param2>&...
    • Dashboard parameters identifiers are set up by the application builder
    • Some application parameters identifiers are reserved:
      • tm  is the identifier for the time machine.

Parameters format

To create a dashboard URL that you can access externally, the values format is as follow: 

Parameter Format Remarks
Entity parameter <value>@<resolution time>
  • The value can be:
    • The UUID of an instance that has the same entity type as the parameter.
    • The key value of an instance that has the same entity type as the parameter.
      • Works only for entities with simple String or Integer keys.
      • If the entity has multiple simple String/Integer keys, the correct key is chosen searching in a loop for all keys values.
      • The value shouldn't contain the following character : '@'
  • The resolution time:
    • Optional; If it is not specified, the current time machine date is used.
    • Follows the ISO 8601 format: yyyy-MM-dd'T'HH:mm:ss.SSSZ
    • The milliseconds are optional.
    • The time zone offset can be either 'Z' for zero (UTC time), or of the form '+/-HH:mm' for non-zero.
  • The instance must be live at the specified resolution time.
  • When the parameter is multivalued, separate the values using the '|' character.
    • For example: <value 1>@<resolution time1>|<value 2>@<resolution time2>| ...
Attribute parameter <function id>|<value>

When the selected function accepts:

  • No additional input – for example, IS_NULL – the function id is enough.
  • For multiple inputs, separate the values using the '|' character.
    • For example, IN|<value 1>|<value 2>| ...
Classifier parameter <function id>|<value> Similar to the Attribute parameter but the value is the UUID of an instance of the same classifier type as the parameter.
Period parameter

LAST|<scalar value>|<unit>

CURRENT|<rhythm UUID>

  • scalar value is a positive integer value
  • unit is one of seconds, minutes, hours, days, weeks, months, years, weekyears
Time machine

<iso_utc_time>

If you don't specify a value for this parameter, clicking the URL opens the dashboard with the time machine in live mode.

If you specify this parameter, clicking the URL opens the dashboard with the time machine paused to the time that matches your tm parameter settings.



Related Links