System · StartupBuilder

Properties

Property	Type	Required	Description
`job`	`string`	required	The one job it does.

JSON

{
  "$id": "https://api.sb/routewise.dev/systems/system_1",
  "$type": "System",
  "job": "Example job"
}

A System is connected via many Integrations: an Integration connects an outside Source to one System, with credentials at Studio, Startup or Customer scope. connectedVia, inverse connects.
A System defines many Nouns: the Nouns a System keeps records of; several Systems can share one Noun. defines, inverse definedIn.
A System is packaged as many Software Products: Software ships Systems to its Customers as one Product, headless or with an App. packagedAs, inverse packages.
A System is run by many Startups: a Startup runs its work on headless Systems, such as CRM or billing, that every Startup shares. runBy, inverse runs.
A System runs on many Capabilities: a System is built on Capabilities, such as Workflows or Search, that every Startup reaches with one key. runsOn, inverse runs.

createCreates a System.
POST /{namespace}/systemsdoSystem.created
getReturns one System by id.
GET /{namespace}/systems/{id}readNo Event
listReturns Systems, newest first, one page at a time.
GET /{namespace}/systemsreadNo Event
updateChanges the given properties of a System.
PATCH /{namespace}/systems/{id}doSystem.updated
deleteDeletes a System; its history is kept.
DELETE /{namespace}/systems/{id}doSystem.deleted

Which Access level may call each Verb. One-way Verbs wait their delay window.

Operation	`owner`	`admin`	`member`	`viewer`
`System.create`	Yes	Yes	Yes	No
`System.get`	Yes	Yes	Yes	Yes
`System.list`	Yes	Yes	Yes	Yes
`System.update`	Yes	Yes	Yes	No
`System.delete`	Yes	Yes	Yes	No

Text

Add a system to LedgerLark.

The CRM System holds Contacts, Deals, and Quotes for every Startup in the Studio, each Startup seeing only its own.