Difference between revisions of "Help:Sandbox"
From SDU
Chipperdude (Talk | contribs) |
Chipperdude (Talk | contribs) |
||
| Line 34: | Line 34: | ||
2) The loop can have another activity node that sends email to all users in the string, or whatever else you want to do with each element it finds in the string. | 2) The loop can have another activity node that sends email to all users in the string, or whatever else you want to do with each element it finds in the string. | ||
| + | [[Get Groups Worflow Example]] | ||
<\pre> | <\pre> | ||
Revision as of 05:05, 24 February 2008
Feel free to try out the wiki syntax in this page.
This is an example of the workflow to obtain the group members from Servicedesk.
Two workflows required are:
1. Import call_get_group_info as a standard process definition
2. Import get_group_info as standard process defintion, then add as a process actor
Call get_group_info - This is the process that calls the get_groups_info actor. It passes two variables to the
Get_groups_info WF:
a. GrpAttributes - array of string containing the requested attributes
b. GroupName - Group name (Name not UUID) of the group to retireve members from.
The GroupName variable can be set in the node labeled "Set Configurable Variables here"
get_group_info - This is the actor which does the USD logon and retrieves the information.
It will generate an XML listing of the Members of whichever group is passed.
The end result of the call_get_group_info WF will be two final variables containing comma delimted strings from the XML string and creates 2 comma delimted strings:
$strUserNameFirstLastCSV contains Firstname.Lastname
$strUserIdCSV contains userid
1) This two output strings can be used as a drop down for member selection in a form.
2) The loop can have another activity node that sends email to all users in the string, or whatever else you want to do with each element it finds in the string.
[[Get Groups Worflow Example]]
<\pre>
