Chaining Processes

kklosson · Post by **kklosson** » Sun Dec 14, 2008 5:59 pm

I will eventually have a long process that validates a couple of hundred fields. I will do this by creating processes that validate a section at a time. So I've created an action on a form that starts a process. The process it starts will call a number of processes to complete the whole validation process. I find that if I start a process directly, the process works normally. When I start the same process from another process, I just get a "process complete" message when clearly the chained process did not run.

Am I doing this correctly?

tford · Post by **tford** » Sun Dec 14, 2008 6:09 pm

Are there process inputs that you need to pass from one process to another?

tford · Post by **tford** » Sun Dec 14, 2008 6:10 pm

Have you looked at the logs?

kklosson · Post by **kklosson** » Sun Dec 14, 2008 6:13 pm

Nope. The first process is just a starter:

Process1:
Call Process2
Call Process3
etc...

Process2 works fine when I start it directly but when I start Process1, which at this point, does nothing but start Process2, it completes without any errors (which there are).

kklosson · Post by **kklosson** » Sun Dec 14, 2008 6:19 pm

Being still rather new, how does one view the logs?

kklosson · Post by **kklosson** » Sun Dec 14, 2008 6:37 pm

Disregard on the log - I think I have that figured out. But so far, it's not helping me resolve my issue.

tford · Post by **tford** » Sun Dec 14, 2008 6:51 pm

Try putting a DISPLAY MESSAGE action in the processes that you think are not firing.

When you say the logs are not helping, can you see the rules that are in the process in question being evaluated.

Tom

kklosson · Post by **kklosson** » Sun Dec 14, 2008 8:41 pm

I'll do that. Here's what I get from the log. When I start the process directly, it clearly shows that the rule failed (what I expect) and then does what it's supposed to do.

When I start the process from another process, it indicates that the attribute(s) being evaluated could not be resolved. To me, it's as if the object is no longer in context this way.

Hmmm.

kklosson · Post by **kklosson** » Sun Dec 14, 2008 9:27 pm

Based on a few trial and error procedures and viewing of logs, it seems fairly clear that when I start a process from another process, the process being called loses context of the current open object.

kklosson · Post by **kklosson** » Sun Dec 14, 2008 9:57 pm

Okay, since the record I'm validating is that of the LoggedIn user, I am able to state:

If LoggInBO.Attribute IS NOT DEFINED...

and this will work fine, but based on my reading of Processes, Rules, and Context, it seems that the BO should remain in context as the processes are started.

tford · Post by **tford** » Mon Dec 15, 2008 3:17 am

Do you still have a question?

LoggedInRegularUser.AttributeName (as well as other LoggedIn... BOs) is always in context no matter where it is used.

Tom

technopak · Post by **technopak** » Thu Jan 08, 2009 12:16 pm

I have a similar issue -

When calling a 2nd process from an initial process, the BO which was in context in the initial process cannot be referenced by the 2nd process. It seems to be not in context as far as the 2nd process is concerned. My understanding is that the BO should remain in context for other processes to use.

Can anyone clarify this ?

Peter

tford · Post by **tford** » Thu Jan 08, 2009 12:37 pm

Peter,

Have you passed it with a Process Input?

Tom

technopak · Post by **technopak** » Thu Jan 08, 2009 12:41 pm

Hi Tom,

No I haven't passed it.

Obviously I should have

Peter

technopak · Post by **technopak** » Thu Jan 08, 2009 3:57 pm

Still having some trouble -

My initial process uses two BOs, my 2nd process uses the same two BOs.

I've created Process Inputs for the 2nd process naming the two BOs and have referenced them in the code of the initial process which calls the 2nd process (USING Customer,CustomerID).

However, I am now receiving an 'Internal Error' message and the process cancels completely.

I think I'm passing the BOs properly. What could the error message mean ?

Peter