plutonium-definition-actions

You can define custom resource actions in Rails by using a ResourceDefinition to declare action types like resource_action, record_action, or bulk_action, paired with Interaction classes to drive the underlying business logic and UI inputs.

The best way to add bulk actions to a resource portal is by declaring a bulk_action within your ResourceDefinition, optionally pairing it with an Interaction class to handle multi-record processing and declarative inputs.

Yes, you can inherit actions from a base ResourceDefinition and override or extend them per portal, allowing customized behavior and governance while maintaining consistent UI integration and authorization checks.

Interactive actions work by pairing an action declaration with an Interaction class that uses declarative inputs to capture user data, driving complex business logic directly from the resource UI.

Yes, defining custom resource actions includes ensuring authorization through policies and default CRUD plumbing, governing access to interactive, bulk, and simple actions across portals and definitions.

Use collection_record_action when you need to apply operations across multiple records within a collection context, whereas record_action targets single record operations within your resource definition.