CloudWinks · Foundation apps

TheBossTechnical brief

TheBoss runs business processes: approvals, reviews and other work that passes through several steps and people. It keeps each process definition, moves every running process from step to step, and records what happened.

Read the business brief · PDF

1. Architecture in brief

TheBoss is a Foundation app. The process engine is a SQL state machine in the TheBoss schema: start, complete a step, route and cancel are server functions, and each move is one transaction. Long work is handed off: an AGENT step queues a WorkerBee run, and a TASK or APPROVAL step creates a TaskMaster task; those apps call TheBoss back when they finish, and timers are Conductor schedules. FORM, FUNCTION and NOTIFY steps run in TheBoss itself. The Flutter app is a thin client of the SQL engine.

2. Service boundary and intake

A process starts by its key from an app, a person, a WorkerBee agent or Conductor, and is bound to a business record. Data is mapped into each step by a TheIntegrator mapping key. Routing conditions are GoldenRule decisions, and flows are SEQUENCE, CONDITIONAL, PARALLEL with an ALL join, or LOOP with a cap. Published versions are immutable, pass graph checks and dry-run tests, and are rolled back by republishing an earlier version. Human steps carry due periods and escalation, with TaskMaster task alerts and TheBoss notices queued to BigTalk.

3. Data handled

The model holds process definitions, immutable versions, steps and edges, assignee rules, instances bound to a record, append-only step rows and an event log. An instance keeps its variables while it runs, then follows a retention period and is archived with a hash; no session or IP fields are kept. Process analytics are SQL views over instance steps and events, shown as TheReporter dashboards. Thirty process templates come with CloudWinks, including expense, leave, vendor onboarding and Gatekeeper inbox routing.

4. Integrations and ownership

TaskMaster carries tasks and approvals; WorkerBee runs AGENT steps; GoldenRule decides routing and checks such as payroll controls and appraiser eligibility; Conductor runs timers; BigTalk sends notices; TheIntegrator maps data; TheReporter shows dashboards. Seed workflows connect Zibit manual review, LandMan formal-appraisal sign-off, TjingTjing payroll approval (after which the run is locked, payslips go out and the run posts to BeanCounter) and expense reimbursement ending in a BeanCounter bill to the employee’s Crux person.

5. Security and access

Machine steps run with the starter’s rights, re-checked at every step; human steps run with the assignee’s own rights. A personal process runs with its owner’s rights only. Self-approval of payroll is blocked even for administrators, and an appraiser who is the owner or requester cannot sign off. The Zibit reviewer sees masked data only; any reveal goes through KeyKook and is logged.

Competitive context

AlternativeIts focusCloudWinks product focus
CamundaProcess models that coordinate people, systems and AI agents.Processes tied directly to CloudWinks tasks, AI agents, rules, schedules and business records.
Microsoft Power AutomateCloud flows with approval steps that wait for a response.One shared process engine for every CloudWinks app, with fixed tested versions and separation-of-duty checks.

Read the business brief →

← More Foundation apps apps · All application briefs · How the framework works