- Tue May 14, 2019 1:05 pm
#824435
We're evaluating whether PM will fit our needs or not. Currently we're using SharePoint and Nintex on top of that. We have a lot of different buildings that each operate on their own. They have their own approval systems. Until the processes get to headquarters each building operates almost as it's own company.
Right now for task assignments we do a lookup to a master list. It has each building listed and then a lot of columns named after each approval position with AD accounts listed in each position. So each time a workflow is initiated we do a lookup against that list, filtered down to the building selected in a drop down on the form, and then use set those approvers as different variables to be used throughout the process.
In almost every case we don't use groups, we assign directly to specific AD accounts. We do not assign to each and every approver per building, as we may skip certain approval positions if they do not need to be in those workflows.
Also, options chosen on the form itself may determine if additional approvers are added or not.
Is something similar available in PM OOTB? If not, is there a suggested way to handle that?
Right now for task assignments we do a lookup to a master list. It has each building listed and then a lot of columns named after each approval position with AD accounts listed in each position. So each time a workflow is initiated we do a lookup against that list, filtered down to the building selected in a drop down on the form, and then use set those approvers as different variables to be used throughout the process.
In almost every case we don't use groups, we assign directly to specific AD accounts. We do not assign to each and every approver per building, as we may skip certain approval positions if they do not need to be in those workflows.
Also, options chosen on the form itself may determine if additional approvers are added or not.
Is something similar available in PM OOTB? If not, is there a suggested way to handle that?