Auto tab to next text box

AFAIK this is not possible with any components currently.

Can we do a work around to acheive this?

What is your exact requirement?

I have a editable grid with 10 columns with text boxes . Once user enter 5 characters, cursor should automatically move to next text box in a row. 

For what it's worth, a requirement is typically defined as "can the users cause the correct data to be entered into the system using the UI".  The rest is "design", and in Appian we need to constrain our design choices to what's provided by the UI (which has pros and cons). 

In your case, your users would be able to enter the necessary data into text boxes, a 5-character limit be hit, they can press "TAB" or mouse-click to the next box, and continue.  That means the requierment is fulfillable, even if it doesn't meet the design someone envisioned. 

One of our roles as Appian designers is being aware of what the UI components allow (and don't allow), and tempering expectations so that we don't run into such situations where an impossible design creeps into the "requirements".

I 100% agree with Mike. And there are multiple ways of adding this validation. You can use the new character limit param. Or you can use the validation parameter. To make the experience smoother, you can use the refreshOn as "KEY_PRESS" so that the error messages are displayed in real-time. 

One more classic way is to just not save any characters after the first 5. For this, you will have to use the left() function in your saveInto. 

I 100% agree with Mike. And there are multiple ways of adding this validation. You can use the new character limit param. Or you can use the validation parameter. To make the experience smoother, you can use the refreshOn as "KEY_PRESS" so that the error messages are displayed in real-time. 

One more classic way is to just not save any characters after the first 5. For this, you will have to use the left() function in your saveInto. 

Unknown said:

You can use the new character limit param.

yeah, this is what i was thinking too - this one is especially good for this use case because it works even without setting the refreshOn to "KEYPRESS", which can sometimes have performance implications.

Thanks Mike and  HArshit..

I communicated the same but still wanna confirm so raised a query here. 

Thanks for confirming