Hi Scott, I wanted to reinforce what Justin has said - it is great to see you back making these videos they are massively helpful. Thank you! Funnily enough I had a similar requirement on a recent project except instead of going to a job role, our requirement was for the workflow item (Purchase requisition in our case) to go to the manager of the requestor, and then to a few different teams of people. The manager part was fine as we used the hierarchy you showed, but for the workflow to end up with a team we decided to assign the users within the teams to User groups (System administration > Users > User groups). We could then route the workflow item, based on value, to the appropriate teams by using the Participant option within the workflow assignment, then selecting User group participants in the Type of participant field. Thought I would share in case it is helpful for any of your viewers as this solution is working well so far our side. Thanks again Scott!
In some companies, we do have a hierarchy that is not consistent across departments. So you set up this hierarchy but what if some departments have not filled in a position, let's say a Manager reports to VP but usually we have Director in between but in other departments you have that consistent hierarchy. Do you have a workflow suggestion? If in workflow, I think you'd have to be more exact in your title i.e. Project of Mgr of Accounting for instance, not just Project Manager.
I guess you can use organisations signing limit policies and the same you can compare in workflow like employee limits >= PO Balance. You are already linking employee HR records with position. This way we do not have to create multiple approval limits based on approval amount.
Thanks... I looked at signing limits and wasn't able to get it to work correctly. It was probably something I was doing wrong but for whatever reason it wasn't working as I would expect it to. It's been a couple of months so I don't remember the exact issue, but this method ended up being a cleaner implementation.
I have set up signing limits for PO's - both spending and approval, but still can't get the workflow to look at the signing limits. The approval goes through the hierarchy, but doesn't seem to take my signing limits into consideration. The signing limits have been assigned to my org/legal entity. I have also ensured the signing limits have the correct job rule. Any thoughts on this or do you have a link to video/documentation piece for the setup you mention?
Hi Scott, I wanted to reinforce what Justin has said - it is great to see you back making these videos they are massively helpful. Thank you!
Funnily enough I had a similar requirement on a recent project except instead of going to a job role, our requirement was for the workflow item (Purchase requisition in our case) to go to the manager of the requestor, and then to a few different teams of people. The manager part was fine as we used the hierarchy you showed, but for the workflow to end up with a team we decided to assign the users within the teams to User groups (System administration > Users > User groups). We could then route the workflow item, based on value, to the appropriate teams by using the Participant option within the workflow assignment, then selecting User group participants in the Type of participant field.
Thought I would share in case it is helpful for any of your viewers as this solution is working well so far our side.
Thanks again Scott!
Great to see you making videos again, Scott. Thanks for posting these.
Great Video Scott. Loved your presentation.
In some companies, we do have a hierarchy that is not consistent across departments. So you set up this hierarchy but what if some departments have not filled in a position, let's say a Manager reports to VP but usually we have Director in between but in other departments you have that consistent hierarchy. Do you have a workflow suggestion? If in workflow, I think you'd have to be more exact in your title i.e. Project of Mgr of Accounting for instance, not just Project Manager.
I guess you can use organisations signing limit policies and the same you can compare in workflow like employee limits >= PO Balance.
You are already linking employee HR records with position.
This way we do not have to create multiple approval limits based on approval amount.
Thanks... I looked at signing limits and wasn't able to get it to work correctly. It was probably something I was doing wrong but for whatever reason it wasn't working as I would expect it to. It's been a couple of months so I don't remember the exact issue, but this method ended up being a cleaner implementation.
I have set up signing limits for PO's - both spending and approval, but still can't get the workflow to look at the signing limits. The approval goes through the hierarchy, but doesn't seem to take my signing limits into consideration. The signing limits have been assigned to my org/legal entity. I have also ensured the signing limits have the correct job rule.
Any thoughts on this or do you have a link to video/documentation piece for the setup you mention?