steedos-object-buttons

To add custom actions to Steedos object record pages, create a .button.yml file inside the object's buttons/ directory. This YAML-driven approach defines custom actions with visibility rules, dialogs, and AJAX calls for both record pages and list views.

The Amis schema for Steedos object buttons must be wrapped as a service object to ensure reliable rendering. This root service wrapper supports multiple events including ajax, dialog, reload, and broadcast for complex workflow execution.

Yes, you can hide or customize built-in buttons in Steedos using standard button overrides. The YAML-based button configuration supports overriding default actions to modify visibility or replace built-in behavior on record and list views.

The best way to define multi-action workflows in Steedos is through YAML button files that coordinate multiple events like ajax, dialog, reload, and broadcast. These configurations operate across record and list views for complex behavior execution.

Yes, Steedos supports YAML-driven visibility rules for object buttons. Defined within .button.yml files in the objects/{name}/buttons directory, these rules control when custom actions appear on record pages and list views.