Skip to main content


 

Symptoms


_1: We were told a while ago that the WorklistCriteria calls are being deprecated and we were recommended to use the management API using SourceCode.Workflow.Management DLLs with the new filter WorklistCriteriaFilter. Currently we are in the process of doing that within our BPM Service….however we are running into an issue.

Currently we are performing an OpenWorklist (in order to open a worklist for a user) after we do an impersonate:

Example: Worklist worklist = wfConn.OpenWorklist(worklistCriteria)

However, now we are running into a problem when trying to code the new Management WorklistCriteriaFilter.

Example: SourceCode.Workflow.Management.WorklistItems managementWorklistItems = k2ManagementConn.GetWorklistItems(wcf)

We do not see an option that will allow us to open a worklist (and thus change the Status of the Worklist to Open) once we get the worklist items.

Is there any way to do this? Can it not be done at this time? Any advice would be greatly appreciated.

_2: Customer is getting the following error when trying to use WorkflowManagementServer.GetWorklistItems method
System.Exception was unhandled
HResult=-2146233088
Message=Method could not be resolved!
Source=SourceCode.HostServerLib
StackTrace:
at SourceCode.Workflow.Management.WorkflowManagementServer.GetWorklistItems(String whereClause, String orderByClause, String paramList, Dictionary`2 ParamDic, Int32 PageIndex, Int32 Maxpage)
at SourceCode.Workflow.Management.WorkflowManagementServer.GetWorklistItems(WorklistCriteriaFilter filter)
at Test_Anything.Program.Main(Stringi] args) in c:Humana Workflow ITranchesK2POCTest Anything4.6.6SrcProgram.cs:line 43
at System.AppDomain._nExecuteAssembly(RuntimeAssembly assembly, Stringi] args)
at Microsoft.VisualStudio.HostingProcess.HostProc.RunUsersAssembly()
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Threading.ThreadHelper.ThreadStart()
InnerException:
 

Diagnoses


_1: I believe you can use the SourceCode.Workflow.Management – WorklistItem Class to get the Serial number. The Serial number is a combination of “Process Instance ID”_”Activity Instance Destination ID”.

With SourceCode.Workflow.Management – WorklistItem Class, you have access to these values.

Then you should be able to use the Workflow Client API to open them correct?
http://help.k2.com/onlinehelp/k2blackpearl/DevRef/4.6.7/Working_with_a_Process2.html
http://help.k2.com/onlinehelp/k2blackpearl/DevRef/4.6.7/Working_with_Global_Worklist.html

_2: During the live meeting, we noticed that the code executed successfully when connecting the project to QA environment. Customer did a compare the dlls between Dev and QA and found some discrepancies.
 

Resolution

_1: Customer will use the above suggestion.

_2: After customer made sure that the dlls from in Dev are matching QA, he was able to test that the code executes successfully in Dev.


 




 
Be the first to reply!

Reply