Make the action
predictable.

Build and compare

• Contact Actions remains based on Contacts, with a named FollowUps portal.
• New follow-up enters the blank Task row without creating a record until you type.
• Mark done sits inside the portal row and changes only its task.
• UI scripts call controllers; returned messages explain failure.
• Blank-row click creates no task; repeated completion creates no duplicate.
• Missing DueDate stops the save; correct it and retry.
• Contact count and ContactStatus remain unchanged.
• Reopen: completed task and contact link persist.

Explain the design

Why must Mark done sit inside the portal row?

Why might Done appear before a successful save?

What does the relationship supply when you create the task?

Your notes and questions