In a recent UX update to the Action panel, the “Action Name” field has been shrunk even smaller.
-
The devs must be working from very small screens, so it made sense for them to shrink it… but if you’ve got a wider screen, now it’s smaller and harder to see the names of descriptively named actions.
-
Well… why don’t you just name your actions simpler names?
- Because when you build enterprise level software using AppSheet, you end up with hundreds of actions - and having names that are easily distinguishable from one another is essential.
So this change of making the Action Name field smaller is a bit of a hinderance - IMHO.
- Personally, I feel it makes more sense for the size of these things to be based on a percentage of the screen size - not some arbitrary number.
Hopefully we can get the field size increased so its easier to see longer action names. Cheers!
Just throwing it out there… ¯_(ツ)_/¯
7 Likes
Totally agree with @MultiTech .
@lizlynch ,
May we request you to take it up with the concerned developers.
The action name is not used in any expression. Also a table can literally have many actions doing almost similar executions- navigation to various views, setting some status field with various statuses and so on. Then there are group actions , reference actions that need to be properly named to understand their relevance in the sequence.
Bottom line: As a result of the above reasons, the action names are almost invariably longer. As such the name setting needs to accommodate at least 70 characters. It used to accommodate larger names previously. Please do the needful to restore it.
Example: Please see the below tip where there are screenshots that show longer action names. Those names are on the side panel of the common action settings pane. The individual action name settings have been shortened that need to be rstored back.
Name actions with emojis and numbers to make them … - Google Cloud Community
4 Likes
@Suvrutt_Gurjar @MultiTech - Expect a fix for this early this week (if not today)! This was not intentional and the team is working to correct the issue. Apologies for the inconvenience! (This was raised and discussed in the comments of the May 13th release notes, but realize not everyone would have seen that thread.)
3 Likes
Thank you very much @lizlynch .for the update.