Table of Contents

Was this article helpful?

6: Redundancy

Depending on what kind of app you’re running, choosing to run an app on a mobile device like a smartphone means you might end up doing a lot of scrolling to get to the top or bottom of a given screen. Since we want our app to be user-friendly, Method best practice says you should include a redundant Save button at the top of the screen so a mobile user doesn’t have to scroll all the way to the bottom just to save a record.

Customize the New Car screen.

Select the top secNav and click the Cols + icon to add a column.

Select the new column (on the right) and change the alignment of the cell to Top Right.

Next, drag a text object into this cell, and change the text to "Save".

You’ll notice Method automatically calls this object “Save1” on the canvas. That’s because you already have another text object called “Save” on this screen, so it’s designed to help you keep track of which is which. Don’t worry; it will still show up as “Save” in the published version of the screen (you can switch to Preview mode to check if you don’t believe us!)

Click Show icon, then find and select the Save icon.

Underneath Style, change the Text Color to Primary.

This new Save object is meant to perform the exact same actions as the other save object on this screen. Do you remember how we told the object to do the actions of another control? It's Call Another Action Set.

Select down arrow of the new Save object and select the Click event.

Search for and add Call Another Action Set.

For Select An Action Set choose Save (Click).

Add an Internal Note: "Do the actions of the bottom save button".

Close the Action Editor and then close Design Mode.

Now the top Save link will act just like the bottom Save button because it's calling the same actions.

The great thing is, if you need to alter how the save works, you just have to change the bottom Save button.