MENU
The architect is designing a flow where a screen flow is used to create a contact and display a
confirmation screen. While the confirmation screen is displayed, remote API is invoked to update
the contact in the external system. The update fails. How should the architect resolve the design?
Suggested Answer: A
Get Premium Process Automation Accredited Professional (AP-221) Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
In the scenario where a remote API update fails after creating a contact through a screen flow, incorporating an error handling mechanism within the flow is essential. This allows the flow to gracefully handle exceptions and errors, providing feedback or rollback options as necessary. Regular testing during the development phase helps identify potential issues early, ensuring the flow functions as intended upon deployment. Reference: Salesforce Help - Add Fault Handling to Your Flow
44 comments · newest first
TI
Tijuana
11 months ago
Error handling is crucial in any flow design!
EM
Emile
11 months ago
I think using Process Builder (D) is outdated.
GR
Graciela
11 months ago
Wait, is it really not possible to update via flow? (C)
MA
Malcom
11 months ago
I disagree, using a separate transaction (B) is better for reliability.
GL
Gladys
12 months ago
Option A seems like a solid choice.
RU
Ruthann
12 months ago
I don't think switching to Process Builder is the right move; we focused on flows for this kind of task. Option D seems off to me.
HE
Herminia
1 year ago
I vaguely recall something about using Apex for external updates, but I’m not confident if that’s necessary here. Option C could be a fallback, right?
LA
Larae
1 year ago
I think using a separate transaction could help isolate the update process, like we practiced in that last case study. Option B might be the way to go.
AR
Arlen
1 year ago
I remember we discussed the importance of error handling in flows, so option A sounds familiar, but I'm not entirely sure if it's the best choice here.
AM
Amber
1 year ago
Process builder, huh? I haven't used that in a while, but it might be worth considering as an alternative to the flow approach. I'll need to look into the pros and cons.
LE
Leatha
1 year ago
Hmm, I'm not sure about using Apex for this. I'll need to review the flow capabilities and see if there's a way to handle the remote update within the flow itself.
MO
Moon
1 year ago
Using a separate transaction to update the contact in the external system could be a good way to handle this, but I'll need to double-check the details on that.
SI
Silva
1 year ago
Hmm, this looks like a tricky one. I'll need to think through the different options carefully and consider the implications of each approach.
AR
Arleen
1 year ago
Okay, I think I've got a handle on this. Adding error handling and testing early seems like a solid strategy to me.
SH
Shaun
1 year ago
Okay, let me think this through. XHTML and XSLT are definitely coded using XML, and SOAP headers also use XML syntax. I'll go with B and C for my answer.
DE
Dewitt
1 year ago
I'm a little confused by the wording of the question. I'll need to re-read it a few times and think through each of the conditions to determine the best answer.
GE
Gerald
1 year ago
I recall a practice question that mentioned national income, but that sounds different from what we're looking for here.
ER
Erasmo
1 year ago
I think we had a similar practice question where we discussed federation vs. interoperability. I need to check my notes on that.
CH
Cherry
2 years ago
Haha, D? Using Process Builder instead of Flow? That's like using a sledgehammer to crack a nut!
LA
Lazaro
2 years ago
C) Use Apex since updating a contact in the remote system is not possible in flow.
SA
Salina
2 years ago
B) Use a separate transaction to update the contact in the external system.
MA
Maybelle
2 years ago
A) Add error handling mechanism to the flow and test often and early.
SE
Selma
2 years ago
I'd go with B. Keeping the flow and the external update separate is the smart move here.
DE
Devon
2 years ago
B) Use a separate transaction to update the contact in the external system.
VE
Veronika
2 years ago
A) Add error handling mechanism to the flow and test often and early.
RA
Raelene
2 years ago
I'd go with B. Keeping the flow and the external update separate is the smart move here.
BE
Berry
2 years ago
B) Use a separate transaction to update the contact in the external system.
CA
Candida
2 years ago
B) Use a separate transaction to update the contact in the external system.
MA
Maybelle
2 years ago
A) Add error handling mechanism to the flow and test often and early.
CA
Cassie
2 years ago
A) Add error handling mechanism to the flow and test often and early.
BE
Bette
2 years ago
C? Apex? No way, that's overkill. Flows are great for this use case if you handle the errors properly.
AN
Angella
2 years ago
C? Apex? No way, that's overkill. Flows are great for this use case if you handle the errors properly.
AL
Alaine
2 years ago
A) Add error handling mechanism to the flow and test often and early.
AL
Aleta
2 years ago
B sounds like the way to go. Separate transactions will ensure the flow doesn't get stuck if the external update fails.
DE
Denise
2 years ago
It's important to consider all options and choose the one that best fits the design requirements.
KA
Karol
2 years ago
Using a separate transaction seems like a safe bet to prevent any issues with the external update.
LA
Latrice
2 years ago
Agreed, testing often and early with error handling is key to ensuring the flow works smoothly.
JU
Juliann
2 years ago
Process builder might not be the best option as it is more suitable for simple workflows.
ST
Stefania
2 years ago
I think using Apex might be an overkill for this scenario. Keeping it simple is better.
AN
Andree
2 years ago
Yes, adding error handling mechanism to the flow is also important to handle such scenarios.
GE
Gerald
2 years ago
B sounds like the way to go. Separate transactions will ensure the flow doesn't get stuck if the external update fails.
AL
Alishia
2 years ago
B sounds like the way to go. Separate transactions will ensure the flow doesn't get stuck if the external update fails.
CL
Clare
2 years ago
A) Add error handling mechanism to the flow and test often and early.
LE
Lera
2 years ago
Definitely A. Error handling is crucial, especially when dealing with external systems. Can't risk leaving users in the dark.