> For the complete documentation index, see [llms.txt](https://docs.rmhpos.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rmhpos.com/releases/old/3-11-0.md).

# 3.11.0

Release Date: July 4, 2022

## **Store Manager, POS, and POS Software Development Kit (SDK)**

* Program a chain of commands

Starting with release 3.11.0, when programming POS Task Pads or Custom Buttons you can program buttons to execute a series of commands when the button is clicked by adding a semicolon (;) between commands. For example, you might create a chain of commands to discount a transaction (command 1) and then automatically select a discount reason code (command 2). There is no limit to the number of commands in a chain. However, the commands should be chained together to follow a logical transaction process.

* Configure sequential tendering for POS (preview only)

Starting with release 3.11.0, there is a new POS Profile option "Enable sequential payment" to enable sequential tendering in POS. With sequential tendering, cashiers can process different payments (such as debit or credit card) one at a time before the transaction is completed in POS.

**Note:** Currently, there are no payment extensions that support sequential tendering, so you should NOT enable this option. Our independent software vendor (ISV) partners are currently in the process of developing sequential tendering capabilities in their payment extensions using the POS Software Development Kit (SDK) supplied in this release. We will publish the list of supported payment extensions once those become available.


---

# 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 dynamically by asking a question.

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

```
GET https://docs.rmhpos.com/releases/old/3-11-0.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.