A template is the step list for one real job, written out: which targets to pick, which rules to add, what to check before you let it run. Build it once, keep it as your own profile.
Deliberately few. Each one is written against what the extension actually does today; anything we have not verified, we have not published.
Rows from a queue, catalogue or case list into the exact fields you chose, with retries for slow pages and a run log you can read.
TemplateDrive a portal form from the sheet you already maintain, with condition checks before every submit and one-row-first testing.
TemplateOpen the page, read what changed, write it out and leave a log. The same workflow as any other, started by the built-in scheduler.
Every template states the targets to pick and the rules to add, in order, with what to check first.
Same picker, same rule engine — you are copying a recipe into the panel, not installing someone else’s script.
The log is the review step. It shows which values came back empty before anything gets saved at volume.
It becomes a normal ORCA workflow: yours to edit, keep locally, or put on the scheduler.
Describe the steps and we will say plainly whether ORCA can hold them. If it can, the template gets written and published with your job in mind.
