FILESOFT ACADEMY / COURSE 3 / LESSON 1
Check every
navigation route.
Print this worksheet or save it as PDF from your browser.
Back to the lesson ↗Build and compare
- Back up the saved, closed Course 2 file.
- Three controller scripts: Browse-mode guard, validated commit, immediate error checks and direct Go to Layout.
- Three UI scripts: error capture, matching controller call and returned-message dialog.
- Contacts, Tasks and Report buttons on Contact Actions and in the overview Header.
- Contact Actions stays Form View; overview/report stay List View.
- Buttons remain aligned on the left when the window is resized. Every button opens the expected layout. Repeated navigation creates no records.
- Invalid task entry prevents leaving; correct it and navigate successfully.
- Open found set carries from overview to report. Back to Tasks returns to the overview in Browse mode and is absent in Preview/PDF.
- Existing New follow-up and Mark done actions still target the intended task.
- Close/reopen: buttons, records and statuses persist.
Explain the context
Why does the toolbar count contacts on one screen and tasks on another?
Why does Contacts not automatically select the parent of a task?
How do you return from the printable report?