User Provisioning

data source

HIPAA

multi-tenant

<h4>Changing the Elasticube Before Loading a Dashboard</h4>
This add-on gives you the ability to dynamically determine which data source should power a given dashboard. You determine how data sources are selected dynamically through a security settings file or via customizable URL parameters.
You can replace any data source (ElastiCubes, Live models and data sets), while sharing dashboard for a specific group of users. In addition, each data source for each widget can be changed.
To configure the add-on to work with multiple data sources, you need to configure a new data source for dashboards in the `dashboardDatasource` config section and then configure the section `WidgetsDatasources` for each widget (see the security section in the configuration below).
Note: If you want to change only the dashboard&#8217;s data source, you can delete the `WidgetsDatasources` section.
<div style="width: 640px;" class="wp-video">
<video class="wp-video-shortcode" id="video-32098-1" width="640" height="360" preload="metadata" controls="controls"><source type="video/mp4" src="https://cdn.sisense.com/wp-content/uploads/dynamicElasticubes.mp4?_=1" /><a href="https://cdn.sisense.com/wp-content/uploads/dynamicElasticubes.mp4">https://cdn.sisense.com/wp-content/uploads/dynamicElasticubes.mp4</a></video></div>

__in-chip-technology-2-image-unique-image-unique

__in-chip technology

<h4>To install the Dynamic Elasticubes add-on:</h4>
<ol>
<li>Download the add-on. 
For Windows users: 
Extract the `.zip` archive to `C:\Program Files\Sisense\app\plugins` 
&#8211; If the folder does not exist, create it before extracting the `.zip` file. 
&#8211; Use the alternative plugins folder `C:\Program Files\Sisense\PrismWeb\Plugins` for Sisense versions lower than 7.2. 
&#8211; For Linux users: 
&#8211; Extract the `.zip` archive to `/opt/sisense/storage/plugins/ 
&#8211; Use alternative plugins folder on tab `Admin &gt; System Management &gt; File Management` then upload extracted plugin to the `plugins` folder for Sisense versions higher than l8.0.3</li>
<li>Configure the config.js file described below.</li>
<li>Refresh your dashboard.</li>
</ol>
<h4>Implementation</h4>
<ol>
<li>Configure the config.js file (see the Configuration section below). 
Note: After upgrading to Sisense Linux 8.0.5, the config.6.js configuration file is overwritten. Sisense recommends you copy the configuration file before upgrading and then restore the file after upgrading.</li>
<li>The add-on redirects queries to one of the data sources, it is imperative to apply data security rules based on user groups. This can be configured in your Sisense Admin panel.</li>
<li>Ensure that Active Directory imported groups are allowed to query the ElastiCube via &#8216;Admin&#8217; &gt; &#8216;Data Sources&#8217; &gt; &#8216;Share&#8217; &gt; Modify group to &#8216;Can Query&#8217; or &#8216;Can Edit&#8217;.</li>
</ol>
<h4>Configuration</h4>
<ul>
<li>urlParamName(STRING) &#8211; allows you to configure URL params(see section &#8216;Using URL parameters&#8217; below).</li>
<li>configureByDashOID(BOOLEAN) &#8211; default behavior for the security object below is to use dashboard OIDs as the nested object keys. Disabling this option will revert to dashboard titles. Default is true.</li>
<li>throwErrors(BOOLEAN) &#8211; enable if each dashboard in your implementation has to be switched dynamically and errors need to be uncovered in QA. Defaults to false. 
&#8211; if set to `false`: hide errors in the browser console 
&#8211; if set to `true`: throws errors in the browser console and returns from plugin execution</li>
<li>maskDataOnError(BOOLEAN) &#8211; leaves data mask on if an error occurs while switching data sources. The default behavior is to show data, even after an error (i.e. the dashboard was not configured, bad API call, no user groups defined, etc.). This does not affect downloads and users will still be able to download. Defaults to false.&#8221;</li>
<li>verifyECLocation(BOOLEAN) &#8211; enable if your data source migrates between servers. 
&#8211; if set to `false`: the add-on will assume the server locations of data source remain unchanged. 
&#8211; if set to `true`: an additional API call will be fired to confirm the server location of a datasource</li>
<li> selectMostRecent(BOOLEAN) &#8211; if set to `false`: the add-on will work with original functionality, switching via a configuration file or URL parameter.- if set to `true`: the add-on will work with custom logic. For users from Active Directory within an AD Group, the latest created and shared data source for this AD Group will be used as the datasource for the dashboard.</li>
<li>mostRecentRolesBlackList(ARRAY OF STRINGS) &#8211; would not update data source for specified roles if `selectMostRecent`is enabled. Works only with `selectMostRecent` parameter.</li>
<li>security(OBJECT) &#8211; nested objects that describe security configuration for dashboard and widgets on a per dashboard basis. The default identifier for each dashboard is OID, but this can be reverted to dashboard titles if desired. For configuring new data sources for dashboard fill fields in the `dashboardDatasource` object. For configuring different data sources for widgets configure `widgetsDatasources` object, replace widgetId by your widget id which should be changed and fill fields `title` and `address`.For configuring multiple data sources:`&#8217;dashboardIdOrTitle&#8217;: {  &#8211; dashboard identifier (id or title)&#8217;groupId&#8217;: {  &#8211; identifier of the group which dashboard should be updated dashboardDatasource: { &#8211; section which configures a new data source for the dashboardtitle: &#8216;dataSourceTitle&#8217;, &#8211; data source titleaddress: &#8216;dataSourceAddress&#8217;, &#8211; data source address (can be localhost, live, set or ip of the server where data sources can be imported from). Localhost by default.},
widgetsDatasources: { -section which configure a new data source for the widgets
&#8216;widgetId&#8217;: { &#8211; widget id which should be changed
title: &#8216;dataSourceTitle&#8217;, &#8211; widget title
address: &#8216;dataSourceAddress&#8217;, &#8211; data source address (can be localhost, live, set or IP of the server where data source can be imported from). Localhost by default.
},
}
},
},
`
</li>
</ul>
<h4>Using URL parameters</h4>
<ol>
<li>Modify the *mod.urlParamName* variable inside the config.js file to your preferred query string variable name.</li>
<li>Navigate to your target dashboard and append the following to your dashboard URL with your own information: 
?{yourURLParamName}={desiredECubeTitle}</li>
</ol>
<h4>Limitations</h4>
<ul>
<li>When using the URL parameter strategy, if the user navigates to another dashboard with the URL parameter still attached, a query error will arise if the schemas aren&#8217;t identical. If users need to be able to switch between dashboards and dynamically switch to different data sources. Sisense recommends using the security settings strategy.</li>
<li>If using a URL parameter strategy, the add-on will switch data sources for any dashboard it encounters, assuming the URL is correctly formatted.</li>
<li>If exporting the dashboard to PDF from the left-side panel (outside of the dashboard itself) and the dashboard hasn&#8217;t been opened before, it might take a second attempt to successfully export.</li>
<li>When enabling &#8216;maskDataOnError&#8217;, downloads are not disabled.</li>
<li>The add-on will not work in Sisense.js.</li>
<li>`selectMostRecent` &#8211; works only with users from Active Directory, for other users it will be ignored. First AD Group is used to authorize the check of ElastiCube updates.</li>
<li>If selected the data source is not shared with a user, an error with the text: &#8220;you don&#8217;t have access rights&#8221; will be displayed. After page refresh error message will be changed to: &#8220;something went wrong&#8221;.</li>
<li>The add-on will not replace the widget data sources if the dashboard&#8217;s data source was not changed.</li>
</ul>
<h4>Change Log</h4>
28 June 2018
  &#8211; Added support for Elasticube sets
  &#8211; Solved bugs related to various exports, report sharing
  &#8211; Added support for 7.1.1 and some backwards compatability
&nbsp;
18 July 2018
  &#8211; Fixed filter behavior bug

Leave Feedback