Skip to main content

Developers · Examples

Kinetic reference builds: one per solution area

We are preparing three reference builds: a vendor onboarding portal, employee onboarding across HR and IT, and a service catalog in front of ServiceNow. None is published yet. Each goes up only after it has been imported into a clean space and run against a real tenant. Until then, the Getting Started guides cover the same pieces.

Start today The Getting Started series in Platform Guide 6.1 covers forms, integrations and workflows step by step.

Reference builds

What each build covers

Each build covers one cross-system process and uses only published integrations or ones you can define as Connections.

  • Client Management Being prepared

    Vendor onboarding portal

    Problem. Vendors email documents to procurement, someone rekeys them into the ERP, and nobody can see where an application stands.

    What it shows

    • A portal bundle signed in through an OAuth client, showing each vendor its own requests
    • A workflow that routes approvals, then creates the vendor record in the ERP
    • Status written back to the submission so the vendor sees progress

    Layers: Experience, Workflow, Integration

  • Work Management Being prepared

    Employee onboarding across HR, identity and IT

    Problem. A new hire touches the HRIS, Active Directory and the service desk, and the steps are tracked in a spreadsheet.

    What it shows

    • A WebAPI the HRIS calls when a hire is confirmed
    • A routine that creates the account and assigns groups using the Active Directory handlers
    • One submission that holds the status of every step

    Layers: Workflow, Integration

  • Service Management Being prepared

    IT service catalog in front of ServiceNow

    Problem. Employees navigate a service desk built for agents, and requests that span several teams are split by hand.

    What it shows

    • A catalog Kapp with request forms grouped by category
    • Workflows that create and update ServiceNow records through the published handlers
    • Fulfillment updates from ServiceNow sent back to Kinetic through a WebAPI

    Layers: Experience, Workflow, Integration

What a published build contains

A build is listed as available only when all four are in place.

  • An export of the Kapp, forms and workflows as JSON and XML, ready to import into a space
  • Setup steps for the integrations, with placeholders for your credentials
  • The API calls used to test it, run against a real tenant
  • The Kinetic version it was tested on

Questions about the examples

Answered by Kinetic Data. Last updated .

  • Is there a public repository I can clone?

    Not yet. Each build is published only after it has been run against a real tenant. Until then, the Getting Started series in the docs covers the same building blocks.

  • Why one build per solution area?

    Most Kinetic projects are client portals, cross-department processes or service catalogs. One build for each shows the pattern a team reuses for its next application of that kind.

  • Can I see one running before they are published?

    Yes. In a working session we build the closest pattern to your process in a Kinetic space with you.

See the pattern on your own process

Bring one process. In a free two-hour working session we build the closest pattern in a Kinetic space with you and show the definitions and API calls behind it.