Skip to content

Solutions · Available now

Process Design: don't adapt to the software, make it fit how you work

CloudotNet Process Design is a tool that lets you build, step by step and without code, when a job starts, which path it takes under which condition, who approves it, how long to wait and who is notified. Approvals, notifications and scheduled work are at its core. It works inside every CloudotNet solution, and the rules you set flow straight into your team's daily work.

Problems it solves

The software dictates its own flow

Off-the-shelf tools assume a single way of working. Here you decide the approval order, notifications and timing yourself.

Every change waits for a developer

Adding an approval step or changing a condition doesn't mean waiting on anyone. You edit the steps yourself.

Approval order depends on people

Who approves what is set up once and applied the same way every time. People may change; the process doesn't.

Reminders are done by hand

Approvers are notified automatically and pending approvals sit in one list. You put regular reminders on a schedule, so there's no more chasing people on the phone.

What's inside

  • WhenStarts when a task or record is created or completed, or on a schedule
  • IfSend the process down a different path by priority, amount or location
  • Who approvesSingle or sequential approval; a pending approvals list and approval history
  • WaitWait for a set time, then move on to the next step
  • NotifyEmail and in-app notifications
  • Create recordCreate a record or look up existing records within the process (with Records & Forms)
  • Sub-processBuild steps you use often as a separate process and run it from other processes

Example processes

These processes are examples of what you can build with Process Design. You set up your own process by choosing the steps, and we're happy to help with the setup.

Staff leave requestExample process
  1. When

    When an employee fills in the leave request formWith the date range and a note

  2. If

    If the leave is longer than 3 daysOtherwise the manager's approval is enough

  3. Who approves

    Line manager first, then HRApproved in order

  4. Notify

    Tell the employee the outcomeApproved or rejected

Frequently asked questions

Do I need software skills to design a process?

No. A process is built by choosing the steps “when does it start, under which condition, who approves, how long to wait, who is notified”. No code is written.

Which solutions does Process Design work in?

All of them. Today it works on your tasks and your own records, and the solutions on our roadmap, such as requests, inventory, purchasing and staff, will use the same process design.

Can I change a process after setting it up?

Yes. As the way you work changes, you can edit steps, conditions and approvers at any time.

How are notifications sent?

Notifications go out by email and as in-app notifications. SMS notifications are on our roadmap.

Can I use the example processes?

The examples on this page, such as leave requests, inspection findings and spend approvals, show what you can build with Process Design. You set up your own process by choosing the steps, and we're happy to help with the setup.

Got a question? Let's talk directly.

Tell us about your work and we'll walk you through the right setup on screen. Or just give us a call.