How Data cloud works?

 

• Connect all your data sources whether batch or streaming data.
• Prepare your data through transformation and data governance features.
• Harmonize your data to a standard data model.
• Unify data with identity resolution rulesets.
• Query and analyze data using insights.
• Use AI to predict behavior.
• Segment your data and activate to use in various channels to create personalized experiences.
• Analyze your data using supported analytic tools.
• Output data to multiple sources to act on data based on your business needs.
• Continue to review, measure, and optimize data.

Einstein Trust Layer

 Interacting with generative AI is a simple as sending a prompt to a large language model and getting a response.

Salesforce Introduced Einstein trust layer as part of the Einstein 1 Platform.

The trust layer is a secure intermediary for user interactions with LLM’s. Masking PII checking output toxicity etc.

Every prompt that runs through the trust layer starts out in the Einstein 1 platform and usually originates from one of our CRM applications.

Once the prompt hits the trust layer it goes through a multi-step process to ensure that the response is generated and sent back to the user.

1. Secure Data Retrieval

   If the prompt uses merge fields to pull in record data for example from a contact. It pulls that record data from the page context in one instance or if that prompt starts out on the server it pulls via SOQL.

      2. Dynamic Grounding 

Dynamic grounding is able to bring business logic into the transaction itself.

Ex : 

If that prompt requires you to go out and pull data from flow or from data cloud you can bring in that additional context into to enrich the prompt and further grounded in detail so that it’s more knowledgeable about the case at hand .

   3. Data Masking

To prevent sharing PII we use data masking a detection tool identify sensitive data like government IDs replacing them with placeholders like Person_0,Person_1 etc.

Trust layer maintains this placeholder origin mapping for you.

Once masking is completed we apply additional ‘prompt Defense’ 

  4. Prompt Defense

Ensuring that model responses remain reliable and avoid misleading outputs.

Once prompt is secured it then proceeds to the LLM  Gateway.

LMM Gateway :

This manages connections with various model providers and on reaching out to the gateway the prompt roots to the necessary model.

If sent to external models like Open AI the data is encrypted and never stored externally.

  5. Zero Retention :

Open AI is our first LLM partner operates a zero retention basis for prompts.

They also have a Content moderation API that flags unusual or harmful content and alerts salesforce of this immediately.

Once the response has been generated from the LLM gateway it’s ready to present back to the user.

But first we want to take that response and ensure that it’s safe with the first step of the after generation process and that is toxicity detection .

  6.Toxicity Detection :

We are going to take that response and run it through our toxicity filter to ensure that there is no harmful content any negative language and make sure that it’s safe and secure for your users.

  7.Data Demasking :

We are going to take all of the data that was masked in the original step through the masking process and we’re going to rehydrate that through demasking so that all of the data like the name , first name and addresses are all put back into the response and then it’s ready to be presented back to the user.

8.Feedback Framework

We have feedback framework in place with api’s so that you can provide feedback to the generation so whether or not it was useful or not whether or not it was successful is all logged and will be used for us to retrain the models and ensure that we’re providing the responses that you need.

9.Audit Trail 

We allow you to store the prompt any actions that were taken the toxicity so that you can provide trusted generative AI at scale.

This is just the first step towards creating the trust between yourself your company and generative AI.

Understanding 4 Waves of AI

 1.Predictive AI

2.Generative AI

3.Autonomous AI

4.Artificial General Intelligence

1.Predictive AI :

Uses historical data to forecast future events.

Predictive AI  generic use cases

Data analytics, Stock market predictions, Weather forecasting etc

Ex : Einstein Lead Scoring

Automatically scores and prioritises leads based on their likelihood to convert.

Ex : Einstein Opportunity Insights

Predicts the likelihood of an opportunity closing Successfully, providing real-time insights.

Ex: Einstein Prediction Builder

Allows the creation of custom AI models to predict business-specific outcomes like churn.

Ex: Einstein Vision 

Can analyse images for predictive maintenance, such as when machinery parts may fail.

Note : Predictive AI is specialised in forecasting based on existing data.

2.Generative AI :

Creates new data that resembles a given dataset.

Generative AI generic Use cases

Tech behind deep fakes, chatbots , MidJourney, Call-e,Stable Diffusion,ChatGPT etc.

Generative AI Salesforce Use cases 

Einstein Copilot :

A conversational assistant that can generate responses and prompts.

Einstein for Developers :

Can generate Apex code using natural language, aiding in rapid development.

Einstein Email Insights :

Generates suggested follow-ups or actions based on the content of emails.

DataWeave Codegen :

A generative AI tool that simplifies the use of MuleSoft’s DataWeave language by generating DataWeave scripts from sample input and output data.

Note : Generative AI is focused on creating new , similar data.

3.Autonomous AI :

Can make decisions and perform tasks without human intervention.

Autonomous AI generic use cases 

Self-driving cars and drones are prime examples.

Autonomous AI salesforce use cases

Einstein Bots :

Automates routine customer service tasks by handling inquiries without human intervention.

Einstein Case Classification :

Automatically categorises and routes customer service cases to the right agents.

Einstein Automated Contacts :

Uses email and event activity to fine new contacts and opportunity contact roles.

Note : Autonomous AI is all about making decisions and acting without human intervention.

1. Artificial general intelligence (AGI)

Machines that possess the ability to understand , learn , and apply to knowledge across different domains, much like a human.

AGI is still very far away and will need significant breakthroughs in AI research before it can be achieved.

Note : Artificial General Intelligence aims to be as versatile and capable as humans in multiple domains.

“Custom Error” in Record-Triggered Flow

 As part of Winter 24 release, Salesforce released this much-awaited flow feature by which we can fire custom error messages to users as part of record-triggered flows. This feature is available as part of both before and after save record triggered flows.

We can add error messages to a specific field or at the page level.

Advantages

1. Earlier when we wanted to add complex validations to a record save operation, Apex trigger was the only option if it cannot be achieved using a validation rule. Now we can implement this using a flow also.

2. On unexpected exceptions from flow it was showing system error messages always. Now we can replace that with custom messages.

Selective Sandbox Access

 With Selective Sandbox Access, you can limit access to a sandbox to only the required users during the refreshing or creation process.

No more worrying about unauthorized users accessing sensitive sandbox data!

By default, all active users in the source org have access to the sandbox.

However, now you have the power to grant access to specific users through a public group.

This means you can choose who gets access and maintain control over your sandboxes.

One fantastic benefit of Selective Sandbox Access is that the email addresses for the users included in the public group will remain in their original format.

No need to modify or append ".invalid" to their email addresses.

This makes the process streamlined and hassle-free.

But what about users who are not part of the public group?

Well, they can still gain access, but there's an additional step.

They will need to be unfrozen in the sandbox. This ensures that only authorized users can access the sandbox and guarantees a secure environment for your testing and development needs.

Selective Sandbox Access will be available in production orgs starting mid-October 2023 with the Winter '24 release.

If you have the Manage Sandbox user permission, you'll have the opportunity to leverage this feature.

Note :

With selective sandbox access, grant access only to required users. It also removes the additional step for a Salesforce admin to change the user email address back to the original format. If you don’t want to match the access currently defined in the source org, you can create a public group to grant access to a subset of users.

If you don’t see the option “Sandbox Access User Group”, while creating the sandbox in your production org, please log a case with Salesforce.

DataRaptors in OmniStudio

 A DataRaptor is a mapping tool that enables you to read, transform and write Salesforce data.

DataRaptors supply data to OmniScripts and OmniStudio FlexCards from Salesforce, and write updates from OmniScripts and Flexcards back to Salesforce.

Types of DataRaptors :

1.Turbo Extract  : Get data from a single Salesforce object (sObject).

2.Extract : Gets data from one or more Salesforce sObjects.

3.Load : Saves data to one or more Salesforce sObjects by 

—>Updating Salesforce records

—>Creating Salesforce records

—>Migrating CSV data into Salesforce records.

4.Transform : Manipulates any data that comes from inside or outside Salesforce.

Data Raptor Designer :

Extract tab

Formulas tab

Output tab

Options tab

Preview tab

Note : Tabs are subject to data raptor type.

In the DataRaptor designer (Extract) , we get the above tabs to work with.Some of these tabs are common in all the DataRaptors.

Salesforce Integrations

 

Salesforce Integration Levels 

1.UI Integration

2.Process Integration

3.Data Integration

UI Integrations :

        1.Force.com Canvas SDK

        2.LWC/Aura + Apex Callout

        3.Javascript Fetch API

Process Integration:

  1.Platform Events

  2.Salesforce REST API

  3.Apex SOAP service

  4.Trigger+ Apex Callout

  5.Enhanced External Service

  6.Salesforce SOAP API

  7.APEX REST Service

  8.APEX Email Service

Data Integration :

  

1.Salesforce Connect

2.Change Data capture

3.Bulk API 2.0