backend-actions

Drumr backend actions require clear execution contracts that separate request handling, validation, and persistence logic into the correct layers. You must choose the correct action type for GlobalAction, ModelAction, or ObjectAction work, define in-file parameter models, and apply the correct canExecute guard signatures.

To define backend action parameters correctly, you should use in-file parameter models that include validation rules, GraphQL exposure settings, and default values. This approach ensures action contracts remain consistent across frontend and backend ownership boundaries.

Handling transactions and permissions requires selecting the appropriate transaction choice for your write or bulk execution operations and registering the necessary permissions. Your backend actions must implement correct canExecute signatures to enforce these permission boundaries securely.

Yes, backend actions can be used for scheduled workflow actions and background jobs. The execution contracts cover transactional writes, bulk execution, and scheduled background jobs, ensuring consistent behavior across all backend and frontend boundaries.

GlobalAction, ModelAction, and ObjectAction distinguish the scope of your backend execution contracts. GlobalAction handles application-wide work, ModelAction targets all records of a specific type, and ObjectAction operates on a single specific record, each requiring distinct canExecute signatures and permission registrations.