This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Improvement suggestion: Substitute Users - time limit or warning icon

Good afternoon,

I want to make an improvement suggestion regarding the appointment of substitute users.

When this feature is used by our users, in most instances, they forget to disable when no longer required.

I can understand how this happens; most users when they return from an absence are catching up on business and e-mails etc. and remembering to disable substitute users is probably the last thing on their mind. As a result, the substitute users can continue to be included in the Assignments.

I have two suggestions that might be useful for this:

  1. The ability to set an expiry date for substitute users. Once this date passes, substitute users are removed/cleared.
    1. Maybe even better, could a user set a start and an end date for substitute users to be active, the same way this can be specified for Outlook Out-of-Office replies.
  2. A warning icon on the top of the taskbar (similar to the yellow update icon we see when there are updates available). That way when the user logs in to M-Files they would see the icon immediately and would know that substitute users is still active.

Also, if substitute users is something we really want to promote as a feature of the system, doesn't it make sense that it has its own command, possibly on the M-Files Homescreen? At the moment, it is tucked away under 'User Settings'. In my experience, most of our users don't even know where to find it if they wanted to use it.
The feature should be more prominently visible, maybe alongside the "Create" button.

Thank you for your consideration.

Patrick.

  • Are you interested in an out-of-the-box solution to all your substitute user 'problems'? Recently we created an M-Files VAF app that covers 'all' related challenges such as: E.g. scheduled activation and deactivation, authorization of substitutes for filtered object classes, assignment classes, access rights via NACL, chains of substitutes, etc.