By role Business configurators

Clicks, plain sentences and instant tests, on live rows, with a validator that catches mistakes before a save.

For the person who builds the app. This page says what SmartApps put in your hands, what stays with other roles, and how a week runs.

A week

How a week runs with SmartApps

Monday
Draw the lanes for a returns process; the validator shows green.
Tuesday
Draft three screens from the handlers; rename labels; set visibility by role.
Wednesday
Write four criteria; each shows the live rows it selects as you type.
Thursday
Preview as customer, agent and warehouse; the process owner signs the preview.
Friday
Publish version 1; watch the first instances on the board.
Yours and theirs

What you do yourself, and what other roles keep

Yours

  • Screens: components, layouts, properties, validation, actions
  • Criteria, decisions, clocks, in the expression editor
  • Hierarchies and lanes, roles and scopes
  • Variables and their tests

Kept by other roles

  • New connectors and objects
  • Write-back switches
  • Functions and REST calls that need code
Apps you will meet first

Questions

Do I need to code?

Formulas cover conditions, calculations, dates, text and lists; scripts and REST calls are registered once by the app team as functions you call by name.

What stops me from breaking something?

The validator refuses a save that references a missing field or removes a handler a screen uses; the preview holds writes; the publish gate needs the owner's approval.

Where do I learn?

The documentation's configuration guide, the 30-minute first-app walkthrough and the catalogue entries, each a worked example.

See it from your seat

Tell us your role and one process; the demonstration runs the screens you would use, on data like yours.