Brief description of the idea:
Our team develops Qlik-Sense OEM applications for several companies. Many of our customers are using NPrinting.
So we designed on-demand reports for specific reports in our OEM applications.
In the on-demand reporting button, we have to enter a unique 'NPrinting server URL' for each customer when we roll out our new features.
So we want to be able to use a variable in this URL that we can set outside the application in a script.
The value proposition of the idea:
We can take care of the URL outside the application and don't have to copy and paste it when we roll out new features to customers. Less effort is needed to keep the URL correct after a release.
The target audience (user role) for the idea:
Qlik Sense and NPrinting developers, especially if you create the same reports for many customers.
How does this idea help the user?
Less effort is needed to keep the URL updated and correct. Typically, after a new rollout of the new application, you have to remember to check the customer's URL.
With this feature, the URL can be stored outside of the application and is unlikely to change and will be updated as new features are rolled out.
Adding context to the review process
The idea is also useful for Qlik Sense developers.
Greetings from Southern Germany
