@andranik, I need to add a record using a conditional form in a modal. Unfortunately, the parent page is not updated when this happens, so it’s not as simple as closing the modal to see the new record after the form is submitted.
@artur, since modals do not always update the parent page, can we have the “Scroll to” action deployed on forms which would redirect back to a particular tab (i.e. parent page in this case).
Hey @Ben Thanks for getting back! I already raised this internally to have the scroll to action feature that redirects to a specific tab, our product team is already aware of your request.
Best,
@artur. Tabs need additional fixed labels or updated labels when configuring navigation. There is no way to identify them when attempting to set up ‘Scroll to section’ actions. For instance, when you customize the label for Tab1 to “Tasks”, the “Scroll to section” is labeled Page/#tab1, rather than Page/#Tasks, Page/#Tabs1(Tasks), or something that corresponds with the the customized label. This gets confusing when configuring navigation to multiple tabs with customized labels, especially when they are rearranged.
That’s right we discussed this internally but haven’t gotten into it yet… I will share here when I get a bit more clarity on a solution and timeline
@artur, any progress about this that I can work with? I am not confident that it will be implemented, especially with how long scrolling to blocks on different pages took.
@Ben the challenge is that those are a bit of corner case scenarios and usually scroll to block is becoming harder and harder with dynamic apps… we do our best attempts but the results are not good to release
@artur, then how can a user add an item using conditional logic, then navigate back to the list the item was added to? This should not be a “corner case scenario”, especially when there are conditional forms, and lists that can be located under tabs. If builders are not using features like lists, modals, and forms in a powerful and intuitive way like this, it’s not because they wouldn’t, it’s because they can’t.
Thanks for your comments, Ben. Tabs is still a relatively new block, and not all of the potential user flows are in place at this stage. With new blocks like this, it’s hard to account for every way a user will use them. In the beginning, we like to start by observing if users do indeed use them, and from there, we collect feedback like this so we can further enhance them once we see the demand from our users is there.
Workflows will be a HUGE help with this, as they’ll allow for multistep CRUD operations, along with other UI and navigational actions, to create enhanced user flows like this.
Hey JJ. That sounds like a rational way to prioritize new features, but tabs were released 6 months ago. For years, builders have submitted feedback to improve existing features, like this one, secure onboarding, account management, conditional forms, …, that were significantly delayed for shiny new ones like all of the recent data sources which won’t even be necessary now with Softr’s proposed “Workflows and Tables”.
When existing features are not improved (or integrated in this case), adoption will not improve, let alone exist.
Sure, thanks for bringing it up. As always, we appreciate your feedback and are listening.
@artur, can you confirm whether scrolling to a particular tab will occur? A simple “no” will be helpful so we can re-prioritize potential workflows if not.
@artur, what is the word on improving tab labeling?
RE: @artur, can you confirm whether scrolling to a particular tab will occur? A simple “no” will be helpful so we can re-prioritize potential workflows if not.
@Ben I’m checking this it should already be possible…
@artur, what is the word on improving tab labeling?
I think you have a full freedom to rename them no ? I will double check this
@Artur, referencing this again.
Hi @Ben
I chatted with the team about this. At the moment, you can scroll to a current tab, which I think you are already aware of?
However, like you said, in the scroll to action, you don’t see the name of the actual tab, but instead something like dashboard / tab 1. After checking with our engineers, it’s actually a quite technical challenge to update the name to reflect the current name of the tab for several reasons.
So with that in mind, we’ve backlogged it for now to work on other things like inline editing, and if we hear more confusion or problems around this naming structure, we’ll look to solve that challenge in the future.
@Artur, I was referring to the addition of ‘scroll to’ navigation to forms, especially since real time updates for Airtable will not occur anytime soon.
Again, I ask because there is still no way to add items with conditional fields, then navigate to the list it was added to when the list is located under a tab.