Skip to content
2finity.com
2finity.com
2finity.devSign in

CORE layer 06 of 10

Workflows

Tasks, approvals, automations, processes, triggers and state transitions: how work moves and who signs off.

2finity CORE and the interfaces and participants connected to it
COREWebsiteApplicationsChatAgentsPeopleCompaniesPartnersEnterprise
CORE
The shared operating layer. Ten layers: Identity, Organizations, People, Relationships, Knowledge, Workflows, Commerce, Finance, Communication, Data.
Website (interface)
Public sites and portals that read content and catalog data and submit forms through CORE. Uses the Identity, Knowledge, Commerce and Data layers. Example capabilities: page.get, catalog.list, form.submit.
Applications (interface)
Internal, mobile and dashboard apps: views into CORE with the signed-in identity's permissions. Uses the Identity, Organizations, People, Workflows and Data layers. Example capabilities: customer.get, workflow.start, approval.decide.
Chat (interface)
2finity.chat and other conversational interfaces: language resolved to capabilities, with approval. Uses the Identity, Knowledge, Workflows, Finance and Communication layers. Example capabilities: site.content.update, invoice.create, permission.grant.
Agents (interface)
Actors with their own identity, an owner and scoped permissions; every action leaves an audit event. Uses the Identity, Knowledge, Workflows and Communication layers. Example capabilities: site.publish, deployment.rollback, workflow.start.
People (participant)
Humans in any context: professional, employee, customer or supplier, with one identity throughout. Uses the Identity, People, Relationships and Communication layers. Example capabilities: customer.get, permission.grant, message.send.
Companies (participant)
Organizations that own their data, run their workflows and decide who and what may act inside them. Uses the Organizations, People, Relationships, Commerce and Finance layers. Example capabilities: organization.get, invoice.create, order.update.
Partners (participant)
Other organizations connected by a relationship: suppliers, resellers and agencies see what it grants. Uses the Identity, Relationships, Commerce and Data layers. Example capabilities: catalog.product.get, order.update, permission.grant.
Enterprise (participant)
Large organizations running CORE in an isolated deployment with their own identity provider and policies. Uses the Identity, Organizations, Workflows, Finance and Data layers. Example capabilities: permission.grant, deployment.publish, workflow.start.

Scope

What it holds

How does work move?

A workflow describes how an entity moves from one state to another and who has to agree along the way. Approvals, scheduled jobs, triggers on events and multi-step processes are all workflows. Agents take part as actors: an agent can start a workflow and propose a step, and a human approval can be required before anything is published or paid. Deployments and rollbacks are workflows over revisions.

Model

Example entities

  • Workflow
  • Task
  • Approval
  • Trigger
  • Automation
  • Process definition
  • Step
  • Deployment

Contract

Capabilities

Every action on this layer is a named capability with a permission check and, where something changes, an event.

  • workflow.start→ workflow.started

    Start a workflow instance for an entity.

    Member of the organization
  • workflow.get

    Named in the layer model; not yet described in the catalogue.

  • task.create

    Named in the layer model; not yet described in the catalogue.

  • task.complete

    Named in the layer model; not yet described in the catalogue.

  • approval.request

    Named in the layer model; not yet described in the catalogue.

  • approval.decide→ approval.decided

    Approve or reject a pending step.

    Privileged role or approval
  • deployment.publish→ deployment.published

    Promote a revision set to live.

    Privileged role or approval
  • deployment.rollback→ deployment.rolled_back

    Return a site or application to a previous revision.

    Privileged role or approval
The full catalogue

Connections

Relationships

The layers Workflows reads from and writes to most often.

  • 05

    Knowledge

    What do we know and publish?

    Documents, structured knowledge, policies, published content and context: what the organization knows and shows.

    Open layer
  • 07

    Commerce

    What do we sell?

    Products, services, catalogs, quotes, carts and orders: what an organization sells and how it is bought.

    Open layer
  • 08

    Finance

    What is owed and paid?

    Invoices, payments, costs and financial records: the money side of every order, contract and relationship.

    Open layer
  • 09

    Communication

    How do we talk?

    Messages, conversations, notifications and threads between people, agents and organizations.

    Open layer

Consumers

How interfaces use it

The interfaces and participants on the CORE graph that read or write this layer, with the capabilities of this layer they name.

  • Applications interface

    Internal, mobile and dashboard apps: views into CORE with the signed-in identity's permissions.

    workflow.startapproval.decide

  • Chat interface

    2finity.chat and other conversational interfaces: language resolved to capabilities, with approval.

    Uses the layer; its featured capabilities belong to other layers.

  • Agents interface

    Actors with their own identity, an owner and scoped permissions; every action leaves an audit event.

    deployment.rollbackworkflow.start

  • Enterprise participant

    Large organizations running CORE in an isolated deployment with their own identity provider and policies.

    deployment.publishworkflow.start