Replacement of deprecated Nodes

This article lists deprecated Nodes along with the appropriate Node they should be replaced with.

In order to move to the 2023 Refresh, all deprecated Nodes must be updated as described here.

Statistic

Replace with Set Key-Value. Log a service ticket for us to assist with migrating the backing data.

Query Statistic

Replace with Get Key-Value. Log a service ticket for us to assist with migrating the backing data.

Once this migration has been performed, replace with Get Key Value 2.

Bulk Statistic

Replace with Set Key-Values. Log a service ticket for us to assist with migrating the backing data.

Cacher

This Node does not have a direct replacement. In many cases it was unintentionally used to permanently store data that was only needed within the context of a Workflow invoke.

If you need to store the data permanently, consider replacing it with Set Key-Value.

If you only need to access data within the context of the Workflow invoke, use String Builder.

Reducer

Replace with Reduce. Log a service ticket for us to assist with migrating the backing data.

Set Key-Value, Set Key-Values, Get Key-Value, Get Key-Values

These Nodes must all be replaced with their equivalents for the 2023 Refresh:

• Set Key-Value 2
• Set Key-Values 2
• Get Key-Value 2
• Get Key-Values 2

Note that if you are migrating from the deprecated Statistic Nodes, you first need to move to the first generation equivalent Key-Value Node, then to replacement Key-Value Node.

Log a service ticket for us to assist with migrating the backing data.

Reduce

Replace with Reduce 2.

Log a service ticket for us to assist with migrating the backing data.

SOAP Request

Replace with SOAP Request 2 when moving to 2023 Refresh as SOAP Request is no longer supported.

JSON Request

Replace with Web Request or Web Request 2 when moving to 2023 Refresh or after being moved as JSON Request is no longer supported.