Sajith (Customer) asked a question.
We are currently on 7.5.2 P7 and since 7.2.1 we have been creating change requests to add/remove users to groups from another change request using the RESTWebserviceNode.
Recently as part of a change we wanted to remove the redundant job level parameters from the createChangeRequest's parameter section as they are no longer required in the new change request and after that we are noticing that the change request creation is failing with the below error.
Logs from Workpoint log.
2023-10-25 16:16:43,564 [Worker_actionq#Normal#jdbc/avdb_13] ERROR com.workpoint.server.script.ScriptEngine - A script error has occurred. Error occurred in Statement #1 in Script ID 3:WPDS, Script Name = 'Node - Available Asynchronous', Script type = 'Action'. Job ID = 594570:WPDS, Process Ref = '2175', Node Name = 'Create request', WorkItem = 6951480:WPDS:1
com.workpoint.common.exception.ScriptEngineException: InvocationTargetException caught when executing Java class. Command='#Wed Oct 14 09:07:49 EDT 2009
Parameter6=SymbolTable
Parameter5=ThisWorkItemData
JavaClass=com.aveksa.server.workflow.scripts.nodes.WorkflowNodeHandler
Parameter4=ThisActivityInstData
Method=nodeAvailableAsynchronous
Parameter3=ThisJobNodeData
Parameter2=ThisJobData
Parameter1=ClientContext
ParameterType6=OpTypeNotSpecified
UseInstanceObjectName=
ParameterType5=OpTypeNotSpecified
ParameterType4=OpTypeNotSpecified
ParameterType3=OpTypeNotSpecified
ParameterType2=OpTypeNotSpecified
Version=1
ParameterType1=OpTypeNotSpecified
UseInstance=false
MethodIsStatic=true
<New=Statement>
'; nested exception is:
java.lang.NumberFormatException: For input string: ""
at com.workpoint.server.script.StatementEngineJava.execute(Unknown Source) ~[wpServer.jar:?]
at com.workpoint.server.script.ScriptEngine.A(Unknown Source) ~[wpServer.jar:?]
at com.workpoint.server.script.ScriptEngine.execute(Unknown Source) ~[wpServer.jar:?]
at com.workpoint.server.monitor.ActionMonitorHelper.A(Unknown Source) ~[wpServer.jar:?]
at com.workpoint.server.monitor.ActionMonitorHelper.execute(Unknown Source) ~[wpServer.jar:?]
at com.workpoint.services.impl.ScriptExecAsyncServiceImpl.executeScriptMonitor(Unknown Source) ~[wpServer.jar:?]
at com.workpoint.client.Monitor.executeScriptMonitor(Unknown Source) ~[wpClient.jar:?]
at com.workpoint.queue.work.ActionQWorker.A(Unknown Source) ~[wpQMonitorFull.jar:?]
at com.workpoint.queue.work.ActionQWorker.run(Unknown Source) ~[wpQMonitorFull.jar:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) ~[?:1.8.0_362]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) ~[?:1.8.0_362]
at java.lang.Thread.run(Thread.java:750) ~[?:1.8.0_362]
Even after adding back the removed parameters does not resolve this issue, i will have to import the previous working version of the workflow.
Has anyone faced similar issue?
I have some bad news. Based specifically on the symptom you reported that this is resolved by importing the connector and you cannot recreate with the editor makes me think this is a data migration issue with a legacy workflow definition.
The best solution is likely to start over with the design of a new workflow or new node in the workflow. I expect that if you created the workflow from scratch in the current version it would not exhibit this odd behavior. You could start with just deleting the node (do a save and open in a new editor session after this action) and creating the node in the 7.5.2 Workpoint editor. If this does not work then try recreating the entire workflow in 7.5.2.
I know recreating the entire workflow to solve this issue is onerous, but I think that has the best chance of success. Attempting to repair the existing legacy workflow sometimes just does not work.
@Staines_ian (RSA Security) - Thanks for the details. I had tried to delete the node, saved it but recreated the node within the same session and it did not work.
Will try recreating the node in a new editor session and see if it works.
Unfortunately, recreating the whole workflow does not seem to feasible solution for us at the moment.