Skip to content
Docs

Start here

↑ ↓ navigate · Enter open · Esc closeSearch all 418 articles

Create your first app

Go from the template gallery to a running app and its first results.

Start with a template to learn the relationship between an app and the workflows behind it. Smart Demo is self-contained: it creates sample sales information, calculates regional results, and produces a narrative. Its data is illustrative.

Before you start

Sign in to your Strive workspace. You need permission to create and start apps, and enough available app capacity. The template's processing capabilities must be available in the workspace.

Create and run

  1. Open Apps, then New app.
  2. Choose Smart Demo. Read its description so you know what it will create.
  3. Enter a recognisable title, such as “Sales walkthrough”. Check the app identifier. A name is editable later; the identifier is its lasting address.
  4. Create the app. If the identifier is taken, use the suggested alternative or choose another one.
  5. Open the new app's Overview. Start or deploy it if it is not already running.
  6. Open the app and use its Run action. Wait for processing to finish before checking the metrics and narrative.

The app's interface and workflows are installed together. Creating the app does not prove that its first processing run has succeeded.

Inspect what happened

Open the app's Workflows section to inspect its process. Select the relevant run and read its step statuses and record counts. Open Data to inspect produced records. Follow a record back to its source when a result is surprising.

You can also ask the Assistant: “Explain the latest run of my Sales walkthrough app.” It can inspect the run and propose changes if a configuration needs attention.

Make the next example your own

Try Document Insights for files, Feedback Triage for pasted text, or Topic News for recurring collection. A file-based app needs files before it has results; a news app needs topics and a refresh.

If you cannot proceed

A rejected template dependency needs an administrator to make the required capability available. A start failure belongs to the app lifecycle; a failed processing step belongs to its workflow. Inspect the relevant error instead of repeatedly creating new copies. See app troubleshooting.