Process call Considerations and Credentials Cache

Seen below is the selection for calling a process either synchronous or asynchronous. Regardless of the method chosen, the child process is ultimately owned by the K2 server and the K2 service account. Therefore, if the child process accesses a LOB resource and that resource requires a credentials cache, the K2 server service account would need to be cached against that security label and this in addition to any user credentials that may be cached as well.

Avoiding errors for LOB systems when calling the child process

There are two instances where an authentication error can take place, where the child or parent and child processes may go into error or not complete.

The Process, Folio and Type of Call and the Connections wizard work together in terms of setting how a child process is called and with what credentials.

Synchronous Call: In a synchronous call, the parent process waits for the child to complete. If there was an authentication error both the parent and child process would be in an error state. The child process because of the authentication error and the parent because the process will only move onto the next activity when the child returns that data it is expecting.

Asynchronous Call: In a synchronous call, the parent process passes data to the child process and then moves on to the next activity. If there are any authentication errors, the child process will not be able to complete. In this case the use of the folio is very useful as it would link the parent process to the child.