By role Process owners

You own the process; the app should be yours too.

For the person who owns a process. 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
Read the boardRead the board: open instances, clocks about to run out, decisions taken last week.
Tuesday
Adjust a criterion in the expression editor; test it on live rows; publish version 4 with a note.
Wednesday
Sit with the configurator for a new screen; preview it as each role.
Thursday
Sign the promotion of the new version; write-back for one more object switched on by the app team after its test write.
Friday
Read the weekly digest; answer an auditor's question from the log in a minute.
Yours and theirs

What you do yourself, and what other roles keep

Yours

  • Screens, criteria, clocks and roles of your apps
  • Versions and change notes
  • Who sits at which level, alternates and delegates
  • Measures on the board and the weekly digest

Kept by other roles

  • New connectors and new objects in the catalog
  • Write-back switches per object, after a test write
  • Promotion gates and environments
  • Registered functions and REST calls
Apps you will meet first

Questions

Do I need IT to change a rule?

A criterion is yours: edit it in the expression editor, test it on live rows, publish a version. IT keeps the gates for new connectors, new write-backs and promotion.

How do I know the app is right before people use it?

Preview runs it as each role on live rows with writes held; publish when the preview matches the process.

What happens when the organisation changes?

Update the hierarchy; running instances finish on the version they started on, new ones use the new hierarchy.

See it from your seat

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