• State Not Answered
  • Locked Locked
  • Replies 1 reply
  • Subscribers 95 subscribers
  • Views 4174 views
  • Users 0 members are here
Options
Related
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

How to add Users to AD Groups using Process Orchestrations

andrew.mcdermitt
over 8 years ago

Hi,

 

I am trying to have create a service item that has an external call in it that fires an event for a process orchestration.  I want this process orchestration to be able to add the user that ordered the service item to an AD Group.  There are a number of different AD Groups that the user could get added to, so there would be some processing (which is why I do not have the AD Group attached to the service item, like normal).

I see that when a person gets added into an AD Group in AD, the VI_ADS_ADSAccountInADSGroupTotal_Insert process orchestration runs to add them to the group in AD.  I created a process orchestration that has a process task of HandleObjectComponent - Insert with an ObjectType of "ADSAccountINADSGroupTotal", val_UID_ADSAccount with the UID_ADSAccount, and val_UID_ADS_Group with the UID_ADSGroup.

When I try and run this process orchestration, they get added into the ADSAccountINADSGroupTotal table, but the process orchestration to adds them to the group in AD does not run.  The VI_ADS_ADSAccountInADSGroupTotal_Insert orchestration runs on INSERT_SYNC, so it is telling me that the event is not triggering.

Any thoughts?

Thanks!

Parents
  • 0 over 8 years ago
    In the approval workflow associated with your service item you could use the out of the box EX procedure that raises an EVENT, then have your process Chain trigger on that event and do the business processing required to determine what AD group to assign. In this process chain you could make another request PersonWantsOrg entry for the AD group with a empty approval workflow and possibly relate the two requests together using the child/parent PSO key. This way if the original request was unsubscribed or expired you could trap this and also unsubscribe the second request for the AD group.
Reply
  • 0 over 8 years ago
    In the approval workflow associated with your service item you could use the out of the box EX procedure that raises an EVENT, then have your process Chain trigger on that event and do the business processing required to determine what AD group to assign. In this process chain you could make another request PersonWantsOrg entry for the AD group with a empty approval workflow and possibly relate the two requests together using the child/parent PSO key. This way if the original request was unsubscribed or expired you could trap this and also unsubscribe the second request for the AD group.
Children
No Data