(Related to this, I found a post about multiple users Editing in Desktop edition and a request for the feature that locks Editing to a single user.)
Sometimes in my team we have a developer or QA fail to properly close a data flow they've opened in Edit mode. We have regular reminders & documentation approaches in place to try stop this happening but the risk remains that the Editor fails to properly close it: Analyze will lock the data flow, blocking the team from further development activities until that user is next able to login and properly close the flow. If the user is away for more than a few hours this can pose a big problem.
At present we resolve it by having one of our Admins perform a Password Reset for the user (Users > [username] > Cheange Password), then login as them (impersonate), and re-open / re-close the erroring data flow. This has been a workable solution.
However the ability to perform that impersonation presumably disappears if we implement Single Sign On (a feature released in 3.6.4), because of the security risks posed by impersonating at enterprise level. We'd be able to perform Password Reset but not impersonation.
Do you advise us against implementing SSO (in which case our security policy will force us to stop using Analyze entirely), or is Multiple Simultaneous Editors a feature on the roadmap? Ideally we would simply stop users from failing to close data flows but
- we're not 100% clear on what constitutes properly closing a flow (frequently users report that they've close a flow but Analyze still tells other users it's "locked for editing"; we can't find advice on this in the documentation).
- Analyze can be counter-intuitive as to what constitutes an Edit.
Please sign in to leave a comment.