Text fields in Interface intermittently saving user input

RE: Text fields in Interface intermittently saving user input

mohammedfarazu075443 — Sat, 17 May 2025 14:19:07 GMT

Hi Ashely, we are facing this exact same issue, but with version 24.4, did you happen to create any appian ticket for this, or did you get any resolution for this?

RE: Text fields in Interface intermittently saving user input

Stefan Helzle — Tue, 18 Mar 2025 07:01:52 GMT

In 15 years, I have never seen such behaviour. I suggest to open a support case with Appian.

RE: Text fields in Interface intermittently saving user input

Raghuraman S — Mon, 17 Mar 2025 20:20:17 GMT

To save the value of your textboxes when you are still typing, you can use "KEYPRESS" in refreshAfter parameter instead of "UNFOCUS".

RE: Text fields in Interface intermittently saving user input

Tanishk Khandelwal — Mon, 17 Mar 2025 06:26:44 GMT

Hi AshleyS

If you are using array in save Into please try with a!save(ri!text2,save!value)

RE: Text fields in Interface intermittently saving user input

AshleyS — Fri, 14 Mar 2025 14:41:32 GMT

Hi gayatria0439,

I did create two rule inputs ri!text1 and ri!text2. I rechecked and they are both correctly set to type text. This is a stand alone interface so it is not mapped to a process model's userInput task. I checked other interfaces encountering this problem, and their datatypes are set and are mapped properly to userInput tasks. This issue is also happening for local variables text3 and text4 as well as the rule inputs text1 and text2.

I tried my above code in the Appian Community addition which is running Appian Version 25.1. In this version I did see the code working as expected. Clicking or tabbing through each text field kept every user value as expected. However, in the version I'm using 24.2.392.0, it is not keeping user values when clicking or when tabbing through the text fields. Could this issue be due to a difference in versions?

Additionally, we're seeing a warning in the Dev Console (F12 in browser) stating: Component with cId: xyz tried to issue a reevaluation request while unfocused.

RE: Text fields in Interface intermittently saving user input

gayatria0439 — Fri, 14 Mar 2025 10:52:45 GMT

Hi AshleyS ,I have used your code to check the issue by implementing the flow, and it is working fine for me. You mentioned that you created ruleInput as a text datatype. Can you please recheck and confirm whether you have mapped it to the correct variables in the userInput task? Because there is no issue with your code.

RE: Text fields in Interface intermittently saving user input

Konduru Chaitanya — Fri, 14 Mar 2025 06:36:23 GMT

[quote userid="258835" url="~/discussions/f/user-interface/38698/text-fields-in-interface-intermittently-saving-user-input/146249"] I do expect the value to get updated when the user is typing or entering the value into the input field[/quote]

AFAIK, this will not happen.

[quote userid="258835" url="~/discussions/f/user-interface/38698/text-fields-in-interface-intermittently-saving-user-input/146249"]When clicking in the input field and into the next one it doesn't always save the user input[/quote]

In your current expression, it is not happening in this way. It works fine. Could you please share the rule input data type that you have configured.

RE: Text fields in Interface intermittently saving user input

AshleyS — Thu, 13 Mar 2025 21:48:20 GMT

Hi Konduru Chaitanya,

Yes, I do expect the value to get updated when the user is typing or entering the value into the input field. When clicking in the input field and into the next one it doesn't always save the user input. The same happens when clicking on an input and tabbing to the next.

For example. If I click on Text1 and enter in "one", click or tab into Text2 and enter "two", then click/tab into Text3. Text1 saves "one" into ri!text1 but Text2 doesn't save "two" into ri!text2.

RE: Text fields in Interface intermittently saving user input

Konduru Chaitanya — Thu, 13 Mar 2025 21:36:15 GMT

Hello AshleyS ,

Your code works fine and there seems to be no issue. From what I understand, you are expecting the value to get updated when the user is typing or entering the value into the input field. The value gets updated only when the user clicks outside the input field after entering the value or after a keypress if defined in the refreshAfter parameter of the input field.

If the above is not the concern, please elaborate your requirement in detail.