Button Actions and Custom Screen Navigation

[Jermaine_Richards]

Issue 1: Adding “Show Notification” Action to Existing Button

When attempting to add a “Show notification” action to an existing button (in my case, a “Generate PDF” button), the system creates a separate, visible notification button on the screen rather than adding the notification as an invisible action to the existing button. This behavior is counterintuitive and creates poor UX, as users see two buttons instead of one button with multiple actions.

Expected behavior: Adding “Show notification” should append an invisible action to the button’s action sequence

Actual behavior: Creates a new, visible notification button component on the screen

Issue 2: Unable to Navigate to Custom Screens from Button Actions

I’ve been unable to navigate from a button action to a custom screen (specifically, a confirmation screen after generating a PDF). The available navigation options (“Go to tab”, “Show new screen”, “Show detail screen”) either don’t work with custom screens or aren’t available in the action menu. This makes it impossible to provide proper user feedback after completing actions.

Attempted workarounds:

“Go to tab” - doesn’t work (custom screens aren’t tabs)

“Show new screen” - requires configuration that doesn’t allow custom screen selection

“Show detail screen” - requires a data source, which confirmation screens don’t have

Impact on Development:

These limitations have extended my development timeline by 2+ days as I’ve attempted multiple workarounds.

Questions:

1. Are these limitations specific to the Explorer plan, or are they fundamental design decisions in Glide?

2. Is there a documented workaround for either of these issues that I’m missing?

Thank you for your time and assistance.

[nathanaelb]

Hello Jermaine, welcome to Glide’s community forum

The actions you associate to a component in the layout editor are single actions.

If you want the click of a button to trigger a series of actions, you need to create a workflow. Head over to the workflows editor (see image below), and there you can create a new workflow. Choose the trigger first, then string actions together.

[nathanaelb]

@Jermaine_Richards

“Show new screen” - requires configuration that doesn’t allow custom screen selection

Why has this option not worked for you? It should work fine.

See Show New Screen documentation

[ThinhDinh]

@Jermaine_Richards

I’ve been unable to navigate from a button action to a custom screen (specifically, a confirmation screen after generating a PDF). The available navigation options (“Go to tab”, “Show new screen”, “Show detail screen”) either don’t work with custom screens or aren’t available in the action menu. This makes it impossible to provide proper user feedback after completing actions.

Attempted workarounds:

“Go to tab” - doesn’t work (custom screens aren’t tabs)

“Show new screen” - requires configuration that doesn’t allow custom screen selection

“Show detail screen” - requires a data source, which confirmation screens don’t have

Sounds like you’re trying to navigate to a screen you have already built in another workflow?

If you’re using “Show New Screen”, your current tab/screen must be built on top of the same table as the existing workflow above to be able to reuse the workflow (not the screen itself).

If you’re using “Show Details Screen”, you just need to have a relation/single value from the current table to the table of that screen to reuse it (Show Details Screen > relation/single value).