Anonymous_User Absent Member.
Absent Member.
406 views

WorkOrder vault attribute retrieval advice


Hi,

I'm working on a rule in the WorkOrder driver to delay and send emails.
The rule, without the delay and in an HR driver, works fine and looks
like this:

<rule>
<description>Send GRAD welcome email from Admissions to student on
add</description>
<conditions>
<and>
<if-operation mode="case" op="equal">add</if-operation>
<if-src-attr mode="nocase" name="Group Membership"
op="equal">\IDMVAULT\vault\groups\GRAD</if-src-attr>
</and>
</conditions>
<actions>
<do-send-email-from-template notification-dn="Security\Default
Notification Collection" template-dn="Security\Default Notification
Collection\GRAD welcome email">
<arg-string name="to">
<token-src-attr name="Internet EMail Address"/>
</arg-string>
<arg-string name="FirstName">
<token-attr name="Given Name"/>
</arg-string>
<arg-string name="LastName">
<token-attr name="Surname"/>
</arg-string>
<arg-string name="Username">
<token-attr name="CN"/>
</arg-string>
</do-send-email-from-template>
</actions>
</rule>

but, as I understand it, I need to move this rule to WorkOrder driver
pub-cp in order to achieve postponing the send.

The problem I'm running into is that I need to use the same Group
Membership evaluation logic and retrieve other values from the vault
user object, such as the Internet EMail Address and CN attributes to
form the email and that aren't in the WorkOrder object (and I don't
think I want to store them in the WO object, either). I'm thinking the
answer lies somewhere along the lines of referencing the vault object
from the DirXML-nwoContent value, e.g., vault\users\username and
extracting, but I'm not sure what exactly I would use.

I hope this makes sense and please let me know if I need to clarify
anything. Any advise would be greatly appreciated.

Thanks a lot!

Bill


--
bscully
------------------------------------------------------------------------
bscully's Profile: https://forums.netiq.com/member.php?userid=355
View this thread: https://forums.netiq.com/showthread.php?t=2893

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

Re: WorkOrder vault attribute retrieval advice

On Tue, 28 Aug 2012 14:54:02 +0000, bscully wrote:

> but, as I understand it, I need to move this rule to WorkOrder driver
> pub-cp in order to achieve postponing the send.


Right. Instead of your current do-send-email, you'll create a WO object.
Use dirxml-nwocontent to hold the DN of the object. Then, when the WO is
processed later, you get the dirxml-nwocontent and can use it to query
for everything else you need.

Geoff likes to create his own DN type attribute, so that eDirectory keeps
track of the object for you if it gets moved. dirxml-nwocontent is a
string attribute, but if you don't allow object moves, I don't see much
risk in using it this way.


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

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

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: WorkOrder vault attribute retrieval advice


Thanks. That's where I'm not sure what to do, how to query the DN using
the dirxml-nwocontent? Would you have a sample rule that you wouldn't
mind sharing, please?

dgersic;12108 Wrote:
> On Tue, 28 Aug 2012 14:54:02 +0000, bscully wrote:
>
> > but, as I understand it, I need to move this rule to WorkOrder

> driver
> > pub-cp in order to achieve postponing the send.

>
> Right. Instead of your current do-send-email, you'll create a WO
> object.
> Use dirxml-nwocontent to hold the DN of the object. Then, when the WO
> is
> processed later, you get the dirxml-nwocontent and can use it to query
> for everything else you need.
>
> Geoff likes to create his own DN type attribute, so that eDirectory
> keeps
> track of the object for you if it gets moved. dirxml-nwocontent is a
> string attribute, but if you don't allow object moves, I don't see
> much
> risk in using it this way.
>
>
> --
> --------------------------------------------------------------------------
> David Gersic
> dgersic_@_niu.edu
> Knowledge Partner
> http://forums.netiq.com
>
> Please post questions in the forums. No support provided via
> email.



--
bscully
------------------------------------------------------------------------
bscully's Profile: https://forums.netiq.com/member.php?userid=355
View this thread: https://forums.netiq.com/showthread.php?t=2893

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: WorkOrder vault attribute retrieval advice


So, for example, I'm using the following rule in the WO pub-cp and here
I experimented with writing the email address to DirXML-Other1. I would
love to see a rule that was pulling the vault DN's attributes instead.
Thanks!

<rule>
<description>Send TIU ALL welcome email from IT to student on
add</description>
<conditions>
<and>
<if-operation mode="case" op="equal">add</if-operation>
<if-class-name op="equal">DirXML-WorkToDo</if-class-name>
</and>
</conditions>
<actions>
<do-send-email-from-template notification-dn="Security\Default
Notification Collection" template-dn="Security\Default Notification
Collection\TIU ALL welcome email from IT">
<arg-string name="to">
<token-attr name="DirXML-Other1"/>
</arg-string>
<arg-string name="FirstName">
<token-attr name="Given Name"/>
</arg-string>
<arg-string name="LastName">
<token-attr name="Surname"/>
</arg-string>
<arg-string name="Username">
<token-attr name="CN"/>
</arg-string>
</do-send-email-from-template>
<do-veto/>
</actions>
</rule>


--
bscully
------------------------------------------------------------------------
bscully's Profile: https://forums.netiq.com/member.php?userid=355
View this thread: https://forums.netiq.com/showthread.php?t=2893

0 Likes
Knowledge Partner
Knowledge Partner

Re: WorkOrder vault attribute retrieval advice

Replace these tokens that you use to build strings:

<token-attr name="Given Name"/>

With source attribute, specifying which object instead, more like this:


<token-src-attr name="Full Name">
<arg-dn>
<token-op-attr name="DirXML-nwoContent"/>
</arg-dn>
</token-src-attr>


On 8/28/2012 1:14 PM, bscully wrote:
>
> So, for example, I'm using the following rule in the WO pub-cp and here
> I experimented with writing the email address to DirXML-Other1. I would
> love to see a rule that was pulling the vault DN's attributes instead.
> Thanks!
>
> <rule>
> <description>Send TIU ALL welcome email from IT to student on
> add</description>
> <conditions>
> <and>
> <if-operation mode="case" op="equal">add</if-operation>
> <if-class-name op="equal">DirXML-WorkToDo</if-class-name>
> </and>
> </conditions>
> <actions>
> <do-send-email-from-template notification-dn="Security\Default
> Notification Collection" template-dn="Security\Default Notification
> Collection\TIU ALL welcome email from IT">
> <arg-string name="to">
> <token-attr name="DirXML-Other1"/>
> </arg-string>
> <arg-string name="FirstName">
> <token-attr name="Given Name"/>
> </arg-string>
> <arg-string name="LastName">
> <token-attr name="Surname"/>
> </arg-string>
> <arg-string name="Username">
> <token-attr name="CN"/>
> </arg-string>
> </do-send-email-from-template>
> <do-veto/>
> </actions>
> </rule>
>
>


0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: WorkOrder vault attribute retrieval advice

On Tue, 28 Aug 2012 17:19:30 +0000, Geoffrey Carman wrote:

> Replace these tokens that you use to build strings:
>
> <token-attr name="Given Name"/>
>
> With source attribute, specifying which object instead, more like this:


You mean, of course, _destination_ attribute, since this is on the
Publisher channel.


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

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

0 Likes
Knowledge Partner
Knowledge Partner

Re: WorkOrder vault attribute retrieval advice

On 8/28/2012 3:00 PM, David Gersic wrote:
> On Tue, 28 Aug 2012 17:19:30 +0000, Geoffrey Carman wrote:
>
>> Replace these tokens that you use to build strings:
>>
>> <token-attr name="Given Name"/>
>>
>> With source attribute, specifying which object instead, more like this:

>
> You mean, of course, _destination_ attribute, since this is on the
> Publisher channel.


Why yes, yes I do. Actually, since he used token-attr that would not
have worked either in his example in the WO driver.

Good points.

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: WorkOrder vault attribute retrieval advice


Geoff, thanks, this is working well:

<arg-string name="to">
<token-dest-attr name="Internet EMail Address">
<arg-dn>
<token-op-attr name="DirXML-nwoContent"/>
</arg-dn>
</token-dest-attr>
</arg-string>

My question is, how do I ses this sort of logic for querying group
membership? I don't think the following is going to work for me from
the WO Driver:

<conditions>
<and>
<if-operation mode="case" op="equal">add</if-operation>
<if-class-name op="equal">DirXML-WorkToDo</if-class-name>
<if-dest-attr mode="nocase" name="Group Membership"
op="equal">\IDMVAULT\vault\groups\dotcms_GRAD</if-dest-attr>
</and>
</conditions>

Thanks


--
bscully
------------------------------------------------------------------------
bscully's Profile: https://forums.netiq.com/member.php?userid=355
View this thread: https://forums.netiq.com/showthread.php?t=2893

0 Likes
Knowledge Partner
Knowledge Partner

Re: WorkOrder vault attribute retrieval advice

The If local variable test does something unexpected if used on a
nodeset compare.

Set local variable MEMBERS to dest-attr member (from object DN from
DirXML-nwoContent) as a nodeset.

Now you can test, if local variable where IF local variable TARGET-GROUP
is equal $MEMBERS$ should return true if the single value is in the list
and false if not.

You can read more about this in this article:
www.novell.com/communities/node/13383/common-mistakes-newcomers-idm-make-part-9

As a side note, you can read more Work Order concepts in this article:
http://community.netiq.com/blogs/security_webb/archive/2012/07/13/netiq-identity-manager-work-order-driver-concepts.aspx


On 8/29/2012 12:04 PM, bscully wrote:
>
> Geoff, thanks, this is working well:
>
> <arg-string name="to">
> <token-dest-attr name="Internet EMail Address">
> <arg-dn>
> <token-op-attr name="DirXML-nwoContent"/>
> </arg-dn>
> </token-dest-attr>
> </arg-string>
>
> My question is, how do I ses this sort of logic for querying group
> membership? I don't think the following is going to work for me from
> the WO Driver:
>
> <conditions>
> <and>
> <if-operation mode="case" op="equal">add</if-operation>
> <if-class-name op="equal">DirXML-WorkToDo</if-class-name>
> <if-dest-attr mode="nocase" name="Group Membership"
> op="equal">\IDMVAULT\vault\groups\dotcms_GRAD</if-dest-attr>
> </and>
> </conditions>
>
> Thanks
>
>


0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: WorkOrder vault attribute retrieval advice


Your second article (concepts) was very helpful in pointing our why I'm
getting the error on nwoStatus -- I've got a veto in my pub at the end
of my WO rule. Interestingly, if I remove the veto, then I'm left with
a DO- object. Most of this rule I've grabbed out of the work_order.pdf
under using an HR driver. I guess there's no harm in leaving the veto
and setting the WO object to delete on error. You mentioned in the
article that you left it this way, too. If you've since done something
better, I'd be interested in reading up on what you did.

I'm looking forward to pouring over your variable suggestion for
evaluating groups. Thanks for that too!

geoffc;12186 Wrote:
> The If local variable test does something unexpected if used on a
> nodeset compare.
>
> Set local variable MEMBERS to dest-attr member (from object DN from
> DirXML-nwoContent) as a nodeset.
>
> Now you can test, if local variable where IF local variable
> TARGET-GROUP
> is equal $MEMBERS$ should return true if the single value is in the
> list
> and false if not.
>
> You can read more about this in this article:
> http://tinyurl.com/8ndbslh
>
> As a side note, you can read more Work Order concepts in this article:
> http://tinyurl.com/9fny234
>
>
> On 8/29/2012 12:04 PM, bscully wrote:
> >
> > Geoff, thanks, this is working well:
> >
> > <arg-string name="to">
> > <token-dest-attr name="Internet EMail Address">
> > <arg-dn>
> > <token-op-attr name="DirXML-nwoContent"/>
> > </arg-dn>
> > </token-dest-attr>
> > </arg-string>
> >
> > My question is, how do I ses this sort of logic for querying group
> > membership? I don't think the following is going to work for me

> from
> > the WO Driver:
> >
> > <conditions>
> > <and>
> > <if-operation mode="case" op="equal">add</if-operation>
> > <if-class-name op="equal">DirXML-WorkToDo</if-class-name>
> > <if-dest-attr mode="nocase" name="Group Membership"
> > op="equal">\IDMVAULT\vault\groups\dotcms_GRAD</if-dest-attr>
> > </and>
> > </conditions>
> >
> > Thanks
> >
> >



--
bscully
------------------------------------------------------------------------
bscully's Profile: https://forums.netiq.com/member.php?userid=355
View this thread: https://forums.netiq.com/showthread.php?t=2893

0 Likes
Knowledge Partner
Knowledge Partner

Re: WorkOrder vault attribute retrieval advice


> I'm looking forward to pouring over your variable suggestion for
> evaluating groups. Thanks for that too!


Heck, here is the whole list of 310+ articles:
http://wiki.novell.com/index.php/Geoffrey_Carman%27s_personal_collection

Sorted by topic too. So you can read what is interesting at the time.



> geoffc;12186 Wrote:
>> The If local variable test does something unexpected if used on a
>> nodeset compare.
>>
>> Set local variable MEMBERS to dest-attr member (from object DN from
>> DirXML-nwoContent) as a nodeset.
>>
>> Now you can test, if local variable where IF local variable
>> TARGET-GROUP
>> is equal $MEMBERS$ should return true if the single value is in the
>> list
>> and false if not.
>>
>> You can read more about this in this article:
>> http://tinyurl.com/8ndbslh
>>
>> As a side note, you can read more Work Order concepts in this article:
>> http://tinyurl.com/9fny234
>>
>>
>> On 8/29/2012 12:04 PM, bscully wrote:
>>>
>>> Geoff, thanks, this is working well:
>>>
>>> <arg-string name="to">
>>> <token-dest-attr name="Internet EMail Address">
>>> <arg-dn>
>>> <token-op-attr name="DirXML-nwoContent"/>
>>> </arg-dn>
>>> </token-dest-attr>
>>> </arg-string>
>>>
>>> My question is, how do I ses this sort of logic for querying group
>>> membership? I don't think the following is going to work for me

>> from
>>> the WO Driver:
>>>
>>> <conditions>
>>> <and>
>>> <if-operation mode="case" op="equal">add</if-operation>
>>> <if-class-name op="equal">DirXML-WorkToDo</if-class-name>
>>> <if-dest-attr mode="nocase" name="Group Membership"
>>> op="equal">\IDMVAULT\vault\groups\dotcms_GRAD</if-dest-attr>
>>> </and>
>>> </conditions>
>>>
>>> Thanks
>>>
>>>

>
>


0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: WorkOrder vault attribute retrieval advice


Sweet, bookmarked, thanks!

So, great advice on querying the group variable. That part's working
nicely, but I forgot to account for multiple variables, many groups in
this case. As you can see from below, it's assigning the first group to
the member variable. Any thoughts of how I might get around this? I
commonly do something like this:

<if-src-attr mode="nocase" name="Group Membership"
op="equal">\IDMVAULT\vault\groups\dotcms_UOLP</if-src-attr>

but I guess it's different with variables.

Thanks again!

[08/30/12 15:26:16.559]:WorkOrder PT: Applying rule 'Set local
variables to test existence of program groups and for placement'.
[08/30/12 15:26:16.559]:WorkOrder PT: Action:
do-set-local-variable("member",scope="policy",token-dest-attr("Group
Membership",arg-dn(token-op-attr("DirXML-nwoContent")))).
[08/30/12 15:26:16.560]:WorkOrder PT:
arg-string(token-dest-attr("Group
Membership",arg-dn(token-op-attr("DirXML-nwoContent"))))
[08/30/12 15:26:16.560]:WorkOrder PT: token-dest-attr("Group
Membership",arg-dn(token-op-attr("DirXML-nwoContent")))
[08/30/12 15:26:16.560]:WorkOrder PT:
arg-dn(token-op-attr("DirXML-nwoContent"))
[08/30/12 15:26:16.560]:WorkOrder PT:
token-op-attr("DirXML-nwoContent")
[08/30/12 15:26:16.560]:WorkOrder PT: Token Value:
"vault\users\zmflemmi".
[08/30/12 15:26:16.561]:WorkOrder PT: Arg Value:
"vault\users\zmflemmi".
[08/30/12 15:26:16.561]:WorkOrder PT: Query from policy
[08/30/12 15:26:16.561]:WorkOrder PT:
<nds dtdversion="4.0" ndsversion="8.x">
<source>
<product edition="Standard" version="4.0.1.0">DirXML</product>
<contact>Novell, Inc.</contact>
</source>
<input>
<query dest-dn="vault\users\zmflemmi" scope="entry">
<read-attr attr-name="Group Membership"/>
</query>
</input>
</nds>
[08/30/12 15:26:16.562]:WorkOrder PT: Pumping XDS to
eDirectory.
[08/30/12 15:26:16.562]:WorkOrder PT: Performing operation
query for vault\users\zmflemmi.
[08/30/12 15:26:16.562]:WorkOrder PT: --JCLNT--
\IDMVAULT\services\DriverSet\WorkOrder Driver - Publisher : Duplicating
: context = 872480846, tempContext = 872480841
[08/30/12 15:26:16.563]:WorkOrder PT: --JCLNT--
\IDMVAULT\services\DriverSet\WorkOrder Driver - Publisher : Calling free
on tempContext = 872480841
[08/30/12 15:26:16.563]:WorkOrder PT: Query from policy
result
[08/30/12 15:26:16.563]:WorkOrder PT:
<nds dtdversion="4.0" ndsversion="8.x">
<source>
<product edition="Standard" version="4.0.1.0">DirXML</product>
<contact>Novell, Inc.</contact>
</source>
<output>
<instance class-name="User" event-id="0"
qualified-src-dn="O=vault\OU=users\CN=zmflemmi"
src-dn="\IDMVAULT\vault\users\zmflemmi" src-entry-id="51187">
<attr attr-name="Group Membership">
<value timestamp="1346358302#371"
type="dn">\IDMVAULT\vault\groups\dotcms_DFLD</value>
<value timestamp="1346358302#361"
type="dn">\IDMVAULT\vault\groups\dotcms_UNDG</value>
<value timestamp="1346358302#351"
type="dn">\IDMVAULT\vault\groups\dotcms_UOLP</value>
<value timestamp="1346358302#341"
type="dn">\IDMVAULT\vault\groups\dotcms_BUSN</value>
<value timestamp="1346358302#331"
type="dn">\IDMVAULT\vault\groups\dotcms_students</value>
<value timestamp="1346358302#39"
type="dn">\IDMVAULT\vault\groups\GoogleApps</value>
</attr>
</instance>
<status event-id="0" level="success"></status>
</output>
</nds>
[08/30/12 15:26:16.566]:WorkOrder PT: Token Value:
"\IDMVAULT\vault\groups\dotcms_DFLD".
[08/30/12 15:26:16.566]:WorkOrder PT: Arg Value:
"\IDMVAULT\vault\groups\dotcms_DFLD".


geoffc;12264 Wrote:
>
> > I'm looking forward to pouring over your variable suggestion for
> > evaluating groups. Thanks for that too!

>
> Heck, here is the whole list of 310+ articles:
> http://tinyurl.com/d5tnqyo
>
> Sorted by topic too. So you can read what is interesting at the time.
>
>
>
> > geoffc;12186 Wrote:
> >> The If local variable test does something unexpected if used on a
> >> nodeset compare.
> >>
> >> Set local variable MEMBERS to dest-attr member (from object DN from
> >> DirXML-nwoContent) as a nodeset.
> >>
> >> Now you can test, if local variable where IF local variable
> >> TARGET-GROUP
> >> is equal $MEMBERS$ should return true if the single value is in the
> >> list
> >> and false if not.
> >>
> >> You can read more about this in this article:
> >> http://tinyurl.com/8ndbslh
> >>
> >> As a side note, you can read more Work Order concepts in this

> article:
> >> http://tinyurl.com/9fny234
> >>
> >>
> >> On 8/29/2012 12:04 PM, bscully wrote:
> >>>
> >>> Geoff, thanks, this is working well:
> >>>
> >>> <arg-string name="to">
> >>> <token-dest-attr name="Internet EMail Address">
> >>> <arg-dn>
> >>> <token-op-attr name="DirXML-nwoContent"/>
> >>> </arg-dn>
> >>> </token-dest-attr>
> >>> </arg-string>
> >>>
> >>> My question is, how do I ses this sort of logic for querying group
> >>> membership? I don't think the following is going to work for me
> >> from
> >>> the WO Driver:
> >>>
> >>> <conditions>
> >>> <and>
> >>> <if-operation mode="case" op="equal">add</if-operation>
> >>> <if-class-name op="equal">DirXML-WorkToDo</if-class-name>
> >>> <if-dest-attr mode="nocase" name="Group Membership"
> >>> op="equal">\IDMVAULT\vault\groups\dotcms_GRAD</if-dest-attr>
> >>> </and>
> >>> </conditions>
> >>>
> >>> Thanks
> >>>
> >>>

> >
> >



--
bscully
------------------------------------------------------------------------
bscully's Profile: https://forums.netiq.com/member.php?userid=355
View this thread: https://forums.netiq.com/showthread.php?t=2893

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: WorkOrder vault attribute retrieval advice

On Thu, 30 Aug 2012 20:44:01 +0000, bscully wrote:

> So, great advice on querying the group variable. That part's working
> nicely, but I forgot to account for multiple variables, many groups in
> this case.


For group memberships, you need the local variable to be a nodeset.


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

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

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: WorkOrder vault attribute retrieval advice


Ahhh, thanks for pointing me in the right direction. Off I go to learn
about nodesets.


--
bscully
------------------------------------------------------------------------
bscully's Profile: https://forums.netiq.com/member.php?userid=355
View this thread: https://forums.netiq.com/showthread.php?t=2893

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: WorkOrder vault attribute retrieval advice

On Thu, 30 Aug 2012 17:14:02 +0000, bscully wrote:

> Your second article (concepts) was very helpful in pointing our why I'm
> getting the error on nwoStatus -- I've got a veto in my pub at the end
> of my WO rule.


You want to veto at the end of the publisher, so that no DO object is
created. You can avoid the status=error happening by doing something that
shouldn't matter, like:


<rule>
<description>Send Email Notification</description>
<comment xml:space="preserve">Send an email notification of the pending
deprovision of this account.

Note: The do-clear-dest-attr() at the end of this rule is a workaround.
Its purpose is to ensure that an event is processed, resulting in a
"Success" status return to the Subscriber channel. Without this, the lack
of a "Success" return is interpreted as an "Error".</comment>
<conditions>
<and>
<if-class-name mode="nocase" op="equal">DirXML-WorkToDo</if-class-name>
</and>
</conditions>
<actions>
<do-set-local-variable name="order-dest-dn">
<arg-string>
<token-attr name="DirXML-nwoContent"/>
</arg-string>
</do-set-local-variable>
<do-send-email server="smtp.cso.niu.edu" type="html">
<arg-string name="to">
<token-local-variable name="emailaddress"/>
</arg-string>
<arg-string name="from">
<token-text xml:space="preserve" xmlns:xml="http://www.w3.org/
XML/1998/namespace">noreply@niu.edu</token-text>
</arg-string>
<arg-string name="subject">
<token-text xml:space="preserve" xmlns:xml="http://www.w3.org/
XML/1998/namespace">Your Account is scheduled to Expire</token-text>
</arg-string>
<arg-string name="message">
<token-local-variable name="EmailMessageBody"/>
</arg-string>
</do-send-email>
<do-clear-dest-attr-value name="accessCardNumber">
<arg-dn>
<token-local-variable name="order-dest-dn"/>
</arg-dn>
</do-clear-dest-attr-value>
<do-veto/>
</actions>
</rule>



--
--------------------------------------------------------------------------
David Gersic dgersic_@_niu.edu
Knowledge Partner http://forums.netiq.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.