We're reclaiming inactive PDIs to keep them available for active builders. Learn what's changing, who's affected, and how to protect your work. Read More

How to transfer variables from RITM to Remote Task Definition on Service Exchange (ServiceBridge)

JitendraC
Tera Contributor

When the Remote Task Definition (RTD) synchronizes the Provider RITM back to the Consumer instance, the catalog variables are not syncing back.

Task fields are syncing correctly, but variable values are not.

1 REPLY 1

Vikram Reddy
Tera Guru

Hi @JitendraC,

 

This is a known gap in how Remote Task Definitions work on Service Exchange: the RTD's inbound/outbound field mapping syncs sc_task-level fields between the paired Provider and Consumer records, but catalog variables live in sc_item_option, not as a mapped field, so they never ride along on their own.

// Advanced transform script on an inbound field of the Remote Task Definition
current.variables.your_target_variable = object_data.remote_task_vars.number50270d9ec31c8210075c35aa05013126;

You add each variable you need as its own inbound field on the RTD, then pull the value across with an advanced transform using the object_data.remote_task_vars object. The field name is auto generated per variable, you'll find the exact one on the Remote tasks variables related list of the RTD record. For a full variable set or an MRVS this gets tedious fast, at that point stop fighting the RTD and use a Remote Record Producer to order the item instead. If you're on Service Bridge v2.1 (Feb 2025), Consumer Variables for RRPs lets the consumer manage its own variables locally, but note those stay consumer-side only, they are never passed back to the provider.

References

 

Thank you,
Vikram Karety
Octigo Solutions INC