Skip to main content

App Builder

App Builder lets you create business applications by describing what you want in plain language. The AI generates the frontend for you, drawing on the workflows and tables already set up in Vince Platform. No coding, no component-by-component assembly.

Who it's for​

App Builder is designed for several types of users:

AudienceHow they use it
Business usersCreate dashboards, portals, and trackers without development skills
Power usersBuild on top of existing workflows and data processes they already own
App administratorsManage versions, publish apps, and control who can access them
Domain specialistsTranslate supply chain or operations knowledge into self-service tools

Who does what​

The AI builds the app's screens. The data and business rules behind them come from workflows and tables, which someone has to set up first.

PartWho usually does it
Turning on App Builder for your companyVince
Workflows that read and update data in your systems, such as Infor M3Your integration team. Vince often builds the first ones together with you — see Built for customers to own
Tables that store the app's own dataYour integration team or the app builder
The app itself, built from promptsBusiness users and power users with Write access
Publishing the appApp owners with Deploy access
Giving people access to the appYour tenant administrator, through roles — see Security & Roles

App Builder saves the most time when the workflows and tables already exist. If they don't, building them comes first.

Key concepts​

TermWhat it means
AppThe user-facing business application — a dashboard, tracker, portal, or form
WorkflowA Vince Platform process that retrieves, transforms, or sends data
TableA structured data source with defined columns
ResourceA workflow or table connected to an app as its data source
AliasA plain-language name given to a resource for use in prompts
Build SessionThe active editing context — one user per app at a time
Tenant PromptOrganisation-wide standing instructions applied to every app build
InApp RoleAn app-specific access rule controlling what different users see or can do
EnvironmentA deployment context (dev, test, production)

Prerequisites​

Before you can build apps:

  • App Builder must be enabled for your tenant by Vince.
  • Your Vince Platform role must include App Builder: Write or Deploy permission — see Concepts & Architecture for permission levels.
  • The workflows and tables your app will use must already exist in Vince Platform.
tip

New workflows must be run at least once with realistic inputs before App Builder can use them, unless they were created with the M3 Workflow Builder. Tables are ready immediately. See Workflows — The 1-run requirement for details.

Video walkthrough​

Prefer to watch rather than read? This video walkthrough covers the same steps as the quickstart below: enabling App Builder, connecting a workflow, prompting a dashboard, and publishing it.

Quickstart: build your first app​

  1. Open App Builder from the Vince Platform navigation. You land on the App Library, which lists every app in your tenant.

    The App Library showing existing apps with their status, version, and creator

  2. Create a new app. Click + Create new app, give it a name and a short description, and select the LLM connection to use.

    Dialog for creating a new app with name, description, and connection fields

  3. Add a resource. Open the Resources panel and pick the workflow or table your app will use.

    Selecting a workflow to add as a resource

  4. Set an alias. Give the resource a short, descriptive name you can refer to in prompts (e.g. orders_table, invoice_workflow).

    Setting an alias for the selected resource

  5. Write your first prompt. Describe what you want in plain language — mention the resource alias, key fields, and layout, and keep the first prompt simple.

    Writing the first build prompt describing the app

  6. Review and iterate. The chat locks while App Builder generates a preview. Look at the result and refine it with focused follow-up prompts.

    Reviewing the generated preview and refining it with a follow-up prompt

  7. Save to lock in your progress and end the build session.

    Saving the app and ending the build session

  8. Publish to make a version the one end users run.

    Publishing the app so it becomes available to end users

  9. Run the app from the App Library, or share its link with your users.

    Running the published app

In this section​

Last updated on