I was not the developer on that project. Well, actually, I'm not a developer at all, I'm a Basis guy, and not a workflow expert by any means. All I can say is that we have a table that uses cost centers as the key and then has several 'approver' columns containing usernames. The custom workflow takes the cost center associated with a shopping cart and looks up the approvers in the table, then routes the approval step to those users. It's incredibly simplistic. We roll up budget authorities to a higher level in a cost center hierarchy, and so the 'zapproval' table only needs to be maintained at that level (not every cost center must be entered). If a specific cost center is entered, the workflow will use that, if not, it uses the higher-level rollup.
↧