Save Model

Last Updated 09.28.03

General Description

An extensive usability study was performed to understand the user's mental model for "saving" changes they have made on a BLAF application page. Multiple options were tested to watch when a user explicitly selected a button, like "Apply" to save data, and when he/she did not, but assumed that the updates they made were still "saved". This guideline lists general findings from this test as well as outlines the expected "save" behavior for all interactive elements in the UI of many common templates used throughout BLAF applications.

Each object template may be view-only state or updatable state, etc. These same templates are the basis for Table Navigation/Action Methods and Table Flows.

Guideline Attributes

Spec Version # - 3.1
Spec Contributors - Betsy Beier, Craig Louis, Lisa Serface
UI Models - all models
Example Products - all products
Related Guidelines - Object List Templates, Object Templates, 2 Step Template, Step by Step (3[+] Steps) Template, Step by Step Page Flows, Long Page and Overview Page Template, 1 Step Transactional Form page, Table Navigation/Action Methods, Table Flows, Action/Navigation Buttons, Tab/Navigation: SubTabs

Interaction and Usage Specifications

General Principles

Note: The term "Apply" may be "Submit" or "Finish" depending on the page templates. These buttons do the same "save" function, but are labeled differently based on the page template. In usability testing, users did not have problems with the term "Apply". See Language in UI for detail terminology usage.


Save Model for Object List Template - with Updatable Table

High Level Summary

Apply works at page level. Table actions and record navigation cache or temporarily save changes.

Detailed Save Model and Interaction Expectations - Object List with Updatable Table

User updates information in the table or on the page, then selects ...

Related Guideline



Save Model for Object List Template with Non-Updatable Table

High Level Summary

No Page level apply needed (only unless other updatable label/data pairs on page.) Saving only done on detail level pages.

Note: Occasionally, an Object List templates with a non-updatable table may also contain updatable label/data pairs on the same page. If this is the case, then page level "Apply" functionality needs to be used. The picture below does not show this scenario.

Detailed Save Model and Interaction Expectations - Object List with Non-Updatable Table

User updates information in the table or on the page, then selects ...

Related Guideline

Save Model for 1 Step Object Template

High Level Summary

Apply works at page level. Table actions and record navigation cache or temporarily save changes.


Detailed Save Model and Interaction Expectations - 1 Step Object Template

User updates information in a table or on the page, then selects ...

Related Guidelines

Save Model for 2 Step Object Template/ 2 Step Process

High Level Summary

Continue/Review caches or temporarily saves between pages of process. Finish/Submit saves updates from both pages. Table actions and record navigation cache or temporarily save changes.

Detailed Save Model and Interaction Expectations - 2 Step Object Template/ 2 Step Process

User updates information in a table or on the page, then selects ...

Related Guideline

Save Model for 3(+) Step by Step Process: Finish Before End

High Level Summary

Next/Back caches or temporarily saves between pages of process. Finish/Submit saves updates from all pages. Table actions and record navigation cache or temporarily save changes.

Detailed Save Model and Interaction Expectations - 3(+) Step by Step Process: Able to Finish Before End

User updates information in the table or on the page, then selects ...

Related Guideline

Save Model for 3(+) Step by Step Process: Finish at End

High Level Summary

Next/Back caches or temporarily saves between pages of process. Finish/Submit saves updates from all pages. Table actions and record navigation cache or temporarily save changes.

Detailed Save Model and Interaction Expectations - 3(+) Step by Step Process: Only Able to Finish at End

User updates information in the table or on the page, then selects ...

Related Guideline

Save Model for Side Navigation Object Template/NonLinear Sections

High Level Summary

Apply saves updates from all pages within side navigation. Between side navigation sections, caching or temporarily saving data occurs. Table actions and record navigation cache or temporarily save changes.

Detailed Save Model and Interaction Expectations - One Section Page of Object Template with Side Navigation (Nonlinear Sections)

User updates information in a table or on the page, then selects ...

Related Guideline

Save Model for Side Navigation Object Template/Suggested Linear Sections

High Level Summary

Apply saves updates from all pages within side navigation. Between side navigation sections, caching or temporarily saving data occurs. Table actions and record navigation cache or temporarily save changes.

Detailed Save Model and Interaction Expectations - One Section Page of Object Template with Side Navigation (Suggested Linearity)

User updates information in a table or on the page, then selects ...

Related Guideline

Save Model for SubTabs Object Template/Nonlinear Sections

High Level Summary

Apply saves updates from all pages within SubTab Bar. Between subtab sections, caching or temporarily saving data occurs. Table actions and record navigation cache or temporarily save changes.

Detailed Save Model and Interaction Expectations - One Section Page of Object Template with SubTabs (Nonlinear Sections)

User updates information in a table or on the page, then selects ...

Related Guideline

Save Model for Process Within Process

High Level Summary

BLAF users perceive process when working through a sequence of template pages to perform a task or tasks. Completing a process (main process) may occasionally require the user to temporarily depart from the main process, complete a supporting process (subprocess), and return to the departure point in the main process, from where they proceed to overall completion.

Testing shows that users generally perceive their work in a main process, the departure to subprocess, and return to main process as a single overall process. What is not so obvious to them is whether or not their work on subprocess pages is saved to the database when they return to the main process. Based on the test results showing the perception of overall process, BLAF recommends that subprocess changes shall not be saved to the database, but should be cached along with the current main process changes, until the main process itself is applied or cancelled. Clear indications that the user is entering or departing from a subordinate subprocess should be provided.

Conclusions

Save Model Interaction Recommendations - Process Within Process

Based on testing, the following approach is recommended, and is intended to supplement the detailed interaction expectations listed in the sections above:

Related Guidelines

Refer to these BLAF Guidelines for more information on process within process:

Visual Specifications

See above schematics and related guidelines.

Open/Closed Issues