Jump to content

Invocation Error during Change Management BPM


JO_7001

Recommended Posts

We have recently started using the Change BPM with a few tweaks of our own. I have been testing the various processes and assigned tasks and I have found that when we are logging a Standard Change at the point that the assigned task is to "Perform the Change" I receive the attached Invocation Error

image.png.38dd17103700706ab3c3f52cf74b4470.png

 

I have dug around in the logs and I have found the following:

2018-11-30 12:03:26Z [INFO]:[PROFILE]:[8496] data:queryExec() Method call results: success (244293632 B, 8 ms, -32 kB, 0 ms, 0 kB)
2018-11-30 12:03:26Z [INFO]:

:[2920] SELECT count(*) as cnt FROM h_sys_accounts WHERE h_user_id = 'Username' AND h_class = 1 [2681 us]
2018-11-30 12:03:26Z [WARNING]:[SYSTEM]:[2920] XMLMC Request Failed: The specified user 'Username' does not exist
2018-11-30 12:03:26Z [ERROR]:[PROFILE]:[2920] task:taskCreate2() Method call results: failure (244301824 B, 6 ms, -12 kB, 0 ms, 0 kB)
2018-11-30 12:03:26Z [ERROR]:[COMMS]:[6280] The specified user 'Username' does not exist
2018-11-30 12:03:26Z [INFO]:[SQL]:[6280] UPDATE h_bpm_instance SET h_state = ?, h_current_node = ?, h_current_state = ? WHERE h_id = ?
2018-11-30 12:03:26Z [INFO]:[GENERAL]:[7420] Invocations (95cf7f45-f89f-4948-bc58-b2d0b3ace531): bpm/processGetState

(I have removed Names from the above and replaced with 'Username')

I have looked within Database Direct for h_sys_accounts and the accounts that are listed are none of the IT Department but random users from around the business. I have checked the BPM Process for this task and the Owner of the task is System Administrator and the task is Assigned to the Variable ["ownerId"]

 

Is there anything that you are aware of that can resolve the above?

Thanks

 

Link to comment
Share on other sites

7 minutes ago, JO_7001 said:

I have checked the BPM Process for this task and the Owner of the task is System Administrator and the task is Assigned to the Variable ["ownerId"]

Are you sure the task is configured to assign to ["ownerId"]? Because looking through the logs it looks it is configured to assign to ["owner"] which is incorrect...

Link to comment
Share on other sites

@JO_7001 - thanks for the API key. As suspected the error occurs because the process has a human task configured to assign the task to ["owner"]. I can see you posted a screenshot where the task is assigned to   ["ownerId"] so I think there is a misunderstanding of where the error actually occurs. The error did not occur when "Perform the Change" task was created (this one is configured correctly) but on the next task, "Update Documentation". This task is configured incorrectly to assign the task to  ["owner"] instead of  ["ownerId"].

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
×
×
  • Create New...