Strategy Designer - Tools & Artifacts (23%)

Heroku Connect Benefit

A subset of Salesforce data is quickly and easily accessible to an app on Heroku. As an app developer, you simply write standard SQL for queries as you normally would. This along with Postgress provide a low-latency and high-throughput access to Salesforce data.

Market Development Funds (MDFs)

These are discretionary marketing dollars given to partners to help generate future sales (lead generation), typically associated with a marketing budget/plan. They can be allocated in real time or in advance of the marketing campaigns.

Leading Metrics

These are metrics that show activity and engagement, all pointing to eventual revenue.

AppExchange Components

These are modular building blocks that can be used to build other solutions, such as apps and Bolt solutions - no coding required. They allow you to add functionality without having to develop it on your own.

Heroku External Objects

These provide a OData wrapper for the Heroku Postgres database that Heroku Connect maintains a connection for. This feature allows other web services to retrieve data from within the specified Heroku Postgres database using RESTful endpoints generated by the wrapper.

Salesforce REST APIs

These provide apps on Heroku access to Salesforce data through simple JSON-formatted HTTP requests. You can use this integration for data proxies and custom user interfaces.

Omni-Channel

This allows your customers to connect seamlessly with your support staff using multiple channels. At the same time, your support agents have immediate access to a holistic picture of the person they're about to help.

Salesforce Connect

This can be used as a data proxy to pull OData or other data sources into Salesforce on demand. No data is copied to the Salesforce database. You can run endpoints that expose OData 2.0 on Heroku or as provided by external systems.

AppExchange Apps

This is a ready-to-install collection of items that work together to serve a particular function. Developers combine custom objects, applications, tabs, components, and more into a single package.

Task Definition

This is a record that holds information such as name, description, category, and type of task.

AppExchange Lightning Data

This is a special type of app. It connects your Salesforce org to a data feed and automatically enriches your CRM data.

Planograms

This is a visual merchandising mechanism. It shows exactly where specific products are placed at the primary display locations such as refrigerators and shelves.

Retail Execution

This is about creating the perfect in-store experience with optimum product placement to create the perfect shelf.

Research Map

This is based on data gathered specifically for building the map. This approach is best when there are time and resources dedicated to creating a research plan. While this method creates the best maps, it takes time and significant buy-in. Regardless of where you start, your maps should be iterative and constantly updated with new findings.

Docked Prompts

This is great when users need to refer to content while exploring a feature on their own. This stays in place while the user navigates through the app.

Experienced Page Time (EPT)

This is how Salesforce measures the time it takes to download and display the entire content of a webpage in a browser window.

The Internet of Things (IoT)

This is one of the fastest growing and broadly applicable technologies shaping society. It refers to the full range of largely unattended devices that have their own connection to the internet for application-specific purposes.

Event Monitoring

This is part of Salesforce Shield and provides access to detailed performance, security, and usage data on all your Salesforce apps.

Integration Methods

- Heroku Connect - Salesforce Connect - Salesforce REST APIs - Callouts - Canvas

Consumer Goods Cloud Benefits

- Access comprehensive data on accounts with information on shipping and billing details, orders, promotions, and product assortments. - Use location details such as map coordinates, driving directions, addresses, and Salesforce Maps to create an optimized route for field reps to prioritize their visits. - Use platform features such as the Lightning App Builder and Flows to extend the capabilities of page customization, triggering automated tasks, and more. - Optimize action plans, sales agreements, and order management to expand business possibilities. - Gather metrics for specific stores, store groups, and in-store locations for products, product categories, and assortments to analyze the health of the stores and check compliance for products, promotions, and planograms. - Monitor key processes such as inventory audits, planogram compliance, return order processing, promotion checks, and in-store surveys with predefined templates. - Use Einstein object Detection to audit shelves, measure share and shelf, manage stock, and optimize product mix and sales. - Use a variety of data types such as number, Boolean, decimal, percent, date-time, text, and more to gather information on sales, effectiveness, and availability of products. - See advanced CRM Analytics dashboards to experience insights like never before, to drill into aspects of store performance, rep performance, product analysis, and more.

Retail Execution Mobile App Feature

- Ad-hoc visits - Mandatory tasks - Special instructions - Previous visit details - Scan, search, and filter - Add products to the shopping cart - Review collateral, take photos, and write notes

Partner Goal-Setting Considerations

- Adjust your channel's overall sales capacity to reflect their capacity for selling your solution. Your partners will not be 100% dedicated to selling your product, so adjust accordingly. - Consider if and by how much you need to adjust your sales yield expectations. How could margins change when you sell through the channel? Is the product mix different? Are add-ons less prevalent? - Make an objective estimate of your company's overall sales maturity. How predictable is your sales process? Do you offer a complete solution? These factors can influence partner success.

Integration Initiative Categories

- Application Integration - Data Integration - Process Integration

AppExchange Options

- Apps - Components - Bolt Solutions - Lightning Data - Flow Solutions - Consultants

Deal Registration Best Practices

- Communicate clear and fair rules of engagement. Strive for transparency and provide visibility into the process (criteria, eligibility, reward structure). Collaborate with partners and keep them updated on the deal status. - Create an efficient process with workflows and fast approvals. Make it easy to register deals with minimal fields. Automate the approval workflow and use system notifications for fast turnaround. - Establish service level agreements (SLAs). Set expectations for how you will support your partners throughout the process and communicate what is expected of them.

API-Led Connectivity Key Attributes

- Connectivity-in-context - Repeatable - Purpose-built - Scalable - Reciprocal

Channel Lead Distribution Best Practices

- Create a strategy and plan. Be sure to define criteria to assign leads to the right partners. Then decide on the lead stages you want to track and measure and be sure to use assignment rules to automate the process. - Support your partners throughout the process. Provide the resources, tools, and support along the way, and be sure to follow up. Channel managers should report regularly on pipeline and lead activity. - Create a service level agreement (SLA) to encourage activity. SLAs help you structure objectives, responsibilities, and performance measures for this program. Marketing agrees to deliver a fixed number of qualified leads and partners agree to respond to each lead based on the SLA, which should include the timing, persistence, messaging, and measured progress applied to distributed leads.

Experience Cloud Benefits

- Create multiple experiences for specific needs. - Extend business processes to partners and customers. - Integrate data (such as orders or financial information) from third-party providers. - Use themes and templates to create beautiful branded experiences. - Use Salesforce CMS to create content and deliver to any channel.

Reasons to Integrate Heroku Apps with Salesforce

- Data replication - Data proxies - Custom user interfaces - External processes

Internal Reporting Plan Process

- Develop a plan to deliver regular reports to key internal stakeholders. Don't overdo it with data. Share anecdotal information (stories and even excerpts of content from the portal), as well. - Organize metrics in a manner that makes it easy to understand (align to KPIs/business goals). - Set up your own partner scorecard. - Tie data to use cases where possible (deal registration, lead distribution, MDF, training onboarding).

AppExchange Solution Qualities

- Easy to install - Seamless to set up - Peer reviewed - Test for security

Four Types of Mapping

- Empathy Mapping - Customer Journey Mapping - Experience Mapping - Service Blueprinting

Methods to Add EPT Counter in LEX

- Enable Lightning Component Debug Mode from Setup. - Add the following string to the end of your Lightning Experience URL: ?eptVisible=1.

MDF Program Best Practices

- Have an internal process defined with clear stakeholders. - Allocate MDF funds strategically (new product launch, new market, etc.). - Prioritize on the partners potential and ability to execute. - Identify programs and which partner segments are the most successful. - Incent your partners to participate. - Provide pre-packaged Marketing Campaigns. - Track and monitor the performance and impact.

Three Pillars of Channel Strategy

- Executive Sponsorship - Executives need to be involved and support this program on an ongoing basis. - Invest in People - Have the right personnel to manage your channel (sales, marketing, support). - Invest in Technology - Have a robust portal (such as Sales Cloud PRM) to manage your partner network and bring value to all involved.

AppExchange Solution Benefits

- Extend Salesforce functionality - Can be distributed to others - Run on the Salesforce platform - Accelerate solution development

Partner Channel Strategy Best Practices

- Find the right match. Spend the time to vet, qualify, and get to know partners (quality over quantity). - Enablement/training is evergreen. Develop comprehensive training programs, make sure they are fully certified and know your products, and always be ready to answer their questions. - Have clear (easy to understand) policies and guidelines. Ambiguity can cause problems, so be sure to have a good set of guidelines that cover all aspects of your partner program. - Give them an opportunity to grow. Get to know their business goals. Are they looking to focus on a few vendors/ How will you support their business objectives? - The relationship must go beyond transactional. Partners are an extension of your business, they represent your brand and they are taking on risk by partnering with you over someone else. Make sure your partner program focuses on relationship-building.

Deal Registration Benefits

- Gives partners the ability to register their own deals. - Gives partners confidence to know that they are working on the right deals and provides them the exclusivity to work on the deal for a predefined period of time, once you have reviewed and approved it. - This can increase partner participation, driving higher adoption of your portal. - This has been show to increase the likelihood of lead conversion, and with a higher close rate, it makes forecasting that much better.

Six Predefined Assessment Task Definition Types

- Inventory Check - Promotion Check - In-store Survey - Planogram Check - Order Creation Other

Experience Map Characteristics

- It is not tied to a specific product or service. - It is split into 4 swim lanes: phases, actions, thought, mindsets/emotions. - It offers a general human perspective; it is not specific to a particular user type or product/service. - It depicts events in chronological order.

Service Blueprint Characteristics

- It is tied to a specific service. - It is split into 4 swim lanes: customer actions, frontstage actions, backstage actions, and support processes. - It reflects the organization's perspective focusing on the service provider and employees while leaving out most customer details. - It is chronological and hierarchical.

Four Dimensions of the Layer Approach

- Layers: The different types of tasks in a system. - Volume: The amount of data synched and the transformation activity between systems. - Timing: Communication timing is either asynchronous or synchronous, where data flows between systems in real time (or as soon as possible) or is batched up for later delivery. - Direction: The source direction, which can be from Salesforce to another system, from another system to Salesforce, or bidirectional.

Methods to Measure EPT in Salesforce

- Lightning Experience: Add an EPT counter to Lightning Experience. - Lightning Usage App: View aggregated page and browser performance. - Custom Reports: Build custom reports using Lightning Usage App objects. - Event Monitoring: Use event types to monitor performance.

Main Factors That Adversely Affect EPT

- Network: Conditions and "distance" between the device and the host instance. - Device: Available processing power, memory, and resources of your devices. - Browser: Specific browser processing capabilities and configuration. - Salesforce Configuration: Lightning page customization, Visualforce implementations, or specific org customizations.

Partner Portal Use Cases

- Partner Recruitment and Onboarding - Partner Enablement/Training - Lead Distribution/Deal Registration - Marketing Support - Support and Service

Product/Services Channel Strategy Considerations

- Partner expertise (what can the bring to the table?) - New product launch (is there an opportunity to use the channel strategically as part of a product launch?) - Exclusivity (will this product only be available through your partner network?) - How will these decisions impact your partners? Will it make them more successful?

Channel Partner Types

- Partners for Sales Reach - Partners for Delivery and Implementation - Partners for Solutions, Support and Maintenance

Retail Execution Activity Types

- Presales activities - Merchandising activities

System to Salesforce Integration Patterns

- Remote Call-In - Batch Data Synchronization

Asynchronous Integration Patterns

- Remote Process Invocation: Fire and Forget - Remote Call-In (based on implementation solution) - Batch Data Synchronization - Publish/Subscribe

Synchronous Integration Patterns

- Remote Process Invocation: Request and Reply - Data Virtualization - Remote Call-In (based on implementation solution) - High-Frequency Data Replication (based on implementation solution)

Lightning Platform Integration Patterns

- Remote Process Invocation: Request and Reply - Remote Process Invocation: Fire and Forget - Batch Data Synchronization - Remote Call-In - Data Virtualization - High-Frequency Data Replication - Publish/Subscribe

Salesforce to System Integration Patterns

- Remote Process Invocation: Request and Reply - Remote Process Invocation: Fire and Forget - Publish/Subscribe - High-Frequency Data Replication - Data Virtualization

Consumer Goods Objects

- Retail Store - Retail Store group - Visit - In-Store Location - Retail Location Group - Assortment

Consumer Goods Junction Objects

- Store Assortment - Assortment Product - Product Category Product - Store Product

API Integration Layers

- System Layer - Process Layer - Experience Layer

Empathy Map Characteristics

- The map is split into 4 quadrants: Says, Thinks, Feels, Does - It shows user's perspective regarding the tasks related to the product. - It is not chronological or sequential. - There is one for each persona or user type (1:1 mapping).

Customer Journey Map Characteristics

- The map is tied to a specific product or service. - It is split into 4 swim lanes: phases, actions, thoughts, mindsets/emotions. - It reflects the user's perspective including their mindset, thoughts, and emotions while leaving out most process details. - It is chronological. - There is one map per persona/user type (1:1 mapping).

Empathy Map Benefits

- This builds empathy for your users. - To force alignment and understanding about a user type.

Service Blueprint Benefits

- To discover weaknesses in the organization - To identify opportunities for optimization - To bridge cross-department efforts - To break down silos and create one shared, organization-wide understanding of how the service is provided

Customer Journey Map Benefits

- To pinpoint specific customer journey touchpoints that cause pain or delight. - To break down silos to create one shared, organization-wide understanding of the customer journey. - To assign ownership of key touchpoints in the journey to internal departments.

Integration Considerations

- To replicate data between Salesforce and Heroku, use Heroku Connect. - To expose a Heroku Postgres database to Salesforce, use Heroku Connect External Object. - To proxy OData, SOAP, XML, or JSON data sources into Salesforce, use Salesforce Connect. - If Heroku Connect doesn't fit the bill, like when you have a custom UI on Heroku where users log in via Salesforce, use the Salesforce REST APIs. - To offload or extend the process of Salesforce data events, use callouts from Salesforce to Heroku. - To embed a custom UI from Heroku (or other external web app) into Salesforce, use Canvas.

Experience Map Benefits

- To understand a general human behavior. - To create a baseline understanding of an experience that is product/service agnostic.

API Planning Framework Elements

- User Experience: What is the end user experience? What tools does a developer need? - Objects and records: What data are your working with? - Operations: what are you trying to do with the data? - Growth and Scale: How does your integration scale with the growth of your dataset? - API Limits and Allocations: How many API resources are your resources using?

Task Layer Categories

- User Interface Layer - Business Process Layer - Data Layer

Channel Strategy Key Questions

- Why are we building an indirect sales channel, and how does that fit into our corporate strategy? - What do we need to invest in order to build the channel, and where does that investment come from? - How do I get my partners to sell my products/services versus those of my competitors? - How do we plan, get reports, and be able to manage the indirect business? - How do we support partners with demand creation and demand fulfillment?

Assortment Object

In the consumer goods data model, this defines the mixed bag of products eligible for sale at a specific store or store group.

Salesforce Lightning Platform Integration Pattern: Data Virtualization

In this Salesforce Lightning Platform integration pattern, Salesforce accesses external data in real-time.

Salesforce Lightning Platform Integration Pattern: Remote Process Invocation - Fire and Forget

In this Salesforce Lightning Platform integration pattern, Salesforce invokes a process in a remote system but doesn't wait for completion of the process.

Salesforce Lightning Platform Integration Pattern: Remote Process Invocation - Request and Reply

In this Salesforce Lightning Platform integration pattern, Salesforce invokes a process on a remote system and then waits for a reply.

Salesforce Lightning Platform Integration Pattern: Publish/Subscribe

In this Salesforce Lightning Platform integration pattern, Salesforce publishes an event (such as a record created, changed, deleted, and so on) with no knowledge of who may be on the receiving end. Any number of subscribers listen for these events and process them accordingly.

Salesforce Lightning Platform Integration Pattern: Remote Call-In

In this Salesforce Lightning Platform integration pattern, a remote system creates, retrieves, updates, or deletes data stored in Lightning Platform.

Salesforce Lightning Platform Integration Pattern: High-Frequency Data Replication

In this Salesforce Lightning Platform integration pattern, a source system asynchronously replicates data to a target system in near-real time at high scale.

Salesforce Lightning Platform Integration Pattern: Batch Data Synchronization

In this Salesforce Lightning Platform integration pattern, when data is updated in an external system or on the Salesforce Lightning Platform, the updates are reflected in either system. Updates are applied in a batch manner.

Salesforce Connect Benefit

It brings external data into the Salesforce UI and makes it look as if the data resides in Salesforce, although it's just proxied on demand from an external data source. This process makes it easy to collate disparate data sources for Salesforce users.

Connectors

These are developer enablement frameworks that accelerate cross-cloud integration by providing code, configuration, and implementation patterns.

Omni-Channel Supervisor

This allows service managers to see and manage data related to their business's priorities. They track data like: - Wait times - Open cases - Who's working on what - Who has capacity for more cases

Service Blueprints

These are counterparts to customer journey maps, focused on the employees. It visualizes the relationships between different service components - people, props (physical or digital evidence), and processes - that are directly tied to touchpoints in a specific customer journey.

Assessment Task Definition Object

This object holds information on the name, description, category, and type of task.

Future (To-Be) Maps

These are based on an "ideal" state for a user type, experience, or a to-be service structure. The help reinvent and conceive how a user or experience would feel in the future.

Hypothesis Maps

These are based on an accumulation of existing understanding within a team or organization. This approach is a great way to merge multiple existing team views, create a research plan (based on the gaps that emerge), and make a first step towards a higher-fidelity, research-based map.

Current (As-Is) Maps

These are based on an actual "today" state of what you are mapping. This approach is ideal when the mapping goal is to identify and document existing problems and pain points.

AppExchange Bolt Solutions

These are complete industry solutions that are quick to deploy on Salesforce. They can deliver a complete customer onboarding experience, jumpstart the creation of a community or website that seamlessly integrates with Salesforce CRM, and create a portal for franchisees to access the latest version of logos and other brand assets. The deployment requires the services of the partner who created it. They help you install and customize the solution to suit your needs.

High-Fidelity Maps

These are polished, created digitally, and look final. They are the best for creating an artifact that is going to be shared amongst many. They can be easier to read, but less flexible because of the "finished" nature of the product. These maps are often created digitally, then dispersed.

Flow Templates

These are prebuilt, end-to-end, configurable business processes tailored to match specific industry use cases.

Flow Actions

These are prebuilt, stand-alone, functional elements that perform an action within the context of a flow.

AppExchange Consultants

These are specialists with deep industry knowledge and proven Salesforce expertise.

Low-Fidelity Maps

These are unpolished and often created with sticky notes in a flexible, unrefined manner. These maps are best in an early part of the process. They mean little commitment or creation effort and empowers people to collaborate, revise, and update as needed.

AppExchange Web Components

These are user interface elements that can be used to augment or customize a page.

Integration Patterns

These are valuable resources for architects assessing solutions for an integration strategy. They identify how systems (including their components and services) interact as part of an integration solution design. They show you how established solutions accomplish an integration goal. In addition, they communicate how the overall solution functions. They describe (or capture) a proven way to evaluate and solve integration problems without reinventing the wheel.

AppExchange Flow Solutions

These automatically do things, such as update data, send emails, and interact with external systems, on behalf of the user. This is an umbrella term for two solution types: flow actions and flow templates.

Callouts

These can be used to call external processes on Heroku. You write these in Apex or use workflow outbound messages to have events on Salesforce trigger the execution of a process on Heroku.

Presale Activities

These ensure that products never run out of stock, and the products and promotions are always well-received. They primarily consist of order placement, collection of feedback, and other custom tasks that help companies acquire more customers and increase their footprint.

Experience Map

These generalize the concept of customer-journey maps across user types and products. It is a visualization of an entire end-to-end experience that a "generic" person goes through in order to accomplish a goal. This is agnostic of a specific business or product. It's used for understanding a general human behavior.

Salesforce Solution Kits

These help you solve common business problems by connecting multiple clouds or products. They address a real-world use case and provide a list of required products, considerations, connectors, and configuration steps. They also include a high-level workflow diagram to guide your process, and some include a solution architecture diagram as well.

Lagging Metrics

These metrics are associated with sales outcome and must include more than the simple revenue metric.

Merchandising Activities

These revolve around upselling a promotion, product demos at store outlets, inventory audits, planogram compliance checks, and checking assets on site. When pricing, promotions, and products vary by stores, tracking retailer compliance can be tricky - so this becomes essential.

API Integration Layer: System

This API integration layer is directly connected with external systems, for instance the database, legacy systems, or SaaS applications. Connecting to external systems is the only job of this layer. This creates System APIs as reusable assets that can be used in other applications that you create.

API Integration Layer: Experience

This API integration layer is where the end user interacts with the data and processes. At this point, the user can modify the data and tailor it for their intended audience. Containing the UI in its own layer provides scalability, and it can be segmented into different categories.

API Integration Layer: Process

This API integration layer reads the data. This is where the business logic and orchestrations are contained. Data is merged to create a unified business process view of the underlying systems.

Google Analytics for Salesforce Communities Package

This AppExchange package contains preconfigured Google Analytics reports that track partner activity within a community

Community Management Dashboard Package

This AppExchange package tracks community engagement and monitors health.

Data Proxies

This aggregates different datastores without copying the data. The data can be read only on demand. This approach enables data science, business intelligence, reporting, and dashboarding tools to collate data across multiple datastores without worrying about data synchronization challenges like storage and staleness. You can integrate legacy systems and external systems through these to provide data to Salesforce, or Salesforce can provide its data to other external systems.

Omni-Channel Routing

This allows agents to receive cases via a push model, which assigns work from multiple channels. Businesses can route cases based on: - Highest prioirty - Oldest items first - Availability of an agent - Agent capacity

Omni-Channel Presence

This allows agents to set their availability here so they receive the right cases when they're available.

External Processes

This can offload batch processing or workflow and trigger event handling to apps on Heroku. This method can be helpful depending on the type fo job that needs to be done and the amount of effort involved. Data science, machine learning, image and video processing, and integration with legacy or external systems can be reasons to offload these to Heroku.

MuleSoft Salesforce Connector

This connector has deep support for virtually every Salesforce integration capability, like Salesforce Connect and Platform Events (PE). This can be used by a Mule App to connect to and from Salesforce or other data sources, connecting, for example, Salesforce and Workday.

MuleSoft HTTP Connector

This connector supports listening for and sending HTTP requests. When you're using this within the sources, it's known as an HTTP listener. As a listener, you can receive the request from the client. If you're using this within the destination, it's know as an HTTP requester. As a requester, you can send ay request to the destination.

MuleSoft Database Connector

This connector works alongside any Java Database Connectivity (JDBC) accessible database, including Postgres. It supports the full range of database access possible with a relational database, such as CRUD, stored procedures, and bulk execute.

Direction

This dimension identifies the primary source system and the target system. It's about how the systems interact and connect, and not about the direction that data flows.

Field Service Feature: Service Resources

This field service feature highlights mobile employees who can perform field service work.

Field Service Feature: Service Crews

This field service feature highlights teams of service resources that are assigned to service appointments as a unit.

Field Service Feature: Service Territories

This field service feature highlights the regions where field service work is performed.

Field Service Feature: Skills

This field service feature highlights the skills required to perform field service tasks.

Field Service Feature: Operating Hours

This field service feature highlights the times when field service work can be performed for service territories., service resources, and customer accounts. They are mad up of time slots: a time period within a day when field service work can be completed.

Field Service Feature: Maintenance Plans

This field service feature provides plans that help you track preventive maintenance work using auto-generated work orders.

Field Service Feature: Work Types

This field service feature provides templates for common field service work, such as cable installations or furnace repairs.

Field Service Feature: Service Report Templates

This field service feature provides templates for customer-facing reports summarizing the status of service appointment and work orders.

Field Service Feature: Time Sheets

This field service feature provides tools to track the time your field service employees are spending on tasks.

Customer Journey Map

This focuses on a specific customer's interaction with a product or service. It is a visualization of the process that a person goes through in order to accomplish a goal tied to a specific business or product. It's used for understanding and addressing customer needs and pain points. In its most basic form, it starts by compiling a series of user goals and actions into a timeline skeleton. Next, the skeleton is fleshed out with user thoughts and emotions in order to create a narrative. Finally, that narrative is condensed into a visualization used to communicate insights that will inform design processes.

Volume

This focuses on the amount of the data and the size of the message communicated.

Empathy Map

This helps team members understand the user's mindset.. It externalizes user knowledge in order to create a shared understanding and aid in decision making.

Integration Initiative Category: Data Integration

This integration initiative category focuses on data integration and synchronization between two or more systems. This includes aspects of data integrity, data governance, data flow-design, and data migration.

Integration Initiative Category: Process Integration

This integration initiative category focuses on extending business processes and services across systems. This includes integration solutions such as events that trigger activity from one system or run transactions between two systems.

Integration Initiative Category: Application Integration

This integration initiative category focuses on extending features and functionality across systems. This includes UI-triggered events, API integrations, flows, and connectors.

Octane Score

This is a benchmark that measures a JavaScript engine's performance by running a series of automated tests. The higher this is, the better your Lightning Experience performance will be.

Lightning Usage App

This is a great way to track adoption and usage of Lightning Experience.

Data Replication

This is the act of copying or synchronizing data between Salesforce and another system. You can use this for data warehousing to enable cross-data source reporting and analysis. You can also use it to work with legacy systems that either need data from Salesforce or feed data into Salesforce. The most common use case with Heroku and Salesforce is to provide a high-throughput, low-latency interface for customer-facing applications built with open-source technologies.

Retail Store Object

This is used to capture the information about each physical store.

User Interface Layer

This layer focuses on user interactions with the system. In this layer, you identify the components to integrate third-party web applications into Salesforce.

Business Process Layer

This layer interacts with the data and builds on the UI layer. The business logic includes data interaction, validation, and processing data transactions. These transactions are real-time calls from the UI or data capture events to the database that stores the data.

Data Layer

This layer is the connection with the UI layer and business process layer. It maps and identifies the primary data source and connections to other segments of the system. Data transformations, migration, and replications often occur in this layer. The connectors and services aligned to this layer focus on data accuracies and integrity as the data permeates through the solution.

Deal Registration

This lets you manage channel conflict and get better pipeline visibility by allowing partners to securely register their own deals.

Synchronous Communication

This means a client sends a request to the server and waits for the response before issuing another request.

Asynchronous Communication

This means the system doesn't wait for a reply before proceeding. The application sends a message and the system returns a reply as soon as the resources are available. The system that sent the original message has the ability to continue sending messages without waiting for a reply. Processing the return message is controlled separately.

Assessment Task object

This object holds information about the actual activity that a field rep performs on the field.

Kanban View

This organizes a set of records into columns, so your reps can track their work at a glance.

Partners for Sales Reach

This partner type can expand your presence in a particular market or help you break into a new industry.

Partners for Delivery and Implementation

This partner type has been proven to augment technical staffing limitations.

Partners for Solutions, Support, and Maintenance

This partner type is a great way to modify or extend functionality.

Targeted Prompts

This prompt can connect to a specific page element to show your users exactly what you're referring to.

Action Plan Template

This provides a framework to reuse tasks across stores and visits.

Walkthrough

This provides a step-by-step, guided educational experience on a single page or across multiple pages by stringing together a series of floating, targeted, and docked prompts. They provide in-context training that's perfect for onboarding and feature adoption.

Canvas

This provides a way to load an external user interface into Salesforce that can interact with Salesforce data through a JavaScript API. You can run the external UI on Heroku and build it with an open-source web technology. The data requests that these apps make happen in the context of the Salesforce user.

Heroku Connect

This provides both data replication and data proxies for Salesforce. Data replication synchronizes data between Salesforce and a Heroku Postgres database. Depending on how it's configured, the synchronization is either one way or bidirectional. It also provides a data proxy to Salesforce through the OData protocol using Heroku External Objects.

Channel Sales

This refers to the distribution and selling of a product or service through a value-added reseller (VAR), distributor, or dealer/broker.

Lightning Page View Event

This tracks information such as the page a user visited, the browser they used, how long the user spent on the page, and the load time for the page.

Custom User Interfaces

You can easily create these for Salesforce using a variety of technologies, such as Visualforce and Lightning Components, to name two.