Custom mover event not getting triggered

IdentityIQ (IIQ) IIQ Discussion and Questions
,
1

Which IIQ version are you inquiring about?

[8.4p1]

Share all details about your problem, including any error messages you may have received.

I have a custom mover event set up based on departmentNumber change. The event is not getting triggered. For testing purposes, I am modifying the departmentNumber in the identity xml in the lower environment. and running the ID refresh with “process events “ checked. We are not using rapid setup. I have set the attribute as “temporary” in the identity attribute mapping. What am I missing?

mapping
mapping1791×877 39.9 KB

LCE
LCE1262×697 27.2 KB

2

Hi,

Can you please confirm after aggregation, did you completed running the Refresh identity Task with Refresh Identity Attributes such that identity Attribute department is updated with the new Value.

3

yes, I have “refresh identity attributes” checked. I am not running any aggregation since I am not updating the department number in the authoritative app. for testing, I am manually updating the department number value in debug.

4

If you update something from debug page, it wont trigger the event. Either do it from UI or do from Aggregation.

5

how do you do it from the UI?

6

Search the identity from Identity Warehouse. open it. Navigate to Identity Attributes page. There will be one Edit option you will see. CLick on it and see if department is editable or not. If it is editable then change the value.

Save it.

Run the Refresh task with Process Events.

7

It is not editable. Only thing I can edit is the password and forwarding user.

8

Go to Identity Mapping and change the Edit Mode.

9

the mapping attribute is already set to “temporary” and NOT “read only”

10

Send me the screenshot of identity attribute page of a user.

11

@dmaan There are few ways you can do this..

  • Make the identity attribute editable. In this way, as soon as you save, it’ll trigger the event.
  • Or Run the aggregation, followed by Identity Refresh.
  • Or Get the source attribute of your identity attribute(department number) and update that link attribute with the new value. Run the Identity Refresh. Ex: If deparmentNumber is mapped with DepartMentId of your HR app: HR-App1, then open the identity, go to HR-App1 link and update DepartMentId to the new value. Then run identity refresh, with refresh attributes and process events option.

Please see which option you want to try and let us know if you still see any issues.

Note: Found a fix?Help the community by marking the comment as solution. Feel free to react(:heart:,:+1:, etc.)with an emoji to show your appreciation or message me directly if your problem requires a deeper dive.

12

if you want to directly update from debug then you can use <triggerSnapshots> tag directly in Identity xml. Eg:

<Identity>
  <Attributes>
    <Map>
      <entry key="countryCode" value="USA"/>
      <entry key="displayName" value="TestUser Hunters"/>
      <entry key="divisionCode" value="CAD"/>
      <entry key="division" value="Client Admin Division"/>
      <entry key="email" value="testuser@xyz.com"/>
      <entry key="userStatus" value="OLD_VALUE"/>
	  <entry key="triggerSnapshots">
        <value>
          <Map>
            <entry key="AttributeChange">
              <value>
                <Attributes>
                  <Map>
					   <entry key="countryCode" value="USA"/>
					  <entry key="displayName" value="TestUser Hunters"/>
					  <entry key="divisionCode" value="CAD"/>
					  <entry key="division" value="Client Admin Division"/>
					  <entry key="email" value="testuser@xyz.com"/>
					  <entry key="userStatus" value="UPDATED_VALUE"/>
                  </Map>
                </Attributes>
              </value>
            </entry>
          </Map>
        </value>
      </entry>
	</Map>
  </Attributes>
  .
  .
  .
  </Identity>

Take the test user Identity attributes copy and paste same under <triggerSnapshots> and give the new value in the attribute you want to change.
now when you run refresh identity with “Process Events” as checked then it should work.

2 Likes
13

Hi @dmaan ,

In Lifecycle event options, Previous value and new Value filter.

Please make sure during updating of Identity attribute value, that you are setting value same as mentioned in Lifecycle event new Value filter.

1 Like
14

You can actually test this from debug. Perform an aggregation and refresh first so you have “TriggerSnapnots” generated in your identity XML.

Next, update the attribute value in debug page, make sure you see previous value in TriggerSnapshot and update link attribute value on debug.

Refreshing the cube after this, should trigger the lifecycle event.

1 Like
15

Hi Diwas Karki,

If your identity attribute departmentNumber’s actual source is from particular application then update the value only in the application account (under link tag) in the identity xml, do not update the identity attributes directly. So that when you run the refresh task, identity attribute will update to new value based on value provided in the link and this change in value will automatically add snapshot for attribute changes in identity xml. Then process events option in the identity refresh task will pick this change and will trigger event.

Thanks,

Sivaprakash.

1 Like