BPM issue following v2.36.3 - assignTeamOwnerCapacity

[Martyn Houghton]

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.

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 

[Martyn Houghton]

Following further investigaiton, this is affecting all our requests irrespective of their source.

Cheers

Martyn

[ArmandoDM]

Hi @Martyn Houghton,

we are looking into this issue and we'll get back to you.

Regards,

Armando

 

 

[Martyn Houghton]

@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

 

[ArmandoDM]

Thank you @Martyn Houghton

[Martyn Houghton]

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.

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

Cheers

Martyn

[Steve G]

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

[Martyn Houghton]

@steve_g

Steve

Thanks for the update. Do we have a timescale for v2.36.4, as this issue is having a major impact on out operation?

Cheers

Martyn

[Steve G]

Hi @Martyn Houghton,

We're looking to release 2.36.4 today. I'll let you know here as soon as this is in live.

Kind regards,

Steve

[nasimg]

Hi @steve_g - have to echo Martyn comments we are seeing BPM errors following the latest patch.

[Ralf Peters]

Hi @steve_g

will 2.36.4    fix this error as well  ?

 

 

 

[Martyn Houghton]

@steve_g

Just wondering if there is a revised timescale for 2.36.4?

Will the fix allow the broken workflows to be restarted, as got a growing number of them, as considering restricting my users access the system until this is resolved?

Cheers

Martyn

[Steve G]

Hi @Martyn Houghton,

2.36.4 is now live, please feel free to upgrade Service Manager on your Hornbill instance to pick up the fixes contained within this patch.

With regards to the restart of the BPM, I'll need to confirm this and get back to you.

Kind regards,

Steve

[Steve G]

Hi @Martyn Houghton,

The workflow restart functionality will retry the failed action within the workflow, so the assignment (which should be the last, and failed, action on the workflow) should be reattempted upon restart.

Kind regards,

Steve

[Martyn Houghton]

@steve_g

Have applied 2.36.4 but the broken requests from when 2.36.3 was applied are now failing with the error below when I attempt to restart them.

Also all our new requests now seem to be failing with this error.

Cheers

Martyn

[Martyn Houghton]

 

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

 

[Steve G]

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

[Martyn Houghton]

@steve_g

Thanks for the quick confirmation and will await an update on timescale.

Cheers

Martyn

[Steve G]

Good afternoon @Martyn Houghton,

We've just released patch 2.36.5 to live, which includes the fix for the assignTeamOwnerCreator issue. Please feel free to upgrade to this patch at your convenience to take advantage of this fix.

Kind regards,

Steve

[Martyn Houghton]

@steve_g

Have applied 2.36.4. Still get the error about the mailbox, but the workflow appear to be triggering activities. The HUD is still showing as Red, should this have refreshed as well?

Cheers

Martyn