You are viewing limited content. For full access, please sign in.

Question

Question

rich text not saving data for next user task

asked on September 20, 2021

I have a form that has a rich text field with the variable name Feedback_Provided. This field is set to hide when the radio button variable Type_of_Coaching has Negative selected because the Feedback_Provided variable is only used in positive feedback. Other rich text fields are part of the same field rule as Feedback_Provided and are set to show when Type_of_Coaching is Negative. The process starts with the supervisor filling out all information about either positive or negative coaching. Once submitted the initiator is then assigned the same form in a user task to deliver the coaching and collect signatures. 

When we converted the form to Version 11, the Feedback_Provided variable shows empty in the delivery user task when the form is filled out as positive coaching even though the variable is filled out during the start event. When the form is filled out as negative coaching, the other rich text fields part of the same field rule as Feedback_Provided do not present the problem. 

To test, I switched the field rule to show Feedback_Provided when Type_of_Coaching is Positive and hide the other rich text fields. When I did this, Feedback Provided no longer had the problem during positive coaching. However, the other fields no longer passed the data to the delivery task when a negative caching was completed. I also tried creating a second form with the fields and rules and assigned it to the delivery task in case the problem was that we were using the same form for the start event and delivery task, but the issue continued then as well.

Has anyone run into a similar problem with rich text fields, and if so, how did you make sure the variable did not show empty in the next user task when it was filled out in the previous task and part of a field rule? 

0 0

Answer

SELECTED ANSWER
replied on September 21, 2021

Hi Carlos,

This is identified as a bug for new form designer in Forms 11. The bug has been fixed on cloud, and will be fixed in next on-premises Forms release.

With your case, a temporary workaround for this bug could be to configure separate field rules for rich text fields of positive and negative choice, and make sure each field rule work as expected.

0 0
replied on September 22, 2021

Hi Ziyan,

Thanks, the workaround worked and I will be waiting for the next on-premises Forms release for the fix. 

0 0

Replies

You are not allowed to reply in this post.
You are not allowed to follow up in this post.

Sign in to reply to this post.