[]
        
(Showing Draft Content)

Jump to External URL

Jump To External URL

You can jump to an external web app (with the filtered data) from a dashboard using the option External URL. The external web app will consume the jump-to variables defined in the URL and get the raw data.

For creating this URL, there is a variable Databinding and it has 3 sub-properties: "datasetId", "pivotModel", "rawModel".

  • datasetId: It will return the dashboard's datasetId to the jump URL.

  • pivotModel: It will return the dashboard's pivotModel to the jump URL. The pivotModel is used to get the aggregation data that was displayed on the dashboard.

  • rawModel: It will return the dashboard's rawModel to the jump URL.


    The Jump URL contains "#{Databinding["pivotModel"]}", "#{Databinding["rawModel"]}" and "#{Databinding["datasetId"]}",

Example:

  1. If there is a dashboard with a Column chart, and you want to jump to some external web application and have all the non-aggregated filtered values from the data, you need to create an External URL for the Jump To.


    This URL will give the information to the target application to identify the document, scenario, and any filter/other info needed to recreate the data behind a given dashboard that was jumped from.

    jump to URL

    (In this we have taken the target web app as "http://192.168.0.129:51980", parameter 1 as dataset, parameter 2 as pivotModel, and parameter 3 as rawModel).


  2. Preview the dashboard and right click on the chart and select Jump.

    click jumpto


  3. It will navigate to the target external web app and from this target web page you will get parameter1(p1), parameter2(p2), and parameter3(p3)(datasetId, pivotModel, and rawModel) and these can be used to request Wyn API to get the transactional non-aggregated data in the form of a list of values for a given data set column that correlates with all the filters, etc. that the scenario had before jumping.


    p1 p2 p3

    Note: This jump will be made as the Post request, and it will avoid the too-long URL issue.