Click on the settings icon and then select Process Config option:

• Set Embed in Page to Yes
• Select UX_Samples from the Instance drop-down list
• Select }bedrock.cube.data.export from the Process Name drop-down list

This configuration will already show all the parameters of the process in the webform.

To make the results even friendlier to the users we can add additional code for the parameters.

Inside the "parameters" tag we can add additional config options, in order to set default values and hide specific parameters. Additionally, we can assign check boxes and subsets.

Here is the configuration we can use to make the process easier to us.

Below you can also find, in the attached file, the complete TI setup.

This functionality allows users to dynamically define a dimension hierarchy using a placeholder. After clicking Select button the Hierarchy dropdown list will be changed to text box to enable placeholder input. 

To showcase this example we will create new view:

• Select Add public... option inside App Templates - Views folder 
• Do the following configuration inside the popup: 
  • Add view title e.g. Dynamic hierarchy
  • Change the Cube Source by selecting Retail from the dropdown list
  • Click Create button 

Publish the view.

Next, we are going to set up the view: 

• Open cube settings popup 
• Drag and drop: 
  • Version, Year, Region to Global filters 
  • Currency and Retail Measure to Global fixed settings 
  • Period to Row Dimensions 
  • Product to Column Dimensions
•  Configure the Dimensions: 
  • Version, Year, Region: Default subset, Code and Description attribute
  • Currency: Local fixed value 
  • Retail Measure: Sales Amount fixed value 
  • Period: Default subset, Short Description attribute  

Now we will set up Product dimension to dynamically change  based on the hierarchy selected:

• Click Add Dimension (+ icon) button in Global Settings section 
• Choose Product from the list 
• Click Add Dimension button 
• Click Add button again 
• Set Control objects option to Yes 
• Choose }Hierarchies_Product from the list 
• Click Add Dimension button

• Select }Hierarchies_Product dimension 
  • Open Subset Editor 
  • Click All button
  • Select Product:Color and Product:Size
  • Click Apply 
• Select Product global filter dimension
  • Click Select button visible above Hierarchy dropdown list 
  • In the editable text box input UX Placeholder: $<<UX_Demo.}Hierarchies_Product.}Hierarchies_Product>>
  • Change the list type to MDX  
• Select Product dimension added in columns
  • Add the same placeholder in the Hierarchy text box
  • Change the list type to MDX  

• Close the cube settings popup 
• Change }Hierarchies_Product filter to Product:Size and back to Product:Color

Notice how Product dimension hierarchy dynamically updated in global filter as well as in columns. Save the changes. 

We will use the view configured in the previous exercise to practice how can we add nested UX placeholders. 

In this example the selection will be even more dynamic, both filters are configurated the same way as in previous case, but the MDX changes were made for the Product dimension added in columns.

We need to do only one change in the view configuration:

• Open cube settings 
• Select Product dimension added in columns
  • Change the MDX query to:

• Close the cube settings popup 
• Select element from Product global filter and notice how the column element dynamically updated
• Change }Hierarchies_Product filter to Product:Size and select different Product element
• Save the changes 

Above example shows that by nesting two UX placeholder statements within each other users can not only define dynamic element selection based on filters, but also dimension hierarchy.  

One way to use dynamic filters with the help of MDX is to query a member base on the value of an attribute of another member.

To showcase this, we will create a new view, called Dynamic MDX. Select the "General Ledger" as the source cube for this view.

Setup the dimensions as shown in the following picture and choose the default subsets or members for each of the dimensions.

In our example, we want to make the Currency selection dynamic, based on the selected region. The Region dimension already has an attribute called "Currency". This is the attribute we are going to use for the example.

For the Region dimension select the "All Countries" subset.

For the Currency dimension select MDX and type the following statement and observe that whenever you change the country, the currency will update automatically based on the attribute.

• Define MDX for Currency dimension to display the currency set in attribute of selected Region element: [Currency].[Currency].["+[}ElementAttributes_Region]
• Set Region element to change dynamically: [Region].[Region].[$<<UX_Demo.Region.Region>>]
• Define the Region attribute : [}ElementAttributes_Region].[Currency])+"]

The next example will allow us to see only filtered Region elements on the columns based on their value in the selected cube. 

To showcase this, we will create a new view, called "MDX - Filtering displayed elements". Select the "General Ledger_C3UX" as the source cube for this view.

Setup the dimensions as shown in the following picture: 

• For Department dimension select Element List Type, Code and Description Attribute and Corporate Element 
• For Region dimension select MDX List Type and Code and Description Attribute

Select Region dimension and in the MDX text box paste following query: 

Close the cube setting and change the Version & Account global filter and observe how the displayed elements change based on their value: