• State Suggested Answer
  • Locked Locked
  • Replies 12 replies
  • Answers 1 answer
  • Subscribers 93 subscribers
  • Views 8979 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

UNSAccountB process is not firing for INSERT events for Provisioning using Powershell Connector

Jesus.Estrada
over 6 years ago

Hi,

I want to Create Active Directory Accounts using the Powershell Connector with the OOB AD Sample.xml definition file in my Sync Editor Project.

Right now I'm able to execute the Full Sync, so the AD Accounts are under UNSAccountB but I can't Provisioning new acccounts to the Target System.

I've created a new custom UNSAccountB process for INSERT events and it's not being fired. When I run the Simulation in Designer the Process Step says "Not Generated".

Here's the Pre-Script for Generating and Generating Conditions:

The process step is a process task Projector Component - AdHocProjection with the Following Properties:

Also I've setup the provisioning process operation in order to execute the Sync Workflow for Provisioning:

 

I appreciate any help!

Thanks

Parents
  • 0 over 6 years ago
    I am not asking why you are using the PowerShell connector to synchronize AD and not the ootb AD connector...

    But I would check:

    - If the conditions in your prescript are fulfilled. Especially if the sysem type of the connection is stored at UID_UNSRoot.UID_DPRNameSpace.Ident_DPRNameSpace for your test object.
Reply
  • 0 over 6 years ago
    I am not asking why you are using the PowerShell connector to synchronize AD and not the ootb AD connector...

    But I would check:

    - If the conditions in your prescript are fulfilled. Especially if the sysem type of the connection is stored at UID_UNSRoot.UID_DPRNameSpace.Ident_DPRNameSpace for your test object.
Children
No Data