Discussions
Categories
Groups
Community Home
Categories
INTERNAL ENABLEMENT
POPULAR
THRUST SERVICES & TOOLS
CLOUD EDITIONS
Quick Links
MY LINKS
HELPFUL TIPS
Back to website
Home
Web CMS (TeamSite)
Approval Group Selection
System
I need to have approval by OS group rather than approval by a user (such as the workarea owner). I am working on an Intranet and most of the content is in a single branch. It really needs to be a casual contributor/ad hoc system (with portal integration, so the user browses the portal and selects "edit this page"), so the workflow cannot be created by an editor (who selects an approval group) and assigned to a user. I also don't want to present the user with a drop-down list where they selet the approval group - rules need to be enforced, and anyway those lists get long. I need some sort of logic to select the approval group based on the directory the content they are working with is in, the category/type of the template and/or something else. I was thinking about an XML configuration file to control this but it quickly gets pretty complex and tricky to administer.
What are other companies doing in similar situations and do those solutions work well?
Find more posts tagged with
Comments
Johnny
Hi John,
We have also implemented an XML configuration for approval groups. It was based workareas though and seems to work quite well. A simple XPath query can then retrieve this information during workflow instantiation, hence no user selection is required.
If you can avoid complex business requirements such as what you have been talking about... thats always the best solution.
John
Sydney, Australia
Migrateduser
Hi Jonnhy could you send some piece of code ..?
thanks
smigster
I'm finishing of a couple of workflows with lots of approval and notification tasks. To handle discretely populated lists of approvers I created a workflow properties template which included replicant sections for all the different types of approver groups.
During workflow startup I exec an initialization script that figures out what kind of workflow is being run, who started it, from which branch/workarea, etc. then parses the Staging area version of the DCR to grab the appropriate list(s) of approvers. Then I do task->AddUser($id) where needed. Works great!