In this article
Editing Studio Dashboard Definitions
Within the Dashboards folder, there should be a name for each dashboard.
Within the specific dashboard folder there will be a CDL document that describes the dashboard, and a manifest.json file which contains the name and description of the dashboard as discussed in the previous section.
Editing Dashboard Parameters
Within the CDL document for the program dashboard template, there are a set of dynamic parameters that can control elements of the dashboard such as the various data sources to be used. These parameters are then used as references within the config hub section to point to the relevant datasource.
An example snippet of CDL with the parameters definition block and referencing these parameters is shown below.
This CDL can be added when creating the program dashboards in survey designer using a reference to the assets in the system that will then be copied into the program package. Part of the workflow process will be to substitute in these parameter values with the newly created asset ID’s.
parameters #parameters {
onlineTransactionalSurveyPublicName: p449588071501
onlineTransactionalTextAnalyticsResultsPublicName: TextAnalytics_p449588071501_816
storeTransactionalSurveyPublicName: p990421467305
storeTransactionalTextAnalyticsResultsPublicName: TextAnalytics_p990421467305_816
}config hub {
hub: 209351dataset survey #storetx {
publicName: @parameters.storeTransactionalSurveyPublicName
}
dataset survey #onlinetx {
publicName: @parameters.onlineTransactionalSurveyPublicName
}
dataset textAnalytics #storeta {
publicName: @parameters.storeTransactionalTextAnalyticsResultsPublicName
table responses = storetx.response:
}
dataset textAnalytics #onlineta {
publicName: @parameters.onlineTransactionalTextAnalyticsResultsPublicName
table responses = onlinetx.response:
}