> For the complete documentation index, see [llms.txt](https://docs.workflowgen.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.workflowgen.com/features/technical-components.md).

# Technical Components

## Workflow engine

#### The workflow engine comprises:

* A .NET web application for end-users (User Portal)<br>
* A .NET web application for administrators and process managers<br>
* An SQL relational database containing the process definition, request follow-up, and user management (which can be synchronized with existing directories)

## WorkflowGen database

#### The WorkflowGen database contains:

* User management<br>
* Process definition<br>
* Follow-up information about ongoing and closed processes, as well as significant workflow-related data (approvals, amounts, documents, etc.)<br>
* Files (such as PDF documents) are stored on the server and auto-archived in chronological order

## Applications

#### Applications used to implement actions:

* .NET web form management<br>
* Form data export to SQL database<br>
* Retrieve users from a directory to perform an action or for email notification<br>
* XML transformation (for EAI features)<br>
* RAISEEXCEPTION to cancel one or many actions<br>
* Launch a new request from within an ongoing request<br>
* Develop your own workflow applications with the WorkflowGen development kit<br>
* Reuse existing compatible web services<br>
* Dozens of ready-to-use applications with source code examples available in the WorkflowGen Resource Center

#### Node.js-based web applications

WorkflowGen also includes Node.js-based web applications for GraphQL, webhooks, SCIM, OpenID Connect Auth, and MCP Server features.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.workflowgen.com/features/technical-components.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.