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; } } }

WorkRoute for Worksite MP

Are there any support forums for the WorkRoute add on for Worksite MP 4.1? I require some assistance writing java helper classes to extend the functionallity of the product.

Thanks,

Chris

Find more posts tagged with

Comments

At present this is THE forum for all WSMP questions. The forum is checked daily, and we route questions to knowledgeable engineers as needed.

hth,

lissa

Alright then.

Basically, I am trying to programmatically create and add an attachment to a workflow using a java helper class. Once we start a workflow and gather some information from the user via forms, we use one of Interwovens WorkRoute helper class examples, FormToText, to create a file in the current workspace. This works great. Where I am having difficulties is when I try to add the attachment to the workflow process instance.

Below is the relevant code and exceptions I am getting.

//Get the Process ID
long processId = getProcessId();
ProcessInstance process;
process = getProcessInstance(processId);
System.out.println("^^^^^AttachIT- Getting Process ID: " + process);

//Try to add an attachment
try{
System.out.println("***^^^TRYING to setAttachments^^^***:");
process.startEdit();
process.addAttachment("string", "string");
process.commitEdit();
System.out.println("***^^^Successfully Added Attachments^^^***: ");
} catch(Exception e){
System.out.println("***^^^ERROR setAttachments^^^***: " + e);
}

This produces a couple of exceptions.

1. on process.startEdit();
The exception is:
ProcessInstanceProxy.editForEnactment: WorkRoute could not edit the process instance. (65711)

2. on process.addAttachment("string", "string");
The exception is:
***^^^ERROR setAttachments^^^***: Process instance can not be locked by '(!)' (session=(!)). The process was locked by user '(!)' (session=(!)) at (!) and it is still locked. (Process instance can not be locked by 'wfadmin' (session=200). The process was locked by user 'init' (session=199) at Fri Mar 04 10:18:15 EST 2005 and it is still locked.)

Any help would be greatly appreciated, please let me know if you need any more information.

Regards,

Chris

It looks like you are using raw fujitsu apis to access your workflow engine outside the context of the WOM API and some failure after the startEdit() has caused the record to stay locked. Make sure you use cancelEdit() if exceptions occur, that may be why it is still locked.

You should also switch to using the WOM API, all those fujitsu nuances are wrapped so you will not have to deal with them. Take a look at com.imanage.cms.api.workteam.WorkflowProcess ant the other related WOM API.

pruebas.rptdesign

I've also tried using the WorkflowProcess interface in the WOM API with no luck. Any chance that you could provide a working sample of the addAttachment() method?

What is happening when you addAttachment() with the WOM API to a WorkflowProcess instance?

I always end up with a nullpointer error.

Ok, but that's NOT much to go on...

Have you done all the initial setup of creating a WorkflowTemplate (process definition) in the template designer and getting it deployed to your intended Workspace?

How about you put up your test code and we can go from there?

Hi,

Yes, I've created the template and deployed it to a workspace.

To keep things simple, in the document titled, TemplateDesigner.pdf, page 113 ( or 121 using Adobe page count). It is suggested that attachments can be added via a prologue or epilogue script.

Quote....

WorkRoute MP Template Designer supports the standard ECMA JavaScript
commands. (See the ecma-262.pdf available at http://www.ecma.ch.) In addition,
it also supports following the commands for exchanging information with the
server:
• boolean addAttachment(String attachmentName, String attachmentMoniker)

......End Quote

I've added the following as a Prologue script in an activity node.

addAttachment("PDF1","!V3!WSMP1!C!D$202!");

Where PDF1 is the actual name of a document stored in the same workspace as the workflow and !V3!WSMP1!C!D$202!, I believe, is the document moniker.

The exact error logged is:

ERR:Tue Mar 08 14:11:54 EST 2005: TID=3087989: JSExtensionInterface : addAttachment: JavaScript operation 'addAttachment(...)' encountered an error. (WorkRoute could not add an attachment. (java.lang.NullPointerException))

Thanks in advance for your help

Regards,

Chris

Ah, from JavaScript....

I'll have to refer to this to another chap that has used that before, I'm just an API guy.

Let me forward this on and hopefully he can get back to you soon.

I'll take whatever help I can get. If we can make this work via java script or a java helper, either works for me. Below is the code from a helper class I'm working on.....

import com.imanage.cms.api.workteam.WorkflowAttachment;
import com.imanage.cms.api.workteam.WorkflowProcess;
import com.imanage.cms.api.workteam.Workspace;
import com.imanage.cms.t2.workflow.exceptions.WorkflowException;
import com.imanage.cms.t2.workflow.engine.javascripthelper.JavaScriptHelperBase;


/**
 *
 * @author Chris Bland
 */
public class addAttachmentToProcess extends JavaScriptHelperBase {

    /** Creates a new instance of addAttachmentToProcess */
    protected Object doExecute(Object input) throws WorkflowException {
        String result = "";
        WorkflowProcess wp = null;     
        long pID = getProcessId();
        Workspace workspace = getWorkspace();


        try
        {
        wp = workspace.getWorkflowProcessById(pID);
        wp.addAttachment("PDF1","!V3!WSMP1!C!D$202!");
        result = "Attachment Added";
        }
        catch(Exception e)
        {
        System.out.println("Didn't work!! wah,wah, waaaaahh:  " + e);
        result = "Not added";
        }
        return(result);
    }

}

I call the helper class from a prologue script in an activity node. The java script is below:

[script]

var out = java.lang.System.out;
var AddAttach = new Packages.com.imanage.workflow.engine.TrackIT.addAttachmentToProcess();
var processId = getProcessId();
out.println('Calling addAttachmentToProcess...');
var results = AddAttach.execute(processId);
out.println("Result is: " + results);

[/script]

The exception is thrown at:

wp.addAttachment("PDF1","!V3!WSMP1!C!D$202!");

The exception is:

Didn't work!! wah,wah, waaaaahh: com.imanage.cms.exceptions.composite.CmsCompositeApiException: Process instance can not be locked by '(!)' (session=(!)). The process was locked by user '(!)' (session=(!)) at (!) and it is still locked. (Process instance can not be locked by 'init' (session=242). The process was locked by user '(!)' (session=(!)) at Wed Dec 31 18:59:59 EST 1969 and it is still locked.)

Chris,

I'm truly sorry for my late reply. Things have been hectic here due to release schedules. Alas, there is no way you may edit the workflow process from within a Java helper class. Regardless of wether you use Fujitsu API calls or WOM API calls. The Java helper class can be used to make other WOM calls, such as to create the document. But to actually assign it to the process requires modifying the process. This can only be done in the JavaScript. The call you've listed should have worked. I'm really not sure why it hasn't. (There was a bug with the addAttachment call in WorkSite 3.x, but I believe you're using 4.1, right?)

Can you please attempt to use the JavaScript call again and look into as many server-side WorkRoute related log files as you can for additional information? Also, what script (activity prologue, epilogue, process commit?) are you using to invoke the JavaScript addAttachment call?

Thanks,
Nick

Production Enviroment is Worksite MP 4.1
Development Enviroment is Worksite MP 4.1 SP1
JavaScript in a Delay Node Epilogue Script:

var out = java.lang.System.out;
out.println('****************************');
out.println('****************************');
out.println('****************************');
out.println('***Calling Add Attachment***');
out.println('****Delay Node Epilogue****');
addAttachment("PDF1","!V3!WSMP1!C!D$202!");
out.println('****************************');
out.println('****************************');
out.println('****************************');

imworkflow.0.stdout.log:

****************************
****************************
****************************
***Calling Add Attachment***
****Delay Node Epilogue ****
ERR:Mon Mar 14 11:33:10 EST 2005: TID=17014438: TWFScriptExtensionImpl : addAttachment: WorkRoute could not add an attachment. (java.lang.NullPointerException)
ERR:Mon Mar 14 11:33:10 EST 2005: TID=28039881: JSExtensionInterface : addAttachment: JavaScript operation 'addAttachment(...)' encountered an error. (WorkRoute could not add an attachment. (java.lang.NullPointerException))
ERR:Mon Mar 14 11:33:10 EST 2005: TID=28039881: ScriptInterpreterImpl : JavaScript operation 'addAttachment(...)' encountered an error. (WorkRoute could not add an attachment. (java.lang.NullPointerException))
ERR:Mon Mar 14 11:33:10 EST 2005: TID=28039881: ScriptInterpreterImpl : evaluate: WorkRoute could not evaluate the script. (org.mozilla.javascript.JavaScriptException: JavaScript operation 'addAttachment(...)' encountered an error. (WorkRoute could not add an attachment. (java.lang.NullPointerException)))
ERR:Mon Mar 14 11:33:10 EST 2005: TID=28039881: ActivityType : evaluateJS: WorkRoute could not evaluate the script. (evaluateJS(ScriptType=EpilogueScript, piId=77348, actId=77350)) (evaluateJS(Script=var out = java.lang.System.out;

cms.workflow.sw002dmdev.log
Nothing here but logon events

Mon Mar 14 11:33:09.858: INFO [RMI TCP Connection(839)-10.33.1.172] Login: init

cmstrans.workflow.swoo2dmdev.log
The last even logged here is:

Fri Mar 11 17:05:57.760: INFO [execute] ******************************* Initializing *******************************

cmsmon.workflow.sw002dmdev.log

No events logged.

<bump>

Folks,

The addAttachment() JavaScript method does NOT work in WSMP. Chris' observations were quite correct on that. Furthermore, the common use of helper classes is such that they are synchronous or "blocking" calls which, as I mentioned earlier, do not permit the modification of workflow objects.

The work around to this problems is to use the same Java helper class but to invoke it from the JavaScript event hook using the "asynchronousExecute" rather than "execute" method. Taking this approach allows you to modify attachments, UDAs, etc. However, it's a non-blocking call. As such, you might require a little delay mechanism if you want the modifications made by your helper class to be immediately viewable. (Using a boolean UDA and waiting until its value changes might prove helpful here.)

At any rate, the asynchronousExecute() invocation of Chris' helper class did the trick. We'll hopefully get that addAttachment() JavaScript method working soon.

Thanks,
Nick

Hi,

Can anyone got any workaround on this? I am facing the same problem. I need to attach the file from the javascript only.

I am using WSMP 4.1 SP1.

Please help me out.

Thanks
Tushar

Dada,

Please read my last post to see the work-around. You *cannot* use the JavaScript addAttachment method presently. The work-around is, as I previously described, to use a Java helper class to add the attachment and to invoke that helper class via the asynchronousExecute() method. (For an example of a helper class that would do this, you might want to refer to Chris' earlier post in this same thread.)

Thanks,
Nick