Service Bridge Instance Promotion Best Practices prior to August'24 Store ReleaseThis knowledge article highlights the best practice for promoting development of Service Bridge elements through an instance stack of Development, Test/UAT, and Production instances. It is divided into two sections which highlight actions taken in the Provider instance and actions taken in the consumer instance. Note: This article applies to Service Bridge for Providers v1 and Service Bridge for Consumers v1 apps which were released in November 2023. Instance Configuration Provider instances update set migration is Development, Test/UAT, and Production. Consumer instances update set migration is Development, Test/UAT, and Production. Provider Test/UAT instance is connected to Consumer Development instance and Consumer Test/UAT instance. Two different companies/accounts are used to connect to the Consumer Development and Consumer Test/UAT instance because a connection requires a unique company/account. Provider Production instance is connected to Consumer Production instance. Provider Instances Consumer Connections[sn_sb_pro_consumer_connection], RPS Connections[sn_sb_rps_connection], and Connection Settings[sn_sb_pro_service_bridge_settings] Consumer connections, RPS connections, and connection settings should not be captured in update sets or migrated between instances.Consumer connections, RPS connections, and connection settings are specific to each pair of instance and will need to be established between each pair of instances. Entitlements[sn_sb_pro_entitlement] and Authorized Users[sn_sb_pro_authorized_user] Entitlements and authorized users should not be captured in update sets or migrated between instances.Entitlements and authorized users are published from Provider instance to Consumer instance via Service Bridge connection. Remote Record Producers(RRPs)[sn_sb_pro_remote_record_producer] - This is applicable for both new RRPs and updated elements of the RRPs. If Remote Choice and/or Personas are being used, ensure that this is migrated either in the same update set as the RRP or prior to the update set containing the associated RRP.For Remote Record Producers, capture the following in the same update set Remote Record Producer (RRP)RRP VariablesConsumer CriteriaAssociated custom flows/scripts Remote Task Definitions(RTDs)[sn_sb_pro_remote_task_def] - This is applicable for both new RTDs and updated elements of RTDs.For Remote Task Definitions, capture the following in the same update set Remote Task Definition (RTD)Field mappingsTransformsConsumer CriteriaAssociated custom flows/scripts Customer Conditions[sn_req_criteria_customer_condition] Customer Condition(s) should be migrated in an update set prior to migrating the Consumer Criteria that they will be used in.If there are Customer Conditions that have filtering based on a specific record, the record will need to have the same SysID across the instances, or it will need to be manually updated after moving update sets. For example, if you create a Customer Condition filtering on a Sold Product of a specific model, that model will need to have the same SysID across the instances. If it does not, the condition will need to be manually updated on the destination instance. Consumer Criteria[sn_sb_pro_remote_record_producer_consumer_criteria] and [sn_sb_pro_remote_task_def_consumer_criteria] Consumer Criteria(s) should be captured in the same update set as the RRP or RTD.Consumer Criteria is a M2M record from an RRP or RTD to a Customer Condition. Personas[sn_sb_pro_persona] New Personas should be captured in the same update set as the RRP they are associated with or captured and migrated in an update set prior to the update set containing the RRP the persona is associated with.Personas can be associated with many RRPs. Existing Personas which have been migrated do not have to be captured in an update set and migrated unless the existing Persona has been modified. Transforms[sn_sb_pro_transform] New Transforms should be captured in the same update set as the RTD they are associated with or captured and migrated in an update set prior to the update set containing the RTD the transform is associated with. Transforms should be captured after they have been activated.Transforms can be associated with many RTDs. Existing Transforms which have been migrated do not have to be captured in an update set and migrated unless the existing Transform has been modified. Consumer Instances Provider Connections[sn_sb_con_provider_connection], RPS Connections[sn_sb_rps_connection], and Connection Settings[sn_sb_con_service_bridge_settings] Provider connections, RPS connections, and connection settings should not be captured in update sets or migrated between instances.Provider connections, RPS connections, and connection settings are specific to each pair of instance and will need to be established between each pair of instances. Entitlements[sn_sb_con_entitlement] and Authorized Users[sn_sb_con_authorized_user] Entitlements and authorized users should not be captured in update sets or migrated between instances.Entitlements and authorized users are published from Provider instance to Consumer instance via Service Bridge connection. Remote Record Producers(RRPs) [sn_sb_con_remote_record_producer] Do not capture RRPs in update sets or migrate RRPs between instances.RRPs are published from Provider instance to Consumer instance via Service Bridge.When RRPs are published from the provider, they have different SysIDs in the Consumer instance from the Provider instance. If there are changes made to the RRPs, such as associated Catalog or Categories, these will need to be updated manually in each respective instance. Remote Task Definitions(RTDs) [sn_sb_con_remote_task_def] RTDs are published from Provider instance to Consumer instance and have same SysID.Modifications to an RTD can be captured in an update set in the Consumer Development instance.After an RTD is published from a Provider instance to a connected Consumer instance, the update set which captured modifications made in the Consumer Development instance to the RTD can be applied to the Consumer instance.This is applicable for both new RTDs and updated elements of RTDs.For Remote Task Definitions, capture the following in the same update set TransformsField mappingsAssociated customs flows/scripts Personas[sn_sb_con_persona] - Personas cannot be modified and should not be captured in update sets.Transforms[sn_sb_con_transform] New Transforms should be migrated either in the same update set as the RTD or prior to the update set containing the associated RTD. Transforms should be captured after they have been activated.Transforms can be associated with many RTDs. Existing Transforms which have been migrated do not have to be captured in an update set and migrated unless the existing Transform has been modified.