When to involve developers
You can build and test most forms in Designer. Some tasks need your technical team.
Authors usually own
- Layout, labels, and field keys
- Validation rules from the Rules picker
- Creating and naming Code actions in Designer for approved form logic
- Attaching available Common, Code, and Custom actions to component events
- Preview testing and export for review
Code versus Custom actions
| Type | Where it is defined | Author’s role |
|---|---|---|
| Code | In Designer and stored with the form | Create, name, edit, and attach approved logic |
| Custom | In the host application’s actions property | Attach available actions; request new ones |
Developers usually own
| Topic | Why |
|---|---|
| Installing Designer in your app | Installation |
| Form storage and APIs | Form storage |
| Registering Custom actions and integrations | Actions |
| Custom components in the palette | Custom components |
| Computed properties and complex Render When | Computed properties |
| License keys for paid features | License key |
| Designer UI customization | Designer customization |
Hand off cleanly
Use Hand off to your technical team with export files and a field key list.
Summary
Use the Form Author Guide for authoring tasks. Authors can create Code actions in Designer. Involve developers to register new Custom actions or when logic needs APIs, secrets, or application code. Do not change production Code actions or form validators without review.