I imagine you're referring the Home Page in admin mode, correct? If so,
unfortunately not, you can't add or remove buttons through a configuration.
But this is something that we might want to allow in the future: could you
tell us more about what what your use case for this is?
> +1 for the ability to add buttons to the home page. I'd like to add a
> to navigate a user like the form details button allows.
I am not sure to understand what you are saying: would the button do the
same thing as what clicking on a row of the table on the Form Runner home
page does right now, that is take users to the "summary" page for the form
(or the "new" page if they can't access the summary page)? And where would
you want that button to be shown?
The location of the button isn't important. Along the bottom of the table
like summary or details pages is fine, or along the top like the other
buttons/menus in the home view will work as well.
Imagine I want a button on the home screen to hyperlink the user to a
specific form without having to scroll through the tabular view.
I have a form with an http service that writes information about the user
and they should fill it out and submit it BEFORE filling out any other
forms. like a "register" or "sign up" view for instance, where they enter
some meta-data that is stored in a third party application server and
referenced from other forms in the table.
The use case is purely around the user experience, and more specifically for
In the current release, that user experience is messy. The buttons for
navigation are mixed in with the buttons for actions. For example: on the
details pages, SUMMARY (a navigation button) is next to PDF, SAVE, DELETE,
SUBMIT (actions). Also, there's no consistency: some pages don't have any
buttons, and the ones that do, have different buttons from page to page.
That obviously makes sense for the 'action' buttons (because they aren't
relevant on some pages) but the navigation should be able to be made
consistent, and separated from actions.
Specifically today, we're looking to have an experience where a user can
navigate from RUNNER to BUILDER and LOGOUT without having to type in a URL.
And the ability to navigate to BUILDER from RUNNER SUMMARY or DETAIL, and
the ability to navigate to RUNNER from BUILDER SUMMARY or DETAIL.
> The location of the button isn't important. Along the bottom of the table
> like summary or details pages is fine, or along the top like the other
> buttons/menus in the home view will work as well.
Got it; for now I added an RFE (see link below) to keep track of this, and
thank you for the feedback.
mark reitzel wrote
> In the current release, that user experience is messy. The buttons for
> navigation are mixed in with the buttons for actions. For example: on the
> details pages, SUMMARY (a navigation button) is next to PDF, SAVE, DELETE,
> SUBMIT (actions).
I agree, so let's see how we can improve this! Maybe use links for
navigation and buttons for actions? I see mixing links and buttons at the
bottom of the table as decreasing readability (and just look plain ugly!).
Maybe we could keep buttons just for actions, and move links inside the
table (like edit, view, PDF) or to the menu bar if they are global (like
summary, link to home page). The latter would also maybe solve the
consistency issue you were talking about. What do you think?