Hello,
Does anyone know of a solution that allows me to block another user's access to a specific report when there is at one user accessing this report?
To frame, application Studio report consulted by browser, EPM v12 MT.
Regards
Rui
I would say there might be many solutions. The key is to define what 'work with report' means. Just a fact that a report is opened typically is not enough, it is more 'check in/check out' process on the user level. in this case, one of the solutions might be:
- report has button 'Check In'/'Activate work'/'Lock', etc. Once the user pressed this button, the UX is changed for others:
- users can enter, but report shows no data
- users can enter and see reports, but no data entry available
- navigation to the report doesn't go to report, but shows warning that report is currently locked
- report should also have ability to unlock the report access after users are finished with the changes
just one of the options, all is accessible with platform features
I foresee the problem that when a user has to "activate" his work in the report manually, that he forgets to release it or just end the session without releasing it, so that the report stays blocked as long as somebody releases it...
Or you need some kind of administrative job that releases such reports automatically after X hours...
we have similar concept in B&P business applications and there everyone with the access to this report (Planning step in the B&P example) has ability to 'release' the report. You can also add some notification about this via mail, etc.
Hi Nick,
Thanks for your feedback,
this situation is because we have process to write values in relational table, and the risk of different users write values in table at same time without distinction and his may generate some error in processes ahead . We implemented a different approach, add to table a column to registers the user that made de changes, then we will have multiples registers if more than user user are working in report .
The approach 'Check In'/'Activate work'/'Lock, like Ralf said, the users forget to release it or just end the session without releasing it, so that the report stays blocked, we have exactly some issue Task/Planning steps of B&P, when we assign Groups to the tasks,
