Service Manager - BPM Tasks - "Single line text field" showing as "Initializing... undefined"

[JamieMews]

BPM Tasks with the "Field Type" as "Single line text field" are showing as "Initializing... undefined" when completing the task. 

Screenshots provided. 

I have rename, readded and also created a new "Single line text field" but it still bugs

Screenshots show clear example

 

[nasimg]

See 

We found if the field was "Label" it had become blank....you can add it back and save the form, but has to be all of them before you can publish the form.

Nasim

[Mike Hillman]

We've noticed the same issue this morning with Labels - I thought it was linked to a bug we've already been experiencing on PCFs so I tagged it into the Thread I've already got open for that one

[Martyn Houghton]

We have the same issue and have logged it with Hornbill Support.

Our issue is with the outcome fields in the BPM rather than in Intelligent Capture forms, so affecting existing requests.

[Hornbill Staff DR]

Hi All,

 thanks for reporting the issue(s) and taking the time to supply the supporting screen shots. Hornbill Support are currently on the case and will provide update in due course.

Dan

[James Ainsworth]

A fix has been applied that prevents this issue from occurring on future tasks.  It may be the case that tasks where this issue has already occurred may still have an issue and will need to be addressed separately by Hornbill Support.  

[Jeremy]

On 4/29/2022 at 9:53 PM, James Ainsworth said:

A fix has been applied that prevents this issue from occurring on future tasks.  It may be the case that tasks where this issue has already occurred may still have an issue and will need to be addressed separately by Hornbill Support.  

@James Ainsworth So how do we fix these, we have 3 so far that have this specific issue?

[James Ainsworth]

Hi @Jeremy

I believe you need to get in touch with Hornbill Support to let them know that you have some of these broken tasks.  I'll see what more I can find out about their process for fixing these tasks.  

[Martyn Houghton]

@Jeremy @James Ainsworth

The fix applied to our instance stopped the issue occurring for newly created 'activities' but for the one which have been created whilst the bug was in place, we had to just proceed past the step in the work flow and deal with it manually.

Cheers

Martyn

[James Ainsworth]

We are also looking at providing an update that will automatically fix the activities that are stuck.  If this is possible, then it won't required any interaction with support.

[Jeremy]

@James Ainsworth if we copy the requests will that stop the issue?

[James Ainsworth]

9 hours ago, Jeremy said:

if we copy the requests will that stop the issue?

I'm afraid that I don't know.  Something possibly better answered by Hornbill Support.  

[Steve Giller]

On 5/4/2022 at 8:20 AM, Jeremy said:

if we copy the requests will that stop the issue?

The issue has already stopped, it is only Tasks that were created in a specific timeframe that have the problem.

If you copy the Requests they will have their own, newly created Tasks which will not be affected.
If you then cancel the original Requests, their Tasks will also cancel so you will have bypassed the issue.

[James Ainsworth]

An update is scheduled to go out that will look to automatically fix these tasks.  I believe that all you will need to do is view the broken activity and it will self-repair.