rjreisbi Absent Member.
Absent Member.
521 views

IDM453 changes set-operation-association behavior


Hello,

I recently upgraded to IDM453 Engine and Remote Loader. In one of my
custom HL7 drivers (from EST Group, LLC) there was code in the Sub Event
Transform to "Set-Operational-Association", this would let the
transaction flow to the Output Transformation to be processed, with out
becoming a synthetic add. Prior to IDM 453, this would also add that
association to the object. With 453 installed, it does still by pass
the synthetic add, but does not add the association, which caused issues
in my custom driver on the second transaction from that object. I have
fixed by using the Add-association and set-operational-association in a
"if" policy. This was just the quick fix that I used, I am now going to
reexamine the whole driver, but it is working again.

Just an observation that I wanted to share 🙂

Thanks,


--
rjreisbi
------------------------------------------------------------------------
rjreisbi's Profile: https://forums.netiq.com/member.php?userid=2906
View this thread: https://forums.netiq.com/showthread.php?t=55512

Labels (1)
0 Likes
5 Replies
Anonymous_User Absent Member.
Absent Member.

Re: IDM453 changes set-operation-association behavior

rjreisbi wrote:

>
> I recently upgraded to IDM453 Engine and Remote Loader. In one of my
> custom HL7 drivers (from EST Group, LLC) there was code in the Sub
> Event Transform to "Set-Operational-Association", this would let the
> transaction flow to the Output Transformation to be processed, with
> out becoming a synthetic add. Prior to IDM 453, this would also add
> that association to the object. With 453 installed, it does still by
> pass the synthetic add, but does not add the association, which
> caused issues in my custom driver on the second transaction from that
> object. I have fixed by using the Add-association and
> set-operational-association in a "if" policy. This was just the quick
> fix that I used, I am now going to reexamine the whole driver, but it
> is working again.


Thanks for this. I am using similar logic in a driver I am working on
right now and will likely stumble across this problem in the next day
or so.

Slightly worrying though as this is the second issue I have heard about
related to changes to long-standing association logic and IDM 4.5.x in
recent times.
0 Likes
rjreisbi Absent Member.
Absent Member.

Re: IDM453 changes set-operation-association behavior


What was the other that other issue that you speak of...I have 48+
drivers, and find it impossible to test everything.

Thanks,


--
rjreisbi
------------------------------------------------------------------------
rjreisbi's Profile: https://forums.netiq.com/member.php?userid=2906
View this thread: https://forums.netiq.com/showthread.php?t=55512

0 Likes
Knowledge Partner
Knowledge Partner

Re: IDM453 changes set-operation-association behavior

rjreisbi <rjreisbi@no-mx.forums.microfocus.com> wrote:
>

What was the other that other issue that you speak of...I have 48+
drivers, and find it impossible to test everything.
>
>


The other issue is that changing association state from 3 to 4 no longer
triggers a re-migrate.

--
If you find this post helpful and are logged into the web interface, show
your appreciation and click on the star below...
Alex McHugh - Knowledge Partner - Stavanger, Norway
Who are the Knowledge Partners
If you appreciate my comments, please click the Like button.
If I have resolved your issue, please click the Accept as Solution button.
0 Likes
Knowledge Partner
Knowledge Partner

Re: IDM453 changes set-operation-association behavior

rjreisbi wrote:

> there was code in the Sub Event
> Transform to "Set-Operational-Association", this would let the
> transaction flow to the Output Transformation to be processed, with out
> becoming a synthetic add. Prior to IDM 453, this would also add that
> association to the object. With 453 installed, it does still by pass
> the synthetic add, but does not add the association, which caused issues
> in my custom driver on the second transaction from that object.


Are you sure about this? I was under the impression that
<do-set-op-association> has always (?) only modified the current operation -
not the object in ID Vault - and you'd have to trow in an additional token
<do-add-association> to make it permanent. For exactly that reason I'm using
something like this in my loopback drivers:

<rule notrace="true">
<description>Add Association</description>
<comment name="author" xml:space="preserve">Lothar Haeger</comment>
<conditions>
<and>
<if-association op="not-associated"/>
</and>
</conditions>
<actions>
<do-set-local-variable name="guid" scope="policy">
<arg-string>
<token-src-attr name="GUID"/>
</arg-string>
</do-set-local-variable>
<do-set-op-association>
<arg-association>
<token-xpath expression="es:decodeGUID($guid)"/>
</arg-association>
</do-set-op-association>
<do-add-association>
<arg-association>
<token-association/>
</arg-association>
</do-add-association>
</actions>
</rule>


--
http://www.is4it.de/en/solution/identity-access-management/
______________________________________________
https://www.is4it.de/identity-access-management
0 Likes
rjreisbi Absent Member.
Absent Member.

Re: IDM453 changes set-operation-association behavior


I am about 99% positive, as it was working before, and not after the 453
upgrade. I did not catch it in my lab, and it was 3 days into
production before it was caught. I had to backtrack and fix about 60
users, so not too bad, but could have been worse. I no longer have a
452 system to test with, and it is not worth standing up to verify. My
new code is almost exactly what you have included, except I am using the
workforceID as the association value.

Thanks -


--
rjreisbi
------------------------------------------------------------------------
rjreisbi's Profile: https://forums.netiq.com/member.php?userid=2906
View this thread: https://forums.netiq.com/showthread.php?t=55512

0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.