Version: Adeptia Suite

Creating Scripts for Post Process Application in Process Flow

This section is applicable only for the users of Adepta Connect.

Using Process Flow in a Template

While creating a Process Flow, in the Process Designer, write the following script in the Service exception field under the OnException Scripts tab.

import org.apache.commons.lang.exception.ExceptionUtils;

Throwable rootCause = ExceptionUtils.getRootCause(exception);
String exceptionMessage = null;
if(rootCause == null)
exceptionMessage = exception.getMessage();
else
exceptionMessage = rootCause.getMessage();

context.put("subprocess_code", "ERROR_IN_CHILD_FLOW");
context.put("subprocess_text", exceptionMessage);

Process Flow Calling Another Transaction

If the Process Flow is further calling a Transaction, you need to create a custom plugin using below JavaScript. After you have created a custom plugin, use it in the Process Flow.

JavaScript for Custom Plugin to set child context Param to call any Transaction:

import com.adeptia.connect2.runtime.RuntimeUtils;

RuntimeUtils.setChildContext(inputStream, context, service.getLogger(), "<<ACTION_NAME>>", "<<TransactionName>>", "<<PartnerName>>");

where,

ACTION_NAME is the name of the call or spawn.

TransactionName is the name of the Transaction.

PartnerName is the name of the Partner for which Transaction is created.

for example,

RuntimeUtils.setChildContext(inputStream, context, service.getLogger(), "Action_Name", "FTP_To_Email_Transaction", "Adeptia");

Ensure that you have provided the values in double quotes (").

If you are the owner of the Transaction then type null (without double quotes) as a value in the partner name, for example,

RuntimeUtils.setChildContext(inputStream, context, service.getLogger(), "<<ACTION_NAME>>", "<<FTP_To_Email_Transaction>>", null);

JavaScript for Custom Plugin to set child context Param for calling another process flow:

import com.adeptia.connect2.runtime.RuntimeUtils;

RuntimeUtils.setChildContext(inputStream, context, service.getLogger(), "<<ACTION_NAME>>", null);

JavaScript to check child flow is Aborted or not:

import com.adeptia.connect2.runtime.RuntimeUtils;

return RuntimeUtils.isChildFlowAborted(context, "<<resultCtxVarName>>");

where,

resultCtxVarName is the name of the context variable that contains the status of the sub-flow. The value can be Executed, Aborted, Queued, or Waiting.

JavaScript for Custom plugin to abort parent flow:

import com.adeptia.connect2.runtime.RuntimeUtils;

RuntimeUtils.abortParentFlow(context, "<<resultCtxVarName>>");