In SOLABS QM10, Function Roles (FCT) are mainly used for assignments of tasks within the system such as document workflow tasks, ad hoc/secondary tasks and training assignments.
The Name field and the Job Title field for the Function Role are required fields when the role is created and can be modified later if needed. If this is done, what are the impacts?
❶ The Name field for a Function Role:
The Function Role Name is what is seen in role lists for task assignments such as document workflow tasks (review, approval, retire) and ad hoc/secondary tasks. When choosing a Function Role from a list, a specific user with that Function Role assignment can then be selected or ‘any’ users with that Function Role assignment can be selected.
When the Function Role Name is modified, the role is simply renamed and remains assigned to users with that role assignment. Therefore, at the task assignment level, changing the Function Role Name will have no impact. The modified name will apply everywhere this role is used and where it is currently assigned.
For example, if a secondary task is currently assigned to a role named FCT_Quality Associate, and the Function Role Name is modified to FCT_QA Associate, the new name will be displayed in the task itself and the task assignment will remain the same.
❷ The Job Title field for a Function Role:
The Function Role Job Title is what is seen in lists in the Training section.
These lists are used when linking a Training Activity to Job Title Profiles:
These lists are also used when filtering by Job Title Profile to manage Training Activity assignments:
When the Function Role Name is modified the Job Title field will NOT automatically be updated. Therefore, if the modification of the Name also applies to the Job Title, then that needs to be modified manually as well.
As for the modification of the Name field, at the task assignment level, changing the Function Role Job Title field will have no impact. The modified Job Title will be displayed everywhere that Function Role is used in the Training section.
Comments
0 comments
Please sign in to leave a comment.