Optional
acceptIf this is true, data validation is disabled. This should only be used in contexts where data validation is deferred.
Optional
activityActivity tracking information. If present, activity frames are inserted at key points for diagnostic purposes.
Optional
Readonly
commandIf this is true then data access levels are not enforced. Datatypes and command-related access controls are active.
Optional
exchangeThe Matter exchange in which an interaction occurs.
Optional
Readonly
fabricThe fabric of the authorized client.
Optional
Readonly
fabricIf this is true, fabric-scoped lists are filtered to the accessing fabric.
Optional
interactionIf present the session is associated with an online interaction. Emits when the interaction ends.
Optional
messageThe wire message that initiated invocation.
Optional
offlineIf this is true then access levels are not enforced and all values are read/write. Datatypes are still enforced.
Tracks "offline" rather than "online" because this makes the safer mode (full enforcement) the default.
Optional
sessionThe Matter session in which an interaction occurs.
Optional
Readonly
subjectThe authenticated SubjectId for online sessions.
Optional
Readonly
timedIf this is true a timed transaction is in effect.
Optional
traceA target for instrumentation information. If present, various components will populate with diagnostic information during the action.
The transaction used for isolating state changes associated with this session.
Checks if the authorized client has a certain Access Privilege granted.
Optional
location: Location
Provides contextual information for Matter actions such as accessing attributes or invoking commands.
Matter.js provides an "online" ActionContext for you when responding to network requests. You can also use "offline" agents to invoke cluster APIs Endpoint without an active user session.
See OnlineContext and OfflineContext for details of these two types of interaction.
Context includes:
Authorization details such as AccessLevel, subject and accessing fabric
The transaction required to make state changes
Factory functions for Agent instances you can use to interact with Endpoints
When responding to network requests, low-level contextual information such as the wire message
For the formal definition of an "action" see MatterSpecification.v12.Core § 8.2.4