Playground to Draft Process
Watch how to design automation processes from playground to draft.
About this video
Watch how to take a process you have built and tested in a Kognitos Playground and save it as a Draft, ready for peer review and publication.
What you will learn
- The difference between a live Playground session and a saved Draft Process
- How to capture your Playground work as a versioned Draft
- What reviewers see when they open a Draft for approval
- The next step: publishing the Draft to a live scheduled automation
Common questions
What is the difference between a Playground and a Draft Process in Kognitos?
A Playground is a free-form, interactive environment where you write and test automation steps in plain English. A Draft Process is a saved snapshot of your Playground work, structured for peer review before publishing to production.
When should I move from Playground to Draft?
When your automation handles the expected happy path reliably and you want a reviewer to sign off before it runs live. Draft is the checkpoint between experimentation and production, not a required step for every iteration.
What happens to my Playground when I create a Draft?
The Playground remains intact and editable. Creating a Draft exports a versioned snapshot. You can keep iterating in the Playground and create new Drafts from later versions without affecting the existing Draft.
How do I publish from Draft to a live process?
From the Draft view, use the Publish action to promote the process to production. You set the schedule or trigger, runtime parameters, and exception notification routing. The Published Process runs with full Learnings and audit logging enabled.