# Development Workflow

## Assumptions

* Assumes that you have requirements, specifications, and design documents of your application available (informal or formal).
* Assumes that you have access to Trillo Workbench UI. 
* Access to an IDE or code editor will be very useful. You need an IDE for debugging by stepping through the source code.

## Steps

* **Data Model**
  * Use the default database of Trillo Workbench. Or add a database that is accessible by the workbench (more about it later).
  * Add tables and/or introspect tables from an existing database.
  * Edit tables and attribute metadata.
* **Domain Metadata**
  * Specify domain metadata file as JSON - these are JSON files that contain configuration or metadata used in a function later.
* **Settings**
  * Add external API credentials, external authentication systems specs., public key of private/public key pairs.
  * Link GitHub account (done by admin once).
* **Functions**
  * Write a function/business logic code using the Trillo Workbench editor or an IDE.
  * Debug code using an IDE.
* **Workflows**
  * Workflows are functions. 
  * They are mentioned briefly to emphasize that they can run as a background task with their own logs accessible from history.
  * Workflows can be scheduled.
* **Access Control**
  * Developers can add or update the user roles list.
  * The actual access control rules are specified by the application users and covered in the Role-Based Access Control Chapter.

<figure><img src="/files/N6rJLMdsQl1FfUa1Rb8c" alt=""><figcaption><p>A typical workflow of building an application using Trillo Workbench</p></figcaption></figure>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://trillo.gitbook.io/trillo-workbench/trillo-workbench-development-workflow.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.