# New & enhanced nodes

## New Switch Case node

The [Switch Case](https://clickatell.gitbook.io/flow/action-nodes/action-nodes-switch-case) node is an action node (i.e., not user-facing) that routes a user to a specific step based on a flow variable's value. It is similar to a [Menu node](https://clickatell.gitbook.io/flow/user-facing-nodes/branch-logic-split/menu-nodes-menu-with-options), but instead of relying on the end-user's input to decide which route to take, this node relies on the value of a certain flow variable.

{% hint style="info" %}
[Find out more](https://clickatell.gitbook.io/flow/action-nodes/action-nodes-switch-case) about the Switch Case node and how to set it up.
{% endhint %}

<figure><img src="/files/LgNSOR8XyLzb5jpO1GeA" alt="" width="236"><figcaption><p>A new action node - the Switch Case node.</p></figcaption></figure>

<figure><img src="/files/L0ELpSdREeT8qacLK4FY" alt=""><figcaption><p>Setup of the Switch Case node.</p></figcaption></figure>

## Enhanced Chat 2 Pay node

We've made several enhancements to the [Chat 2 Pay node](https://clickatell.gitbook.io/flow/user-facing-nodes/commerce/chat-2-pay).

Flow-builders now have the option to either let Chat Flow **generate an order number automatically** or they can **generate a custom order number** specific to your business based on an API call. Auto-generated order numbers are available as variables to be used in the workflow.

We've also included the ability for flow-builders to add any **additional data** to payment requests. This gets passed to the payment provider and can be used to match on their backend system (in case of incomplete transactions). These key:value pair fields support variables.

<figure><img src="/files/gGwGPisPPlgmiwumq4SB" alt=""><figcaption><p>Enhanced Chat 2 Pay node</p></figcaption></figure>

## Dynamic List pagination

{% hint style="info" %}
[Find out more](https://clickatell.gitbook.io/flow/user-facing-nodes/branch-logic-split/menu-nodes-dynamic-list) about how to set up pagination on this node.
{% endhint %}

Previously, when using the [Dynamic List node](https://clickatell.gitbook.io/flow/user-facing-nodes/branch-logic-split/menu-nodes-dynamic-list) to present an option list that exceeded 10 items to your end-users, it was automatically rendered as a text menu as shown below.&#x20;

<figure><img src="/files/oUTXHsptqavX5WVuCjlg" alt="" width="270"><figcaption><p>Example of an unpaginated Dynamic List in WhatsApp</p></figcaption></figure>

We now support the ability to paginate dynamic lists instead of reverting to a text menu. If enabled for the node (default), the list above will now render as shown below.

{% hint style="info" %}
Note that pagination, even if enabled, will only come into effect for lists of more than 10 items.
{% endhint %}

<figure><img src="/files/jN0xExcCi0asnOc2OAMa" alt=""><figcaption><p>Example of a paginated Dynamic List node on WhatsApp</p></figcaption></figure>

<figure><img src="/files/8IxqLTbLubPeXpO15Cao" alt=""><figcaption><p>Example of a paginated Dynamic List node on USSD. The SMS channel will have a similar experience.</p></figcaption></figure>


---

# Agent Instructions: 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:

```
GET https://guides.clickatell.com/release-notes/release-notes-archive/2023-release-notes/q3-2023/automated-messaging/new-and-enhanced-nodes.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.