We have a user with a global role of Accounting. Sometimes this person is not included on a document route even though the predefined route includes the role of Accounting. Why is this user not always included?
When Spitfire evaluates a role-based predefined route, it looks for people who have that role on the project team. If any people with that role are found, then only those people are added to the route. If no person with that role is found on the project team, then all contacts who have that role on a global (non-project-specific) level are added to the route.
Let’s say that both Jay Adams and Wilma Flint have the global Accounting role.
But only Wilma is on the Team Contacts for a particular project.
When Spitfire uses the following predefined route to create the routing for a document on that project, it will add only Wilma to Seq 4 – Accounting. However, if Wilma is removed from the project team, Spitfire will add both Jay Adams and Wilma Flint to the document route, since they both have the global Accounting role.
- People with global roles can be added to project team contacts, as in the example above, if such people should always be on project routes.