> For the complete documentation index, see [llms.txt](https://docs.appstrategy.com/apprules-r-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.appstrategy.com/apprules-r-documentation/platform/platform-features/creating-and-running-projects/designer/designer-concepts.md).

# Using the appRules Designer

To create your project, simply navigate to the appRules designer home page and  drag-and-drop activities from the toolbox on to the designer.  

{% hint style="info" %}
The user id to be used for accessing the designer must be set up as a developer in user settings
{% endhint %}

There are several sample projects in the Samples database that show examples of completed projects.

![](https://1923141441-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MFjmFrZ8sef1J7qkr6H%2F-MJaPTU_7Cu4g1fTx2K2%2F-MJafpgyV3bM9UaJRch5%2Fimage.png?alt=media\&token=18b5e493-47ea-460d-8625-63c8e517b3b7)

To configure an activity: 

* Drag-and-drop an activity on to the designer and the "Add New Activity" form will be displayed:                 ![](https://1923141441-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MFjmFrZ8sef1J7qkr6H%2Fuploads%2FJknt0bQUYBMApFwbFjVB%2Fimage.png?alt=media\&token=d8e525a4-0905-4763-9d97-aa9c24fa8304)
* Optionally edit the Display Name of the activity.
* Optionally enter a short description for the activity.
* Select the Execution Plan for the activity (Automatic, On-Demand, etc.)
* Configure the required properties using the many built-in property editors.
* Optionally configure the condition for executing the activity.
* Optionally configure the actions to execute based on execution events.
* Click the Save toolbar button to save the activity.  If no errors are found, the activity configuration will be saved.
* Once saved, you can connect the activity to another activity by dragging an arrow from one activity to another.

###


---

# 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.appstrategy.com/apprules-r-documentation/platform/platform-features/creating-and-running-projects/designer/designer-concepts.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.