A screen function is a named set of actions that belongs to the screen rather than to a component. Any component event, screen event or other function on the screen can run it with the Call routine action.

Screen functions live in Screen properties, not on the canvas, so they take up no space on the screen your users see.

📌 Note: A screen function is only available on the screen it was created on. To reuse actions across several screens in an app, use an App Routine instead.

Why use screen functions

Before screen functions, the usual way to share actions on a screen was to add a button, hide it, put the actions on its Click event, and call that button from wherever the actions were needed.

A hidden button still takes up space on the canvas, so the Builder no longer matches what your users see. A screen function holds the same actions with nothing on the canvas.

For example, a screen has three ways of saving a record: Save, Save and back, and Save and new. Put the saving actions in a screen function called Save record, then call it from each button. If saving ever needs another action, you only change it in one place.

Add a screen function

In the Builder, click a blank section of the canvas to open Screen properties.
Find the Screen functions section, below Events. If the screen has no functions yet, it shows No functions added.
Click +, then Add function.
In the popover, enter a Name for the function.
Click Apply.

To add the function's actions, click the function to open its popover, then click Add to open the action editor. Add your actions the same way you would for any event.

Function names follow these rules:

Rule	Description
Required	Every function needs a name.
Length	Up to 30 characters.
Unique	No two functions on the same screen can share a name. A duplicate shows Function name already exists and Apply stays disabled.

📌 Note: A screen can hold up to 50 functions. When the screen reaches the limit, the + no longer appears.

Edit, rename and reorder functions

Click a function in the Screen functions section to open its popover.

Rename: change the Name and click Apply. Renaming is safe: anything that already calls the function keeps working.
Edit actions: click Edit to open the function's actions in the action editor.
Cancel: closes the popover without saving changes.

Functions are listed in the order they were created. Drag a function up or down to reorder the list.

Call a screen function

Run a screen function with the Call routine action.

Open the action editor for the event that should run the function. This can be a component event, a screen event (such as Load), or another screen function.
Add a Call routine action.
In Select a routine, choose the function under the Screen functions heading.

The routine list is grouped into three headings:

Heading	What it lists
Screen	Events on components of this screen.
Screen functions	Functions on this screen.
App	App Routines in this app.

A function can be called from as many places as you need, and more than once in the same set of actions.

You can also find a screen's functions in the action editor's left navigation, under SCREEN FUNCTIONS. Select one there to edit its actions.

See where a function is used

Each function in the Screen functions section has a references icon.

Click it to open Function references, which lists every component and event that calls the function.
If nothing calls the function, the icon is disabled and shows No function references.

Delete a screen function

Click the delete icon next to the function.

If the function is still called anywhere, the delete icon is disabled. Use the references icon next to it to find each caller, remove those Call routine actions, then delete the function.
If nothing calls the function, a confirmation appears. Deleting the function also deletes its actions.

📌 Note: If you delete a function by mistake, you can undo it with ⌘Z.

Convert an event into a screen function

Convert to function turns an existing component event into a screen function. Anything that already calls that event keeps working and now calls the function instead.

This is the quickest way to clear hidden buttons off screens moved to the new Builder.

In Screen functions, click +, then Convert to function.
Fill in the dialog (see the table below).
Click Convert. Convert stays disabled until an event is selected.

Field	Description
Name	The name of the new function.
Component	The component that holds the event.
Event to convert	The event whose actions become the function.
Delete original event / component	Checked by default. Its label depends on whether the component itself can be removed (see below).

If nothing else references the component, the checkbox reads Delete original component. Leave it checked to remove the component from the canvas, which is how a hidden button is cleared in one step. If another component still references it, the checkbox reads Delete original event instead, and only the converted event is removed.

Copying screens and actions

Copy actions: Screen functions is available as both a source and a destination in the copy actions dialog, so you can copy actions into or out of a function.
Copy a screen: the copy keeps the screen's functions, in the same order. Anything calling a function on the copy calls the copy's function.
Publish an app: published apps keep their screen functions, so accounts that install or update the app get them too.