× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  1.  Home
  2. MIDRANGE-L
  3. May 2013

Re: Preventing recursive call exceptions on triggers, or at least keeping them out of the joblog?

On 16 May 2013 10:00, James H. H. Lampert wrote:
We just got a customer complaint about recursive call exceptions in
the joblog from the trigger-based workflow scripting system in our
CRM product.

Since "workflow scripts cannot trip other workflow scripts" is a
known and published limitation of workflow (as well it should be!),
and the workflow program is on an "after" trigger, *having* recursive
call exceptions is not an issue (although preventing them would be
better than simply ignoring them). But can anything be done to keep
them out of the joblog?

So what is the message in the spooled LOG(4 0 *SECLVL) joblog, and what is the name of the program that implements the *AFTER trigger?

From what is provided already, I believe the answer is to use a language, or a feature of the chosen language, that allows\supports recursion for the program that is assigned to be the TRIGGER for the file.


As an Amazon Associate we earn from qualifying purchases.

This thread ...
Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.