Universal containers houses their order information in their legacy backend systems. Customers need to see their orders from the back office in their customer-facing Community. – The existing Salesforce org (which hosts the community) has integration with the backend legacy system using Salesforce Connect – Customer users only need to see their orders in the Community – Orders are currently public read-only – Customer users need to access fields that are already part of the existing integration What two things should do Salesforce Admin do to meet these requirements? Choose 2 answers

Universal containers houses their order information in their legacy backend systems. Customers need to see their orders from the back office in their customer-facing Community. – The existing Salesforce org (which hosts the community) has integration with the backend legacy system using Salesforce Connect – Customer users only need to see their orders in the Community – Orders are currently public read-only – Customer users need to access fields that are already part of the existing integration What two things should do Salesforce Admin do to meet these requirements? Choose 2 answers
A . Leveraging existing integration with the legacy system
B . Set the external users’ organisation wide defaults to private for external order objects
C . Creating a new integration with the legacy system for customer users
D . Update the customer user profile and given the "view all" permission on the integration object

Answer: A,D

Latest CRT-271 Dumps Valid Version with 293 Q&As

Latest And Valid Q&A | Instant Download | Once Fail, Full Refund

Subscribe
Notify of
guest
0 Comments
Inline Feedbacks
View all comments