Hello, a rather open-ended question to which I equally as open to suggestions:
We have a dashboard in production, which utilizes the fairly typical flow of read from a db, to create QVDs, then a QVW reads those QVDs to present the data to user community. A portion of that data is refreshed in the databases monthly (purchased data from 3rd party). We now have a requirement that a small set of users be able to 'preview'that monthly data as it is presented in the dashboard, after it has been pulled from the database, but BEFORE the balance of the user community sees it. Ideally, the balance of the user community will continue to view the 'old' data. Only upon approval of the "pre-viewers"would the new data become accessible to the full user community.
Hope that explains the basic desired flow.
Has any one done anything like this, or have ideas on how to set this up? I would rather not have duplicate QVWs pointed to different QVDs, as the maint. of these 'twin' QVWs might get cumbersome.
Just an idea (maybe a wild one). I'm assuming that you have a Publisher at your disposal.
Turn the original reload task of the end-user document into an externally triggered task.
Create a second reload task for the same document, this time with a different target group (the ones that should preview the data) and let it run regularly at fixed intervals (every day?)
Also add a file name translation to the distribution setup of the second task. Call the target document "OriginalDocumentName-preview.qvw" or something.
Add a button to the original source document that is only presented to the "preview" users or just to the user that has final authority to release the document with new data to a wider audience. Attach a macro to the button that sends a trigger signal to the first task (search the community for examples)
As long as the new data has not been approved by the preview group or by the user with final authority, the original document won't get an update. The copy however will get regular updates, but will only be visible to the preview group. As soon as the new data looks ok, any one of the designated group of approvers can cause a reload of the original document and publish it to the wider audience.
This story may belong in the category "any input" instead of "good input". But I hope I can get you started in the right direction (eventually).
