Skip to main content
Knowledge mapWhat happens after a click?ArcBlock

You are here. See how this question connects to other ideas.

Select a node to open its page · Expand to read within the map

Knowledge mapFollow a connection. Understand a question.
← AFS and interfaces

One question

What happens after a click?

Trace an interface event to an explicit operation target.

Complete is an action on a task card. A click is an event; completing the task is a business operation. An AUP event binding connects them.

json
{"id":"complete","type":"action","props":{"label":"Complete"},"events":{"click":{"exec":"/example/tasks/.actions/complete","args":{"id":"talk"}}}}

The structure says: clicking the node named complete invokes /example/tasks/.actions/complete, passing talk as the task identifier.

This is a teaching path. It executes only if the application provides and authorizes that action. A working button appearance does not prove a successful operation.

Interfaces also have temporary state: an open menu, selected tab or validation message. These are not all shared business data. The source explicitly makes input validation state client-only and excludes it from AFS persistence.

To understand an interaction, locate the triggering node, event name, operation target, arguments, and how the result reaches the view. This sequence also helps inspect demos and design tests.

Further reading

Technical documentation: read the full reference.

Check your understanding

What separates a click from a completed business operation?

The event mapping, target, arguments, authorization and execution result—and the path by which the result reaches the interface.

Continue along a learning path