Jump to content

Recommended Posts

Posted

Hiya, we have a self-service bpm that logs a job - the first thing that happens is it changes the customer, from the person who completed the form to a username  given in a custom field. 

  • This is completed by basic users
  • It worked up until sometime in the last 2 months
  • Everything but the customer change still functions

I've narrowed it down to find that the BPM only changes the customer (as desired) if the person completing the self service form was a full User and has the Incident management user role.

This seems like a bug to me? Can it be fixed/circumvented?

Many thanks

Posted

@SJEaton, @LawesD I logged this as an Incident on 09/08/23 with Premier Support. I suspect it was introduced by SYS_SYSTEM On 02-08-2023 06:32 (Release Date: (Build: 2910)

I gather it's in the SM release that was delayed last week; Customer Success said it should be this week so I'm hopeful.

  • Like 2
Posted

@Nanette Thanks for confirming. In that case I may be doing something wrong. Can someone cast their eye over the following please.

Intelligent Capture
image.png.0d142a799f19b27626aaeccca4997e5a.png
In the Workflow I have a 
image.png.5b8b6b15f73457d0e20a61fc07583368.png

followed by 
image.png.63c4540c355457a4cadf94116c83de53.png

I have also tried using the 

image.png.e54046fdcbac5a1d043ffc73f290549f.png

The Customer field is not updated in both tests. What am I missing (im sure it will be obvious)

Posted

Hi @Kelvin,

Can't be 100% sure about this, but at a glance from your screenshots, make sure that when you select the field from the Intelligent Capture, you use "Raw Value" instead of "Display Value".

I would expect "Customer_Name" to look like "Customer_Name_value".

Also, it would be better to use Co-worker (from variable) instead of Co-worker.

Thanks,

Samuel

  • Thanks 1
Posted

@samwoo Thank you it was the Raw Value, although we did previously test, maybe I forgot to publish. The Customer_Name was our chosen field name so was correct.

Really appreciate you looking at this :)

  • Like 1
Posted

Hello All, 

I've just tested removing the Incident management user role & reverted our guinea pig to basic user - the issue is still apparent. 

Is anyone else still having the issue?

Posted

After the release above that this issue was touted as fixed in we detected a recurrence and we raised another Premier Support ticket which remains with Support. It seems some instances were fixed but not all.

  • Thanks 1
  • 4 weeks later...
Posted

From a fellow user perspective it's upsetting our customers and messing with our workflow so I have asked Hornbill Customer Escalations to prioritise it. Hornbill noted on Tuesday 24th, "Our developers are aware that the fix in the recent Service Manager release does not appear to have been effective.  They are looking into a solution and once I know more I will of course pass on the next steps".

  • Thanks 1
  • 2 weeks later...
Posted

HB have found this is a defect and is logged as KE00179871 (Not changing customer when using the Change Customer node if Request is raised by a Basic USER).

I have not seen it appear on the Published Defects list so assume it's planned to be in a forthcoming release at some point.

@LawesD @Kelvin @SJEaton

  • Like 2

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...