Maintain Your Integration Architecture Designer Certification for Spring '19
After completing this unit, you’ll be able to:
- Describe key features available in Integration Architecture Design as of Spring ’19.
If you currently hold the Salesforce Integration Architecture Designer credential, you do not need to complete this module by the previously posted April 10th certification maintenance deadline. Instead, your Salesforce certification will automatically be maintained into the next release cycle.
There is no action required, and your certification will not expire. Your certification status will be updated by April 10, 2020. We'll send you an email confirmation to let you know when we've updated your status.
Of course, we know you want to keep your skills up to date and learn about the latest features. This module contains lots of great info about the latest release, which you can explore without worrying about deadlines. Salesforce introduced a number of great feature enhancements. Let’s take a look at some of the more important ones.
As of Spring ’19, you can automatically replace old data with new information for Lightning Data rules that update fields on your records via a lookup to a custom object.
Previously, when sales reps updated accounts, contacts, or leads, Lightning Data could only fill empty fields. It couldn’t update fields that already contained data, even if the data was out of date. Now, sales reps no longer have to click a link to see the latest data, such as head count, revenue, or contact information. With this automation, your sales team enjoys better segmentation, more comprehensive reporting, and easier task assignment.
Replacing old data automatically can be done in Setup by using the Quick Find box to find Data Integration Rules and open a rule that updates records. In the rule’s field mapping settings, select Update. On each field, select Overwrite or Keep. Before selecting Overwrite, enable history tracking for the field.
You can now use external data in flows and processes other than record change processes. This support expands your click-not-code toolbox, letting you build call scripts for support agents with Salesforce and external data, create automated emails incorporating external data, and more.
Another Spring ’19 update that applies to Integration Architecture is that an OAuth client, such as MuleSoft, can now send a request to the dynamic client registration endpoint to automatically register a new child OAuth 2.0 connected client app with Salesforce. With a successful registration, Salesforce returns a new client identifier and metadata about the newly registered child app.
The OAuth 2.0 connected app can check the current state of its access and refresh tokens and the OAuth client can check the current state of access and refresh tokens for itself and its child apps.
In addition, admins can authorize a single connected app to introspect all access and refresh tokens within the entire org.
After creating a connected app, generate an initial access token and configure your new endpoints. Make sure to register your initial access token and integrate your OAuth 2.0 endpoints with your OAuth 2.0 client, such as MuleSoft.
With Spring ’19, you can now receive near-real-time changes of Salesforce records, and synchronize to corresponding records in an external data store. This can be done with the Change Data Capture feature, which publishes change events that represent changes to Salesforce records. Changes include creating a record, updating a record, deleting a record, and undeleting a record. Change Data Capture was offered in the last release as a developer preview and a pilot, and we’ve made enhancements for this release.
As of Spring ’19, you can now use high-volume platform events to publish and process millions of events efficiently, receive notifications in real time, and use an event-driven programming model to automate your processes and integrate your apps with external business processes.
With high-volume platform events, your apps scale better than with standard-volume events, and you can retrieve retained event messages for up to 3 days. High-volume platform events are now the default event type for new event definitions.
High-volume platform events are published asynchronously so that the system can process high loads of events efficiently. The publishing call places the publish request in a queue. The event message might not be published immediately after the call returns, but it is published when system resources are available.