0% found this document useful (0 votes)
438 views3 pages

Salesforce Integration Questions For Discovery

The document discusses key integration questions around user experience, data modeling, API operations, growth and scaling, and API limits. For user experience, it asks about the end user, use cases, service levels, and access channels. For data, it addresses identifying objects, fields, relationships, and mapping the data model. For APIs, it asks about data sources, volumes, direction, and operations. It also covers planning for growth in system performance and data volume over time, as well as monitoring API limits and request volumes.

Uploaded by

Good Crimp
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
438 views3 pages

Salesforce Integration Questions For Discovery

The document discusses key integration questions around user experience, data modeling, API operations, growth and scaling, and API limits. For user experience, it asks about the end user, use cases, service levels, and access channels. For data, it addresses identifying objects, fields, relationships, and mapping the data model. For APIs, it asks about data sources, volumes, direction, and operations. It also covers planning for growth in system performance and data volume over time, as well as monitoring API limits and request volumes.

Uploaded by

Good Crimp
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 3

Integration Questions

User experience: What is the end user experience? What tools does
a developer need?

Define the end user experience.


● Who is the end user?
● What will be the primary use case in which the end user will utilize your
solution?
● What service level agreements need to be met to enable a good
experience?
● What channels will your end user need to access the solution?

Define the developer experience. 


● Are there any technical dependencies to other tools?
● What kind of outcomes are you striving for with your solution?
● What are the other Salesforce solutions and systems that are in scope of
your project?
● What format is the data in?
● Are you dealing with a client-side or server-side enabled experience?

Objects and records: What data are you working with?

Identification of Data
● Are any objects and fields from non-Salesforce systems included in your
solution?
● What objects and field types will you need for your data?
● What are the key identifiers for each of the objects?

Relationships of Data
● Importance of Relationships
○ The metadata about objects and fields plays a vital role in

determining how data flows through your project.


○ The relationships between your objects determine the data structure

and how data is processed. Consider the following questions to help


determine the relationship between your objects. 

● Types of Relationships
○ These fields are called master-detail, indirect lookup, external lookup,

and lookup.
○ They create the one to one (1:1), one-to-many (1:N), and many-to-
many (N:N) relationships in Salesforce. 

● Questions on Relationships
○ How will records across your objects be created?
○ What are the relationships between the objects already in the

system?
○ Are there dependencies between the objects?

Mapping of the Data


● Value of Data Model
○ Data modeling determines the overall structure and relationships

between tables and systems.


○ The data modeling map is to help you understand what’s possible for

your solution. Your data modeling structure shows what’s happening


with the data at each level in the database and helps you easily
identify your data load.
○ Knowing these factors helps you determine how to scale the design. 

● Considerations for Data Model


○ How will the data be maintained as the project scales?
○ What type of reporting and analytics will you need?
○ How will this data be collected and processed across the system?

● Definition of Data Model


○ Define how data flows throughout your solution in mapping tool
○ Visualize any existing in Schema Builder
○ Identify the operations you want to execute
○ Ask, “Is there an API for that?” 

Specific API Integration Considerations

Operations: What are you trying to do with the data?

● How Will API Operate with Data


○ What is the source of truth for data structures?
○ What volume of data are you working with?
○ What direction is the data flowing as the end user consumes your

solution?
○ What data is being written to the database and at what time?
● What Type of API Will Operate with Data
○ How many records will the operation execute on?
○ Should the operation run in a synchronous or an asynchronous

mode?
○ Should operations execute individually, in a batch, or in a bulk

workload?
○ What happens when the transactions the operation executes fails?
○ How does the execution and performance of these operations impact

the end user experience?

Growth and scale: How does your integration scale with the growth of your
dataset?

● Definition of Growth and Scale


○ From the developer perspective, growth is about how well the system

performs as resources are consumed.


○ When planning for scale, you should also consider how well the

system functions as the data volume increases. 

● Considerations for growth and scale.  


○ What is the processing threshold for the resources you’re using?
○ What success metrics should you use to define growth?
○ How is the system tested throughout the ALM process?

API limits and allocations: How many API resources are your resources using?

● Check for API Limits and Allocations (Use, Remaining, Maximum)


○ System Overview
○ CLI

● Plan for API Limits and Allocations


○ How many other integrations are making API requests into your org?
○ How soon will your org reach its entitled API request limit each day?
○ What is your daily API request budget for your org?
○ How many API requests are needed to address your use cases and

data volume?

You might also like