steedos-object-functions

To expose Steedos server-side object functions as REST API endpoints, define your logic in a .function.yml file, which automatically creates a POST endpoint at /api/v6/functions/{objectApiName}/{functionApiName} for external integrations.

Inside Steedos object functions, you access input data and perform object operations using the ctx-based scripting context, specifically utilizing ctx.input, ctx.params, and the objects.* APIs for structured data validation and modification.

Yes, you can trigger Steedos object functions from amis UI buttons and automation triggers, enabling seamless execution of business logic like validating quotes or updating statuses directly across the platform.

The best way to execute shared business logic in Steedos is defining server-side object functions in .function.yml files, which centralizes logic for invocation from UI buttons, triggers, and external REST API integrations.

Yes, Steedos supports context-aware scripting for server-side object data validation by providing the ObjectQL context, allowing you to robustly handle errors and modify data through ctx.input, ctx.params, and objects.* APIs.

You use .function.yml files to define REST endpoints in Steedos projects because they enforce structured function definitions, automatically exposing your server-side logic via REST API for seamless button, trigger, and external system integration.