Welcome Serena Central users! CLICK HERE
The migration of the Serena Central community is currently underway. Be sure to read THIS MESSAGE to get your new login set up to access your account.
iammi Absent Member.
Absent Member.
320 views

The oposite of Strip Operation Attribute ??


Hello,

In my Loop Back driver, I receive a creation event of a user, in the
logs of my driver I notice the XML input into the driver (the user
data)

when I do "Strip Operation Attribute" on a given attribut it
disappears

What I want to do is the opposite of "Strip Operation Attribute", but
no "Add Operation Attribute" is available, I would like to add some
attributs to my input entry in "Input Transformation Policy"

what must I use ? set default attribut value ? set source attribut?

I dont want to see in the logs any add attribut operation, I want just
after aplying the ploicy in "Input Transformation" to see the attribut
in the user data

I will be grateful if you give me some dirxml samples

Regards,


--
iammi
------------------------------------------------------------------------
iammi's Profile: http://forums.novell.com/member.php?userid=71308
View this thread: http://forums.novell.com/showthread.php?t=450004

Labels (1)
0 Likes
5 Replies
Knowledge Partner
Knowledge Partner

Re: The oposite of Strip Operation Attribute ??

On 12/24/2011 4:46 PM, iammi wrote:
>
> Hello,
>
> In my Loop Back driver, I receive a creation event of a user, in the
> logs of my driver I notice the XML input into the driver (the user
> data)
>
> when I do "Strip Operation Attribute" on a given attribut it
> disappears
>
> What I want to do is the opposite of "Strip Operation Attribute", but
> no "Add Operation Attribute" is available, I would like to add some
> attributs to my input entry in "Input Transformation Policy"
>
> what must I use ? set default attribut value ? set source attribut?
>
> I dont want to see in the logs any add attribut operation, I want just
> after aplying the ploicy in "Input Transformation" to see the attribut
> in the user data
>
> I will be grateful if you give me some dirxml samples


Add dest attr will inlcude an op attr in your document.

if you do not want it to show up in trace, that is harder.

You could clone op attr if you want the same value from an existing
attribute in the event document.

You can clone by XPATH if you have the XML handy or built.

Not sure what you are really trying to do here.

0 Likes
iammi Absent Member.
Absent Member.

Re: The oposite of Strip Operation Attribute ??


You can clone by XPATH if you have the XML handy or built. ---> do you
have any examples ?

Not sure what you are really trying to do here --> am I not plain on
asking the question ? I want just to add an attribut to the current
document, for example calculating displayName attribut (not available in
the document) from givenName and Surname, and put it into the current
document in "Input Transformation Policy"

Some king of modifying the input document to add an operation attribut,
is that possible ?

Thanks in advance.


--
iammi
------------------------------------------------------------------------
iammi's Profile: http://forums.novell.com/member.php?userid=71308
View this thread: http://forums.novell.com/showthread.php?t=450004

0 Likes
Knowledge Partner
Knowledge Partner

Re: The oposite of Strip Operation Attribute ??

On 12/24/2011 6:26 PM, iammi wrote:
>
> You can clone by XPATH if you have the XML handy or built. ---> do you
> have any examples ?
>
> Not sure what you are really trying to do here --> am I not plain on
> asking the question ? I want just to add an attribut to the current
> document, for example calculating displayName attribut (not available in
> the document) from givenName and Surname, and put it into the current
> document in "Input Transformation Policy"
>
> Some king of modifying the input document to add an operation attribut,
> is that possible ?


add dest attr


0 Likes
Knowledge Partner
Knowledge Partner

Re: The oposite of Strip Operation Attribute ??

On Sat, 24 Dec 2011 23:26:01 +0000, iammi wrote:

> Not sure what you are really trying to do here --> am I not plain on
> asking the question ? I want just to add an attribut to the current
> document, for example calculating displayName attribut (not available in
> the document) from givenName and Surname, and put it into the current
> document in "Input Transformation Policy"


The "add destination attribute" token is the one you need to use. You can
then calculate the value (attribute / given name + space + attribute
surname) to use for displayName.


--
--------------------------------------------------------------------------
David Gersic dgersic_@_niu.edu
Knowledge Partner http://forums.novell.com

Please post questions in the forums. No support provided via email.

0 Likes
Knowledge Partner
Knowledge Partner

Re: The oposite of Strip Operation Attribute ??

On Sat, 24 Dec 2011 21:46:01 +0000, iammi wrote:

> What I want to do is the opposite of "Strip Operation Attribute", but no
> "Add Operation Attribute" is available, I would like to add some
> attributs to my input entry in "Input Transformation Policy"


Incidently, synthesizing attribute values in the Input Transform is not a
good idea. You may want to read my series of articles on the purposes for
the various parts of IDM:

http://www.novell.com/communities/node/6679/guided-tour-novell-identity-
manager
http://www.novell.com/communities/node/6696/guided-tour-novell-identity-
manager
http://www.novell.com/communities/node/6697/guided-tour-novell-identity-
manager

The Input Transform is best used to "fix" the values of the attributes on
the way in. As an example, if the source system provides phone numbers as
(xxx)yyy-nnnn and you need them in the ID vault formatted as xxx-yyy-nnnn,
then the Input Transform is the place to do that. (A complimentary
reformat, on the Output Transform, may also be needed to change xxx-yyy-
nnnn to (xxx)yyy-nnnn.)

If you are synthesizing an attribute, like displayName, you need to
consider the various events that could influence its value, as well as
whether (or not) the attribute can be multivalued. On object creation,
you may want (need) to supply attribute values that are synthesized, and
the obvious choice may be to put the rules for doing so on the Create
Rule. This, then, limits the scope to <add> operations.

But what happens later if the surname changes? Now you also need to
handle <modify> operations, updating (adding or replacing) the displayName
with the new surname and the unchanged givenName. This is best done on
the Command Transform.

This, then, brings up another point to consider. The Command Transform
applies to <add> _and_ <modify> documents. And it's often better to have
one set of rules in a single policy, rather than having multiple policies
doing similar things.

So your best solution may be to have a single policy, on the Command
Transform, that handles both <add> events (synthesize value) and <modify>
events. If it is well named, it will then be easy to find and update
later as needed.


--
--------------------------------------------------------------------------
David Gersic dgersic_@_niu.edu
Knowledge Partner http://forums.novell.com

Please post questions in the forums. No support provided via email.

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.