> 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-counters-and-running-totals.md).

# Snippet - Counters & Running Totals

This snippet sample project demonstrates how to configure appRules Actions to generate and maintain counters and running totals without using scripts or code.  

The project uses a single ViewRuntimeValues activity accessing actions and conditions that have been defined for the demonstration. 

 

## **Actions**

9 Actions have been defined in the project:

## Conditions

2 Conditions have been defined in the project:

## ViewRuntimeValues Activity

17 Entries have been added in the ViewRuntimeValues activity used in the project:

**When the project is run the results are shownin the view activity**


---

# 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-counters-and-running-totals.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.