Jump to content

BPM issue following v2.36.3 - assignTeamOwnerCapacity


Martyn Houghton
 Share

Recommended Posts

Our BPM process is failing since applicaiton of Service Manager v2.36.3, referencing an issue with assignTeamOwnerCapacity when incidents are logged via the selfservice.

assignTask.JPG

Initially I thought this was down to a change in the behavoiur of the Assign to Request Creator node, but I have bypassed this and still get the issue.

Cheers

Martyn 

Link to comment
Share on other sites

@ArmandoDM

Thanks. Error thrown is logs is below.

2016-11-08 08:56:07Z [DEBUG]:[SYSTEM]:[14016] XMLMC Request Failed: queryParams validation error: The value 'Requests_bpm_assignTeamOwnerCapacity_TeamDetails' for element <queryColumns> is not an allowable value at location '/methodCall/params/queryOptions/queryColumns'
2016-11-08 08:56:07Z [INFO]:[SYSTEM]:[14016] Output message XML Schema validation ok
2016-11-08 08:56:07Z [ERROR]:[PROFILE]:[14016] data:queryExec() Operation Invocation results: failure (209305600 B, 2 ms, -4 kB, 0 ms, 0 kB)
2016-11-08 08:56:07Z [ERROR]:[COMMS]:[14016] Operation[data:queryExec] queryParams validation error: The value 'Requests_bpm_assignTeamOwnerCapacity_TeamDetails' for element <queryColumns> is not an allowable value at location '/methodCall/params/queryOptions/queryColumns'
2016-11-08 08:56:07Z [ERROR]:[COMMS]:[14016] Operation[data:queryExec] queryParams validation error: The value 'Requests_bpm_assignTeamOwnerCapacity_TeamDetails' for element <queryColumns> is not an allowable value at location '/methodCall/params/queryOptions/queryColumns'
2016-11-08 08:56:07Z [ERROR]:[SCRIPT]:[14016] nodeName: Data: queryExec: TeamDetails; nodeId: a303b282-9989-470f-aa0f-f9812afb8923; At 569/1: "Uncaught EspMethodCall:invoke: Operation[data:queryExec] queryParams validation error: The value 'Requests_bpm_assignTeamOwnerCapacity_TeamDetails' for element <queryColumns> is not an allowable value at location '/methodCall/params/queryOptions/queryColumns'"
    throw(e);
_fc_node_exec_a303b282_9989_470f_aa0f_f9812afb8923
2016-11-08 08:56:07Z [DEBUG]:[PROFILE]:[14016] FlowCodeExec(com.hornbill.servicemanager/entities/Requests/fc_bpm/assignTeamOwnerCapacity)(3ms): Nd56579ca4-28dc-481f-b8e5-e8ff969a21cc=3ms,Nda303b282-9989-470f-aa0f-f9812afb8923=0ms
2016-11-08 08:56:07Z [DEBUG]:[SECURITY]:[5100] Session cache folder 'U2016110804836969' removed
2016-11-08 08:56:07Z [DEBUG]:[SECURITY]:[14016] Local cache item for session 'U2016110804836969' has been released
2016-11-08 08:56:07Z [DEBUG]:[SECURITY]:[5100] Local cache item for session 'U2016110804836969' has been released
2016-11-08 08:56:07Z [DEBUG]:[SYSTEM]:[14016] XMLMC Request Failed: FlowCode Exception (com.hornbill.servicemanager/entities/Requests/fc_bpm/assignTeamOwnerCapacity): nodeName: Data: queryExec: TeamDetails; nodeId: a303b282-9989-470f-aa0f-f9812afb8923; At 569/1: "Uncaught EspMethodCall:invoke: Operation[data:queryExec] queryParams validation error: The value 'Requests_bpm_assignTeamOwnerCapacity_TeamDetails' for element <queryColumns> is not an allowable value at location '/methodCall/params/queryOptions/queryColumns'"
    throw(e);

 

Cheers

Martyn

 

Link to comment
Share on other sites

Looks like there may be a general issue with a number of BPM nodes following the application of Service Manager v2.36.3. @Ralf Peters post below.

An now we are also getting further errors on now on existing workflows when attempting to out request on hold via the workflow.

updateonhold.JPG

Wondering if there is some dependencies on the platform that has not been met for the new SM release?

Cheers

Martyn

Link to comment
Share on other sites

Hi @Martyn Houghton,

Your initial issue on this post (regarding assignTeamOwnerCapacity) was evident in BPM nodes that assigned a request to the most available analyst. We've fixed this issue, and this will be released in Service Manager patch v2.36.4.

The other BPM issue is currently under investigation.

Kind regards,

Steve

Link to comment
Share on other sites

 

Suspect the Error being displayed is a red herring and the error relates to the below which is shown in the logs.

1375141 11:08:54 09/11/2016 error perf 10536 bpm:processResume() Operation Invocation results: failure (275853312 B, 61 ms, 0 kB, 0 ms, 0 kB)
1375134 11:08:54 09/11/2016 error scripts 10996 BPM operation: BPM related error: The business process instance cannot be resumed (Process:Execute: Resuming failed process)
1375133 11:08:54 09/11/2016 error scripts 10996 BPM flowcode resume: Process:Execute: Resuming failed process
1374287 11:08:50 09/11/2016 error comms 7196 Operation[apps/com.hornbill.servicemanager/Requests/bpmOperation:assignTeamOwnerCreator] FlowCode Exception (com.hornbill.servicemanager/entities/Requests/fc_bpm/assignTeamOwnerCreator): At 451/45: "Uncaught SyntaxError: Unexpected token ILLEGAL" if(global["query_exec_teamMembers_results"]["rowData] != undefined) global["lastException"] = typeof global["lastException"] == "undefined"? null: global["lastException"];

Cheers

Martyn

 

Link to comment
Share on other sites

Hi @Martyn Houghton,

This is another BPM defect, and wasn't directly related to (and not reported with) the issues from yesterday - although it does appear that it was present yesterday too. This issue is only affecting workflows that contain an Assignment > Assign to Requets Creator. 

I have fixed this issue, and it's currently being tested for release in another patch. I will let you know as soon as I have a timescale for deployment.

Kind regards,

Steve

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share

×
×
  • Create New...