nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

addPackage method error in process builder

Imran_Yusubov

Hello Experts,

I am developing a custom activity which will clear workflow packages. Here is what I am doing.

1. Loop through the packages and first remove them using,IDfWorkitems,

void removePackage(String packageName) throws DfException

method.

2. Then I add the package back to the workitem and save it.

IDfId addPackage(String packageName, String packageType, IDfList componentIds) throws DfException

The JavaDocs say if you don't want to attach any components use null. (A package may have one or more components or no components. To add a package with no components, specify componentIds as null.)

So I use the method in this way,

workItem.addPackage(packageName,packageType, null);

The problem is that this metod works very fine in method server but while debagging a process in process builder this method fails.The error shown below occurs in process builder.Please guide me to find the issue.

=========================================================================

DfException:: THREAD: pool-2-thread-2; MSG: ; ERRORCODE: ff; NEXT: null

at com.documentum.bpm.engine.adapters.WorkitemExAdapter.addPackage(WorkitemExAdapter.java:300)

at com.documentum.bpm.engine.adapters.WorkitemExAdapter.addPackage(WorkitemExAdapter.java:277)

at com.sinam.bpm.methods.RemoveWorkflowPackage.doTask(RemoveWorkflowPackage.java:42)

at com.documentum.bpm.rtutil.WorkflowMethod.execute(WorkflowMethod.java:214)

at com.documentum.bpm.rtutil.AbstractWorkflowMethod.executeMethod(AbstractWorkflowMethod.java:27)

at com.documentum.bpm.rtutil.GenericWorkflowMethod.execute(GenericWorkflowMethod.java:124)

at com.documentum.bpm.rtutil.GenericWorkflowMethod.execute(GenericWorkflowMethod.java:84)

at com.documentum.bpm.engine.utils.InvokeWfMethodService.execute(InvokeWfMethodService.java:96)

at com.documentum.bpm.engine.model.activity.WorkflowMethodActivityTaskHandler.executeWorkitem(WorkflowMethodActivityTaskHandler.java:43)

at com.documentum.bpm.engine.runtime.AutomaticWorkitemHandler.executeService(AutomaticWorkitemHandler.java:256)

at com.documentum.bpm.engine.runtime.AutomaticWorkitemHandler.execute(AutomaticWorkitemHandler.java:119)

at com.documentum.bpm.engine.runtime.AutomaticWorkitemHandler.run(AutomaticWorkitemHandler.java:63)

at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)

at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)

at java.lang.Thread.run(Unknown Source)

Caused by: java.lang.NullPointerException

at com.documentum.bpm.engine.adapters.WorkitemExAdapter.addPackage(WorkitemExAdapter.java:288)

... 14 more

Thanks in advance

Find more posts tagged with

Note:

If there are Accepted Answers, those will be shown by default. You can switch to 'All Replies' by selecting the tab below.

Button

Accepted answers

CláudioGil

The Process Builder uses as different execution engine with slightly different implementions of the workflow classes. It's a bummer but this case is simple to workaround.

You may already have changed it but passing null or new DfList(IDfList.DF_ID), as the component ids, is equivalent although the documentation only mentions the null for simplicity. Process Builder will accept the empty list and the standard engine will also create an empty package.

All comments

Julien.Fontaine

Hi,

I know that some methods cannot works in process builder debug mode !

Perhaps you have not got the jar file ?

Imran_Yusubov

Hello,

Thank you very much for the reply.

I have created a standard module which extends WorkflowMethod and implements IDfModule and deployed it into the docbase. Process builder have downloaded it into it's local cache.The rest of the methods that I use are standard DFC methods so there should not be this issue.Can't understand why it is causing to this issue.

Julien.Fontaine

Do you already read the Procees Builder development Guide to check that your module can run in debug mode ?

Julien.Fontaine

Does it works now ?

DCTM_Guru

"The problem is that this metod works very fine in method server but while debagging a process in process builder this method fails."

- Which method class are you implementing? I'm pretty sure one of them does not work with PB - I just dont remember which one.

Imran_Yusubov

Hello,

No it is still not working in process builder.

Johnny, here is my complete source code. please see what I can add into it to get it work.

package com.sinam.bpm.methods;import java.io.PrintWriter;import com.documentum.bpm.rtutil.WorkflowMethod;import com.documentum.fc.client.IDfCollection;import com.documentum.fc.client.IDfModule;import com.documentum.fc.client.IDfPackage;import com.documentum.fc.client.IDfSession;import com.documentum.fc.client.IDfWorkitem;import com.documentum.fc.common.DfId;import com.documentum.fc.common.IDfList;import com.documentum.fc.common.IDfProperties;public class ClearWorkflowPackages extends WorkflowMethod implements IDfModule  { public final String REQUEST_PACKAGES="PACKAGE_NAMES"; @Override protected int doTask(IDfWorkitem workitem, IDfProperties activityParameters, PrintWriter printWriter) throws Exception { IDfSession session = workitem.getSession(); IDfList requestPackage =activityParameters.getList(REQUEST_PACKAGES); IDfCollection wPackages=workitem.getAllPackages(null); while(wPackages.next()){ String pckgName=wPackages.getString("r_package_name"); for(int i=0;i<requestPackage.getCount();i++){ if(requestPackage.get(i).equals(pckgName)){ IDfPackage pck=(IDfPackage) session.getObject(new DfId(wPackages.getString("r_object_id"))); String pckName=pck.getPackageName(); String pckType=pck.getPackageType(); //Remove the package and save the workitem workitem.removePackage(pckName); //Add the package again and save the workitem again workitem.addPackage(pckName, pckType, null); workitem.save(); }  } } return 0; }}

CláudioGil

The Process Builder uses as different execution engine with slightly different implementions of the workflow classes. It's a bummer but this case is simple to workaround.

Imran_Yusubov

I though about that but did not try, I will update it and let you know about the results.

Imran_Yusubov

Adding

new DfList() works.

//Add the package again and save the workitem again workitem.addPackage(pckName, pckType, new DfList());