Right click on the Technical Components folder (found in. It comes dialed in with 8 categories and 44 components. You can create enterprise grade, Interactive Dashboards and Analysis applications to name a few. Lumira Designer is fully loaded and extendable. The new names are Lumira Discovery and Lumira Designer.
You can only add one of these to an application, but you can then use scripting to dynamically create any number of components at runtime. Now SAP has combined both Lumira and Design studio into one add on to the BI server. Now i have a severe dilemma: The customer doesnt want prompts on application startup and we need dimension filters in the TEXT-Objects for further processing.īy the way: With Design Studio 1.6 we didnt have these issues. To dynamically create new components on the fly, it is necessary to add the Components Technical Component to your application. I tried to move the coding for writing dimension filters to Text-Objects from " On Startup"- Event to " On Before Prompts Submit", but the syntax get mutiple errors there and a syntax help is not available for this type of event. I investigated that if i change "Force prompts on Startup" from false to true, the dimension filters are written in corresponding TEXT-Objects again. Please remind, that the coding for this is placed in the "onStartup event". Filters of dimensions are changed by the User and confirmed via "OK" Button in the prompt.Īfter that Datasources are filtered according to all changes, but the dimension filters are not written in corresponding TEXT-Objects.
In addition we have for "onStartup event" some coding which writes filter values (with a syntax logic) of a dimension in a TEXT - Object.Īs a result of this procedure, we dont need a prompt for these additional applications ( Force prompts on Startup = false), Dimension Filters of the central Dashboard are filtering Datasources of the additional applications and these dimension filters are written in corresponding TEXT-Objects.īUT Users should be able to change dimension filter values in these applications via a button which calls the prompt (APPLICATION.openPromptDialog()). On Application level it is defined in the "on Variable initialization" event that these Global Variables fill Bex Variables of a Bex Query. At these apllications we have global variables defined as STRING and URL parameter. Via Open Document interface we sent filter values which are set in the central Dashboard to our additional Lumira applications. As an extension, SAP Lumira Designer 2.2 now provides users the ability to create their own components, modify their. SAP Lumira Designer 2.1 allowed users to create components at runtime. Lumira Designer has been adding features to enrich the self-service experience of its applications. We are using a central Lumira Dashboard for drill down to additional Lumira applications. Authoring in SAP Lumira Designer 2.2 An Introduction. I have a question regarding prompts and events in SAP Lumira Designer 2.1. To dynamically create new components on the fly, it is necessary to add the Components Technical Component to your application.
0 kommentar(er)
