Allow User Selected Startup Documents to Override Startup Documents Assigned in TARGIT Management
The existing configuration permits documents assigned to users through TARGIT Management to override the Load on Startup document chosen by a user and saved in their Anywhere profile. This has sparked concerns due to its apparent restriction on user autonomy, especially when a user is associated with multiple groups, each with a Startup Document assigned.
To address this issue, I suggest adopting a more user-centric approach. If the development team opts to maintain Management as the overriding document, it would be advantageous to introduce a feature allowing users to designate their preferred startup document when they belong to multiple groups with distinct startup documents. This adjustment would grant users greater flexibility and control, preventing the system from imposing a startup document solely based on group membership.
As an illustrative example, a user belonging to both the Parts and Service groups in Management may currently find the Service startup document taking precedence over the Parts startup document. The proposed enhancement would empower users to make their own selection for the startup document or enable them to choose their preferred document for startup. This ensures a more personalized and efficient startup experience.
The hierarchy of enforcement, from lowest to highest, would be: Management Group Startup Document < User Selected Management Group Document < User Selected Startup Document.
Comments
Thank you. We appreciate your input, and it has been noted.
The status of this post will be updated as your request is being processed by TARGIT.
Until then, the post will remain here to gather further interest, more votes and comments.
Best regards
Ole
Please sign in to leave a comment.