Filter the view.
Keep the work.

Build and compare

• Back up the closed Lesson 3 file; preserve the corrected Overdue cue.
• Contacts::gTaskView: Text, global storage, one repetition. Task views list: All and Open.
• Duplicate Contact Actions as Contact Task Views, based on Contacts.
• Use the documented Case calculation on FollowUps portal; blank means All.
• Six scripts: UI handlers and controllers for Apply view, New follow-up and Mark done.
• Commit with validation before Apply view. New follow-up sets All before entry. Mark done refreshes only after a successful save.
• Preserve the original Contact Actions layout and scripts.

Test a disposable copy

1. Use a disposable practice copy. In Browse mode, choose Contact Task Views from the Layout menu and use Form View. Record the Contacts toolbar count.
2. Select Alex Rivera. Choose All and click Apply view. The supplied file has three Done tasks for Rivera. Scroll the portal to see every row; visible row slots are not a task count.
3. Choose Open and Apply view. Rivera should have no matching existing tasks. A blank entry row may still be present. Return to All and verify all three Done tasks remain.
4. With Open selected, switch to Alex Morgan. The global choice stays Open; Morgan’s “Send project outline” appears. Confirm the contact names, email and task agree. The Contacts found-set count stays unchanged.
5. On Morgan, click New follow-up while Open is selected. Expect Task view to become All and the blank task row to be selected. Enter “Review the draft,” a valid due date and Status Open. Commit before changing the view. No new contact should be created.
6. Choose Open and Apply view. On “Review the draft,” click Mark done. After a successful save and refresh, it should disappear. Choose All and Apply view; confirm that same task remains with Status Done. Other tasks must be unchanged.
7. In All, click Mark done on the blank row. Expect a message and no new task. In a practice copy, clear a saved task’s required Task text, then click Apply view: expect a save/validation message. Restore the text and commit before continuing.
8. Use Contacts to return to the original Contact Actions layout. Confirm its unfiltered portal and existing New follow-up/Mark done actions still work. Use the Layout menu to return to Contact Task Views. Also check Tasks, Open tasks, All tasks, Report and Back to Tasks; those task found-set operations remain separate.
9. Save, close and reopen the practice copy. Verify saved task data, choose the view explicitly and apply it. Check labels, field padding, button anchors and portal scrolling at the intended window size. Discard the practice copy when finished.

Explain what you learned

How does the relationship’s job differ from the portal filter’s job?

Why is the Contacts toolbar count unchanged when a task disappears?

Why switch to All for entry, and refresh only after saving a completed task?

Your notes and questions