Independence Day Deal! Unlock 25% OFF Today – Limited-Time Offer - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Salesforce Exam Process Automation Topic 1 Question 12 Discussion

Actual exam question for Salesforce's Process Automation exam
Question #: 12
Topic #: 1
[All Process Automation Questions]

Northern Trail Outfitters (NTO) is looking to build an app for its logistics team where users will

be able to submit inventory refill requests. The current manual process involves filling out a long

form containing many fields. NTO is planning to replace the current process with Flows. Users

frequently change field values as they are filling out the form. What should NTO keep in mind

about letting users go backward in the Flow to make updates to field values?

Show Suggested Answer Hide Answer
Suggested Answer: B

Contribute your Thoughts:

King
2 months ago
Ah, the joys of Flows. Where users can navigate like a maze, and developers can cry like a baby. NTO should just hire a professional Flow-whisperer to sort this out.
upvoted 0 times
Candra
1 months ago
D) Once the user navigates to previous screen, all field values on the current screen will be lost and will need to be repopulated.
upvoted 0 times
...
Sage
1 months ago
C) Letting users navigate from the later screen to the previous screen could result in duplicates.
upvoted 0 times
...
Francisca
1 months ago
A) Allow Navigation' needs to be set to TRUE on the Flow.
upvoted 0 times
...
...
Telma
2 months ago
B sounds like a power move. Only the chosen ones can navigate the Flows? Forget about that, I'm gonna hack my way through like the Kool-Aid man. Oh yeah!
upvoted 0 times
Stephaine
17 hours ago
B) Only users with 'Navigate Flows' permission can navigate to previous screens.
upvoted 0 times
...
Phung
6 days ago
C) Letting users navigate from the later screen to the previous screen could result in duplicates.
upvoted 0 times
...
Bronwyn
19 days ago
A) Allow Navigation' needs to be set to TRUE on the Flow.
upvoted 0 times
...
William
20 days ago
D) Once the user navigates to previous screen, all field values on the current screen will be lost and will need to be repopulated.
upvoted 0 times
...
Theresia
1 months ago
C) Letting users navigate from the later screen to the previous screen could result in duplicates.
upvoted 0 times
...
Serina
2 months ago
A) Allow Navigation' needs to be set to TRUE on the Flow.
upvoted 0 times
...
...
Merlyn
2 months ago
D is also a good point. Losing all the data on the current screen? That's a recipe for frustration and user rage. NTO should definitely watch out for that.
upvoted 0 times
Nicolette
1 months ago
D is a good point. Losing all the data on the current screen can be frustrating.
upvoted 0 times
...
Stefania
1 months ago
A) Allow Navigation' needs to be set to TRUE on the Flow.
upvoted 0 times
...
...
Remedios
2 months ago
But what about option C? Duplicates could be a big issue too.
upvoted 0 times
...
Terrilyn
2 months ago
I agree with Janine, losing field values would be a hassle.
upvoted 0 times
...
Dorothy
2 months ago
I agree with C. Having users go back and forth could create a mess with duplicate requests. Gotta keep that flow tight!
upvoted 0 times
...
Janine
2 months ago
I think NTO should keep in mind option D.
upvoted 0 times
...
Katlyn
2 months ago
C is the correct answer. Letting users navigate back can lead to duplicates, which is a valid concern that NTO should keep in mind.
upvoted 0 times
Marget
19 days ago
True, it's important to balance user experience with data integrity in this case.
upvoted 0 times
...
Ryan
2 months ago
That's a good point. Maybe NTO should consider a way to save field values when users navigate back.
upvoted 0 times
...
Lanie
2 months ago
But what about D? If all field values are lost, that could be frustrating for users.
upvoted 0 times
...
Martina
2 months ago
I think C is the correct answer. We need to avoid duplicates.
upvoted 0 times
...
...

Save Cancel
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77