> 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/samples/sample-projects/snippets/snippet-arguments-variables-dynamic-values-and-sourced-values.md).

# Snippet - Arguments, Variables, Dynamic Values & Sourced Values

The Snippet – Arguments, Variables, Dynamic Values & Sourced Values project demonstrates how to define arguments, variables, dynamic values and shows how to use appRules Sourced Values to set these values.

## Arguments

Arguments are defined in the Arguments tab of the Project Details form as show below.       

{% hint style="info" %}
Note that the values shown are defaults.  They can be changed by passing different values when you run the project.
{% endhint %}

## Variables

 Variables are defined in the Variables tab of the Project Details form as show below.

## Sourced Values

Sourced Values are used when getting and setting values in appRules.  appRules includes several built-in value sources and editors are displayed at design time based on the Source(type) of the data.  In this sample project, you will explore several editors displayed when setting the values.

Two activities are used in this project to set and display values.

## **SetValues Activity**

This activity from the Base module is used for setting the values.

The Values property is a collection for setting values.

 

## **ViewRuntimeValues Activity**

This activity from the Dialogs module is used to display the values. When the project is run, the following form is displayed.


---

# 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/samples/sample-projects/snippets/snippet-arguments-variables-dynamic-values-and-sourced-values.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.