Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Salesforce Exam Salesforce-Hyperautomation-Specialist Topic 4 Question 4 Discussion

Actual exam question for Salesforce's Salesforce Certified Hyperautomation Specialist exam
Question #: 4
Topic #: 4
[All Salesforce Certified Hyperautomation Specialist Questions]

An RPA process is invoked by a MuleSoft Composer flow. The RPA process has a User Task that can take up to 24 hours to complete.

Show Suggested Answer Hide Answer
Suggested Answer: C

When an RPA process involves a User Task that can take a significant amount of time (up to 24 hours) to complete, it is best to use a follow-up mechanism to handle the results once the process is finished:

Second MuleSoft Composer Flow:

Create a second MuleSoft Composer flow that is triggered when the RPA process completes. This ensures that the first flow is not held up while waiting for the long-running RPA process to finish.

The second flow can start based on an event, such as the completion status of the RPA process, ensuring timely and efficient processing of the results.

Trigger Mechanism:

Configure the RPA process to notify MuleSoft Composer when it is complete, possibly using a REST API or another integration method.

Best Practices:

This approach adheres to best practices by keeping flows modular and focused on specific tasks, making them easier to manage and troubleshoot.


MuleSoft Composer Documentation

MuleSoft RPA Documentation

Contribute your Thoughts:

Verda
22 days ago
I bet the RPA process is powered by a team of mules running on a treadmill. 'Mule-Soft' Composer, am I right?
upvoted 0 times
Haydee
7 days ago
A) Using best practices, how should the results be consumed by MuleSoft Composer?
upvoted 0 times
...
...
Yvonne
24 days ago
B is the classic choice, but I like the idea of C. Keeps things nicely decoupled and event-driven. Plus, it's more fun to say 'MuleSoft Composer' out loud.
upvoted 0 times
...
Katina
28 days ago
Hmm, E looks interesting. Checking on a schedule could be a good way to handle the long-running task without blocking the main flow.
upvoted 0 times
Joni
22 hours ago
User 3: Waiting for the RPA process to complete and using the results in the same flow could cause delays. E seems like a more efficient approach.
upvoted 0 times
...
Royal
7 days ago
User 2: I agree. It's important to have a way to check if the RPA process is complete without waiting indefinitely.
upvoted 0 times
...
Yuki
12 days ago
User 1: E looks like a good option. It's a way to handle the long-running task without blocking the main flow.
upvoted 0 times
...
...
Eleni
1 months ago
D is the way to go. Why create a whole new flow when you can just use the results in the same one? Efficiency is key!
upvoted 0 times
Dallas
9 days ago
Rosamond: Exactly, keeping it simple is always the best approach.
upvoted 0 times
...
Rosamond
12 days ago
User 2: Definitely, no need to create unnecessary complexity with a new flow.
upvoted 0 times
...
Joana
17 days ago
User 1: I agree, using the results in the same flow is more efficient.
upvoted 0 times
...
...
Denise
1 months ago
Option C seems like the best approach. Separating the flows makes it more modular and easier to maintain.
upvoted 0 times
Lyda
25 days ago
Option C does seem like a good choice for this scenario.
upvoted 0 times
...
Bobbye
30 days ago
I agree, having separate flows for different tasks is definitely more organized.
upvoted 0 times
...
...
Brett
1 months ago
I prefer option E, as it allows for better monitoring and control.
upvoted 0 times
...
Jina
1 months ago
But with option D, we might have to wait unnecessarily in the same flow.
upvoted 0 times
...
Edwin
2 months ago
I disagree, I believe option D is more efficient.
upvoted 0 times
...
Jina
2 months ago
I think option C is the best approach.
upvoted 0 times
...

Save Cancel