Well, i can guess this is a catch all error code, but any idea why?
Exception: [DM_DFC_E_UNDEFINED]error: "Undefined error." DfException:: THREAD: http-0.0.0.0-9080-2; MSG: [DM_DFC_E_UNDEFINED]error: "Undefined error."; ERRORCODE: ff; NEXT: null DfException:: THREAD: http-0.0.0.0-9080-2; MSG: [DM_DFC_E_UNDEFINED]error: "Undefined error."; ERRORCODE: ff; NEXT: null
at com.documentum.fc.client.DfWorkitem.getNextActivityNames(DfWorkitem.java:55)
at com.documentum.bpm.DfWorkitemEx___PROXY.getNextActivityNames(DfWorkitemEx___PROXY.java)
at com.xx.yy.UtilMethod.getNextActivity(UtilMethod.java:186)
at com.xx.yy.CustomWorkflowMethod.setNextActivity(CustomWorkflowMethod.java:120)
The strange thing is the worklfow got to the queue it was supposed to, with the right priority ( the code before this boosts the priority of the workitem if told to by our rules... )
should we be worried about this?
This is in DFC 6.7.1040.0089