Triggering update task for MX_PERSON attribute

[kenny_vandemoortele]

Hi there,

We encounter following two problems in our IDM 7.2 SP7 enviroment. It would be great if someone could help us out!

first:

When we create a user, then the attributes department and email that we filled in in IDM are added to the user in our ABAP system.

But when we modify this user by changing the department and email attributes in IDM, then these won't update in our ABAP system. It's like the trigger is not set off...

And on the other hand, when we remove or add new privilege or business role in IDM, then this does work.

second:

We just added the new license attribute (UCLASSLICTYPE). But when we create or modify a user, this does not get into our ABAP system.

Does anyone have an idea of what could be the problem?

Many thanks in advance!

Regards,

Kenny

[Former Member · Accepted solution]

Check that your attribute(s) are added to the list that triggers a target update in the "Update System Privilege trigger attributes" pass of the Initial Load job.

Br,

Per Christian

[kenny_vandemoortele · Accepted solution]

Hello Per,

thanks very much for your reply.

I made the changes in both our test and productive IDM system and:

In our IDM testsystem, this was indeed the solution. I've added the attributes to the "update privilege trigger attributes" and now it works. All the attributes (MX_DEMARTMENT, MX_UCLASSLICENSE, ...) are updated when I modify a user.

However, in our Production Enviroment there is still something missing and we don't see a difference between the two enviroments. We've made the same changes as in the test enviroment, but when we modify a user by either changing the department or license attribute, then no jobs are triggered thus nothing happens in the job log. 

Do you maybe have any more idea's?

In any case, thanks already!!!

[former_member2987]

Hi Kenny,

But when we modify this user by changing the department and email attributes in IDM, then these won't update in our ABAP system. It's like the trigger is not set off...

Can you run a trace on the user?  Is the Modify ABAP task being called.  Easy things to check for are that the task is enabled and that you have a running dispatcher assigned to the task and job.

We just added the new license attribute (UCLASSLICTYPE). But when we create or modify a user, this does not get into our ABAP system.

You need to add the attribute to the modify ABAP User task. Add this attribute and then you should be set.

This should get you started on your troubleshooting.  Let us know what you find!

Matt

[kenny_vandemoortele]

Hello Matt,

Also a big thanks for your reply!

The Modify ABAP task wasn't triggered, but now we found the solution.

Apperently their was a global constant MX_PRIV_MODIFY_POLICY that was set as "1" and that was the problem. I understood the meaning of this constant as follows:

1 = you must specify the trigger task in the attribute

nothing or 0 = all modification in a user will set off a trigger

Is this correct?

So now both the test and productive enviroments are working as it should be.

A big thanks for all your help.

Regards,

Kenny