Error "Some attributes for role, "<<user specified role name>>" are not valid please check the values again and resubmit." When Editing Role Attributes in Instantis EnterpriseTrack

Last updated on MARCH 16, 2017

Applies to:

Symptoms

When attempting to edit <> attributes, and receive message:

Roles Edit Error. Please correct the errors shown below, and try again.
Some attributes for role, "Team Member" are not valid please check the values again and resubmit.

The issue can be reproduced with the following steps:

1. Administrative User Navigates to Administration > Resource & Security (tab) > Resource Configuration (group) > and open Resource Roles (link)
2. For <>, click [Edit]
3. Attempt to edit any of the attributes listed:

• • Role is filterable
  • Proposal Signoff Type
    •   Content-Sensitive
    •   Signoff Optional
    •   Signoff Required
  • Part of the initial Proposal team
  • Role is required to create Projects
  • Part of the initial Project team
  • Is Required For Entire Project Duration?
  • Max number of Users with this Role Allowed on a Project:
    •   Drop Down selection 1 (NOTE: 2-many allowed)
  • Phase Due Date Email Notifications:
    •   Send Mail "7" Days Before Phase Due Date
    •   Send Mail When Phase is Overdue       
  • Planned Project Close Date Email Notifications :
    •   Send Mail "7" Days before Planned Project Close Date
    •   Send Mail When Project is Overdue
    •   Send Mails every Week After the Project is Overdue
  • Report Settings:
    •   Show on Financial Benefits by Business Unit
    •   Show on Resource Listing Report
    •   Show info on Project Reports
    •   Required signature final report
    •   Show on status update report
    •   Show On Portal  

4. Receive message: Roles Edit Error. Please correct the errors shown below, and try again.
Some attributes for role, "Team Member" are not valid please check the values again and resubmit.

Changes

The Role <> has been renamed to <> from "External Team Member" and is not a registered global role by default.
 
Due to the default configuration of the role being  role_id=tm_notregistered_globalrole, meaning this is not a registered global role, the role name has been changed, and is being attempted to be used as a created role.

Cause