Pass a population between apps (not document chaining)
The Issue
This is a scenario that happens every day (dozens of times). You’re in an app investigating data when you realize something else might have been a factor in the anomaly you’re investigating (or whatever it may be). If the other factor or other factors live in a different app you’re not left in a very good position.
The Solution
We want to build relationships within each app that would allow a user to simply package up a field, based on the selections made in one app and push those values to a new app, filtering the new app’s data to just those values.
How it's different
This is different from document chaining for a couple of reasons.
-For document chaining to work the way this development would work the user would have to filter data (Month=X, Location=Y and Z and Person=My; for example) then select "All Possible" values of a field they want to push to a new app (like All Possible Account IDs) then drop the filters made on anything other than Account IDs then apply document chaining. And this would only work if the number of records selected was appropriate to apply to a URL. If, on the other hand, there ends up being 100K Account IDs that app1 is trying to push to app2 then document chaining is out of the question.
-If two apps shared enough similar fields to allow document chaining to be pretty dynamic in what filters get passed then likely those two apps could be the same app.
One caution developers always need to be aware of is the ‘mega app’ development. Where people continue to ask for more elements to be added to one app until the app becomes too complicated to navigate and use. This development would eliminate the need for people to ask to add more to a specific app if the data element existed elsewhere and they could take their population with them to study a different facet of the same cohort.
Considerations
-The relationships within each app would need to maintain, not only the other apps the open app can push values to, but also the field that should be related between apps. So if I’m in our Denial Management app I might want to jump to data in the Hospital Accounts app (which would be related on [Billing Account ID]) but I most might want to jump to data in the Claims app (which would be related on [Liability Bucket ID]). The field values that gets pushed to a new app should most definitely be managed by the developers, the users should not have the freedom to pick which field filters data in a new app.
-I think it’s a fair assumption that 1 element of data that lives in 2 or more apps would/should have the exact same name (for us an example would be [Billing Account ID]).
-There’s plenty of real estate below an apps ‘show app information’ button for an additional ‘Jump to new app’ button. The user interface for this development would simply be a dropdown list of apps a user could potentially push a population of data to.
-Something else that should be considered is what apps does the user have access to. They should obviously not be allowed to jump to an app in which they don’t have access. But if there’s a dropdown list of possible apps to jump to, should the apps they don’t have access to be excluded from the list? I don’t really care at this point. I’m too excited about getting something working.
if you know the field of the selection you want to pass to the new app, you should be able to built that using sth like this: ='https://qlikserver/etc....' & Concat(field,...).
You will have to spent some time to create the exact formula but that should help you to get what you are looking for.
