Appian Community
Site
Search
Sign In/Register
Site
Search
User
DISCUSS
LEARN
SUCCESS
SUPPORT
Documentation
AppMarket
More
Cancel
I'm looking for ...
State
Not Answered
Replies
9 replies
Subscribers
7 subscribers
Views
3321 views
Users
0 members are here
Share
More
Cancel
Related Discussions
Home
»
Discussions
»
User Interface
"Working" preventing an end user from typing on a form?
Jason Ruvinsky
Certified Senior Developer
over 8 years ago
We have an end user who is complaining that the "Working" message keeps coming up while typing in a form field, and that she "cannot continue until Working goes away on each field".
In my own testing, this form never shows the "Working" message - there is nothing supposed to be happening while typing into the fields. Why might this be occurring, and how could we resolve this for the user? Does anyone have advice on troubleshooting this?
OriginalPostID-240187
Discussion posts and replies are publicly visible
0
ChristineH
Certified Lead Developer
over 8 years ago
te only time I have seen that is when there is validation on the field. Is that the case here?
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
reginaldm377
over 8 years ago
Are any of your rules in the with() section of your form constantly running some logic that cross with your fields? I would 1st suggest checking the form with performance view & see if any variables, parameters, rules, etc. are degrading the performance of your form.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
Jason Ruvinsky
Certified Senior Developer
over 8 years ago
No, neither case applies. There is no with() and no validations, and there are no performance issues that we can see on our end with this form. When I attempt to reproduce locally, the "Working" message doesn't even appear when working on any fields on this form. I have logged a support case to further troubleshoot.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
danny.leo
Certified Associate Developer
over 8 years ago
sounds network specific
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
rawich
over 8 years ago
Do you have any text fields with refreshAfter set to "KEYPRESS"? That would explain the "Working" message after each keystroke, but there is definite another issue involved, if the message and the pause disrupted the user.
You should also try to isolate the issue by asking the particular user to login from a different computer and try to do the same task. So you'll know for sure if the problem is with the user account/role or the machine, or neither.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
ajaved
A Score Level 1
over 8 years ago
@jasonr411 random thought, might not apply.
Does the user have any browser extension/add-on/plugin installed that sends a request after each field e.g. I have seen AJAX requests being made by add-ons such as Grammarly and others, because they need to validate with their servers each time.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
Jason Ruvinsky
Certified Senior Developer
over 8 years ago
We also think it's likely network specific. We do have the textfields set with refreshAfter: "KEYPRESS" - however that shouldn't cause it to be this slow for this one user, and I'm not sure how it would disrupt the user either. (Although the saveInto does update a value within an array, so it's not the simplest case - but it's never caused an issue before now with any other users).
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
benjamins
over 8 years ago
Problem with these sorts of bugs is that it can be a lot of things....
What browser are they using? The Javascript engine on the browser maybe old. Plugins could be causing issues.
Their computer could also be old which maybe causing issues.
Then there is network. What fields exactly is causing the issues and what are you trying to do in the background?
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
Jason Ruvinsky
Certified Senior Developer
over 8 years ago
It was a browser/client issue. It has not recurred today for the user, so it was likely fixed by a restart.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel