Hi Listers-
I am currently building an LDAP integration into Active Directory
(ARS6.0). I have an escalation that scans my Vendor form and pushes those
records I have specified in the LDAP URL to a temporary form that, in turn,
performs some data massaging via filter guide then updates the associated
SHR:People record. I'm receiving RPC timeouts due to the large number of
records being pushed from my escalation (Somewhere around 25,000). I've
seen many issues on this topic discussed on the List. My goal is to only
update those SHR:People records that have been modified in the last 24
hours. Since I cannot make this calculation in the LDAP URL and there is
no way that I know of to make $TIMESTAMP$ dynamic in the Run-If on my
escalation, has anyone implemented a similar solution?


UNSUBSCRIBE or access ARSlist Archives at http://www.ARSLIST.org
(Support: mailto:support@arslist.org)

I am not sure if this still stands true, but the ARDBC plugin provided by
Remedy (5.1.2 and 6.0 releases) performed a GLEWF regardless of the workflow
qualification, then proceeded to parse the results on the Remedy server side
instead of sending the qualification directly to the directory.

This only stood true for workflow that queried the directory and used >, <,
>=, <= comparisons, but did not hold true if the vendor form itself had the
<, >, <=, >= comparison.

I took advantage of this by updating the data dictionary tables directly,
(something like schemavendor), then triggering a data dictionary recache
before the escalation ran using arsignal -g.

Hope that helps

Axton

-----Original Message-----
From: Action Request System discussion list(ARSList)
[mailto:arslist@ARSLIST.ORG] On Behalf Of M Stromberg
Sent: Monday, January 24, 2005 12:38 PM
To: arslist@ARSLIST.ORG
Subject: LDAP Workflow Question

Hi Listers-
I am currently building an LDAP integration into Active Directory
(ARS6.0). I have an escalation that scans my Vendor form and pushes those
records I have specified in the LDAP URL to a temporary form that, in turn,
performs some data massaging via filter guide then updates the associated
SHR:People record. I'm receiving RPC timeouts due to the large number of
records being pushed from my escalation (Somewhere around 25,000). I've
seen many issues on this topic discussed on the List. My goal is to only
update those SHR:People records that have been modified in the last 24
hours. Since I cannot make this calculation in the LDAP URL and there is
no way that I know of to make $TIMESTAMP$ dynamic in the Run-If on my
escalation, has anyone implemented a similar solution?



UNSUBSCRIBE or access ARSlist Archives at http://www.ARSLIST.org
(Support: mailto:support@arslist.org)


UNSUBSCRIBE or access ARSlist Archives at http://www.ARSLIST.org
(Support: mailto:support@arslist.org)

Axton- Thanks for the input. Question, if you used a Filter Run Process to
run arsignal -g that causes the recache, what was the trigger that you used
to kick this off? A server event that logged when you updated schema
vendor? Or some other trigger?

-----Original Message-----
From: Axton Grams [mailto:ARSList@INSPIRATIONALTECHNOLOGIES.COM]
Sent: Monday, January 24, 2005 5:07 PM
To: arslist@ARSLIST.ORG
Subject: Re: LDAP Workflow Question


I am not sure if this still stands true, but the ARDBC plugin provided by
Remedy (5.1.2 and 6.0 releases) performed a GLEWF regardless of the workflow
qualification, then proceeded to parse the results on the Remedy server side
instead of sending the qualification directly to the directory.

This only stood true for workflow that queried the directory and used >, <,
>=, <= comparisons, but did not hold true if the vendor form itself had the
<, >, <=, >= comparison.

I took advantage of this by updating the data dictionary tables directly,
(something like schemavendor), then triggering a data dictionary recache
before the escalation ran using arsignal -g.

Hope that helps

Axton

-----Original Message-----
From: Action Request System discussion list(ARSList)
[mailto:arslist@ARSLIST.ORG] On Behalf Of M Stromberg
Sent: Monday, January 24, 2005 12:38 PM
To: arslist@ARSLIST.ORG
Subject: LDAP Workflow Question

Hi Listers-
I am currently building an LDAP integration into Active Directory
(ARS6.0). I have an escalation that scans my Vendor form and pushes those
records I have specified in the LDAP URL to a temporary form that, in turn,
performs some data massaging via filter guide then updates the associated
SHR:People record. I'm receiving RPC timeouts due to the large number of
records being pushed from my escalation (Somewhere around 25,000). I've
seen many issues on this topic discussed on the List. My goal is to only
update those SHR:People records that have been modified in the last 24
hours. Since I cannot make this calculation in the LDAP URL and there is
no way that I know of to make $TIMESTAMP$ dynamic in the Run-If on my
escalation, has anyone implemented a similar solution?



UNSUBSCRIBE or access ARSlist Archives at http://www.ARSLIST.org
(Support: mailto:support@arslist.org)



UNSUBSCRIBE or access ARSlist Archives at http://www.ARSLIST.org
(Support: mailto:support@arslist.org)


This e-mail transmission contains information that is confidential and may be privileged. It is intended only for the addressee(s) named above. If you receive this e-mail in error, please do not read, copy or disseminate it in any manner. If you are not the intended recipient, any disclosure, copying, distribution or use of the contents of this information is prohibited. Please reply to the message immediately by informing the sender that the message was misdirected. After replying, please erase it from your computer system. Your assistance in correcting this error is appreciated.


UNSUBSCRIBE or access ARSlist Archives at http://www.ARSLIST.org
(Support: mailto:support@arslist.org)

I think I create a remedy form named dual (from the Oracle/RDBMS concept)
and set an escalation to run on an interval. This same escalation used
direct sql to update the vendor information prior to the arsignal.

Axton




Axton- Thanks for the input. Question, if you used a Filter Run Process to
run arsignal -g that causes the recache, what was the trigger that you used
to kick this off? A server event that logged when you updated schema
vendor? Or some other trigger?

-----Original Message-----
From: Axton Grams [mailto:ARSList@INSPIRATIONALTECHNOLOGIES.COM]
Sent: Monday, January 24, 2005 5:07 PM
To: arslist@ARSLIST.ORG
Subject: Re: LDAP Workflow Question


I am not sure if this still stands true, but the ARDBC plugin provided by
Remedy (5.1.2 and 6.0 releases) performed a GLEWF regardless of the
workflow
qualification, then proceeded to parse the results on the Remedy server
side
instead of sending the qualification directly to the directory.

This only stood true for workflow that queried the directory and used >, <,
>=, <= comparisons, but did not hold true if the vendor form itself had the
<, >, <=, >= comparison.

I took advantage of this by updating the data dictionary tables directly,
(something like schemavendor), then triggering a data dictionary recache
before the escalation ran using arsignal -g.

Hope that helps

Axton

-----Original Message-----
From: Action Request System discussion list(ARSList)
[mailto:arslist@ARSLIST.ORG] On Behalf Of M Stromberg
Sent: Monday, January 24, 2005 12:38 PM
To: arslist@ARSLIST.ORG
Subject: LDAP Workflow Question

Hi Listers-
I am currently building an LDAP integration into Active Directory
(ARS6.0). I have an escalation that scans my Vendor form and pushes those
records I have specified in the LDAP URL to a temporary form that, in turn,
performs some data massaging via filter guide then updates the associated
SHR:People record. I'm receiving RPC timeouts due to the large number of
records being pushed from my escalation (Somewhere around 25,000). I've
seen many issues on this topic discussed on the List. My goal is to only
update those SHR:People records that have been modified in the last 24
hours. Since I cannot make this calculation in the LDAP URL and there is
no way that I know of to make $TIMESTAMP$ dynamic in the Run-If on my
escalation, has anyone implemented a similar solution?




UNSUBSCRIBE or access ARSlist Archives at http://www.ARSLIST.org
(Support: mailto:support@arslist.org)




UNSUBSCRIBE or access ARSlist Archives at http://www.ARSLIST.org
(Support: mailto:support@arslist.org)


This e-mail transmission contains information that is confidential and may
be privileged. It is intended only for the addressee(s) named above. If
you receive this e-mail in error, please do not read, copy or disseminate
it in any manner. If you are not the intended recipient, any disclosure,
copying, distribution or use of the contents of this information is
prohibited. Please reply to the message immediately by informing the sender
that the message was misdirected. After replying, please erase it from your
computer system. Your assistance in correcting this error is appreciated.



UNSUBSCRIBE or access ARSlist Archives at http://www.ARSLIST.org
(Support: mailto:support@arslist.org)


UNSUBSCRIBE or access ARSlist Archives at http://www.ARSLIST.org
(Support: mailto:support@arslist.org)