2,004
edits
Changes
no edit summary
===New Role Permissions for Submit buttons===
Global System Upgrades<br />
Submit buttons can now be configured so that they are presented to users based on role and UTA role permission settings permissions reducing the need for visibility conditions. If a Submit button is associated with both a role and UTA role, the UTA role permission will take precedence.
:* [[Why?]] Prior to this enhancement, Submit buttons could be associated with one or more Level One templates and visibility conditions controlled when the button was visible. This enhancement adds role and UTA role permissions to Submit buttons giving admins more flexibility when configuring them.| [[How]]
<!-- 40243 - Role Permission for Submit button -->
===New Ability to Assign Many Objects to Many Objects With the Assignment List View - Phase 1===77277
Global System Upgrades<br />
This feature adds the ability to assign many objects to many objects through the new Assignment List View feature. This feature will allow you to easily attach a group of reviewers to a Level One, assign many users to one ore many organizations, even attach a Level 1 to one or more Level Ones. Once fully implemented, this enhancement adds the ability to assign many objects (like users, organizations, Level 1, Level 2, Level 3s), to many objects. Phase one of this enhancement (April 2016 Upgrade) will add the ability to attach one or many contacts to Level 1s.
===Enhanced Password Policy Options===
Global System Upgrades<br />
This feature adds an additional option to the password policy ensuring a user’s ID (in its entirety) cannot be the whole, or part, of the user's password, or the whole password.
:* [[Why?]] | [[How]]
<!-- 44147 - Platform password policy enhancement -->