Skip to Content
author's profile photo Former Member
Former Member

IDM 7.2 Validation Tasks - How to Stop provisioning

Hello,

I want to implement an Add Validation Task. This task is fired before the provisioning is started. Thats exactly what I need. But I found no documentation about it. What I have done until now:

1) Added the validation Task to the repository

2) created the Task which at the moment just logs the entrytype and I tried to set the approval on "dicline"

What is happening until now:

1) A pending value is generated, which has the action ADD-Validation, which is fine.

2) nothing 😉 the function uIS_SetApproval only works in Approval tasks.

The only think I found in the documentation about the validation tasks is that nothing has to be returned. Just true or false should be delivered. But how? Do I have to set it at a context variable? If so, which one? Do I have to call a function? Which one?

Anyone who can help me here?

BR,

Christoph

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

1 Answer

  • Best Answer
    author's profile photo Former Member
    Former Member
    Posted on Oct 03, 2011 at 09:40 AM

    Hi Christoph,

    To automatically decline a validate-add task from a job, set the attribute MX_ATTR_STATE to the value 3.

    This will then behave the same as if you had an approval task, and the user pressed decline.

    Best regards

    John Erik Setsaas

    Development Architect IdM

    PS. We are working on documentation for this now.

    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member

      Hi,

      We are doing exactly this in IdM 7.1 and it works great! The only problem I have now is that the role shows status "Partially OK" which is not what I would want.

      In our case, we are provisioning to one of 2 AD's depending on the location of the user. We have put both privileges in the role, which creates 2 pending values when the role is assigned via an add member task on both repositories. We check the user location, then apply one and clear the other using MX_ATTR_STATE. As effectively this is an approval and a rejection, the role shows as "Partially OK" and this is confusing - though I understand this is correct as per standard.

      Any ideas on how to get the role status to show "OK" in this scenario?

      Cheers,

      Ian

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.