Service Bridge client scripts and variable sets

[sowmyaprabhakar]

Hello All,

While configuring service bridge, we face the below challenges.

Does the client script, variable sets and client callable script includes copy over to the consumer instance ? We don't see them flowing through. 

Are there any documentation around, list of tables config that gets copied over to the remote record producer.

Additionally, can we limit any variables and its data specific to the consumer. Remote choice definition will help with limiting the data I believe. Can the variable itself be limited.

Has anyone faced/ resolved these issues. Appreciate any inputs on these.

Thank you

[Ryan Palamara]

Scripts do not get carried over to consumer instance and is intended for security reasons. Catalog UI Policies can be used and will be replicated to the consumer instance. With the February release of Service Bridge (v1.1.0) variable support set was added (docs site page HERE).

In the docs site there is a data model for both the provider and consumer (HERE). I will check if there is a more detailed model that we can share. 

There is no function to limit which variables are sent to a specific customer, but you could use UI Policies to hide variables in consumer instances. As you mentioned Remote Choice can be used to limit the selectable data within a variable and you can also make them dependent on another variable. 

[MattCD]

@Ryan Palamara Can you confirm that UI Policies are supported on variable sets in the latest release?

I've run into an odd issue where when I add a UI policy to a variable set and then publish it, all works well on the customer instance. However, at 4am when the Scheduled job = "Trigger Daily Refresh All Entitlements" runs on the provider, it deletes the UI Policies from all remote catalog variable sets and triggers an error on the client side logs indicating a unique constraint when trying to INSERT INTO sys_metadata_customization table. This happens on multiple consumer instances.

[MattCD]

If it helps anyone else out; The issue was domain separation related. If the UI policy has a domain set in the sys_domain field, the refresh job doesn't work properly and deletes it from the consumer instance.