MENU
Cloud Kicks has created a new flow that deletes records.
What should the administrator consider when testing the flow?
39 comments · newest first
AM
Amber
11 months ago
I disagree with A, there must be a way to test it safely!
SK
Skye
11 months ago
D is spot on, better to keep those flows inactive while testing.
CA
Carin
12 months ago
Wait, even inactive flows delete test records? That seems risky!
TA
Taryn
12 months ago
Totally agree with C, hard deletes are no joke!
BR
Brandon
1 year ago
A flows with delete elements can't be debugged? That's a bummer.
YO
Youlanda
1 year ago
I believe flows with delete elements should be inactive to avoid accidental deletions, but I’m not completely certain about that.
SH
Sheron
1 year ago
I’m a bit confused about hard deletes during debugging. I feel like I read that they can’t be recovered, but I can’t recall the details.
ES
Essie
1 year ago
I think I saw a practice question that mentioned inactive flows still affecting records. That might be relevant here.
ME
Mertie
1 year ago
I remember something about debugging flows, but I'm not sure if delete elements can be debugged.
CH
Charlesetta
1 year ago
Ah, I see. The records deleted during debugging are hard deleted, not just moved to the recycle bin. That's good to know - I'll need to be extra careful when testing this flow.
RI
Ricarda
1 year ago
I'm feeling pretty confident about this one. I know the flow can't be debugged, so I'll just create a test record and run the flow to see what happens. As long as it's inactive, I should be good.
SO
Soledad
1 year ago
I'm a little confused about the debugging part. Does that mean I can't use the Flow debugger to test this flow? I'll need to find another way to test it.
DI
Dierdre
1 year ago
Okay, I think the key here is to make sure the flow is inactive before testing it. That way, even if it tries to delete a record, it won't actually happen.
MI
Mireya
1 year ago
Hmm, this is a tricky one. I'll need to be really careful when testing this flow to make sure I don't accidentally delete any real records.
CO
Cory
1 year ago
Easy peasy! The security guards are just doing their job to protect everyone. I'm confident this is a true statement.
MY
Myra
1 year ago
I've got this one! Fraudulent invoices are a classic way to trick the system and get around internal controls.
VA
Vallie
1 year ago
Hmm, this looks like a tricky one. I'll need to think it through carefully.
SH
Shawn
1 year ago
Okay, I think I've got this. The user ID is generated by concatenating specific parts of the user's name and birth year, and then it's displayed on a screen. So the number of DETs should be based on that display function. I'll go with option C.
MI
Ming
2 years ago
Haha, imagine if the flow deleted the entire Salesforce org during debugging. That would be a real 'cloud kick' for the admin!
FA
Fannie
1 year ago
C) Record deleted by Flow when debugging are hard deleted.
AN
Annice
1 year ago
B) Even if the flow is inactive, debugging the flow will delete the test record.
TE
Tess
1 year ago
A) Flows with delete elements cannot be debugged by the Flow debugged tool.
JO
Josphine
2 years ago
I'm a bit concerned about Option B. Even if the flow is inactive, debugging it could still delete the test record? That seems like a risky situation.
FE
Felicitas
2 years ago
I agree with Asuncion. It's crucial to ensure that the test record is not actually deleted when debugging a flow with delete elements.
JO
Johna
1 year ago
Alease: That's correct. Debugging the flow will actually delete the test record, even if the flow is inactive.
CA
Caitlin
1 year ago
User 3: Flows with delete elements cannot be debugged using the Flow debugged tool, right?
AL
Alease
2 years ago
User 2: Yes, that's important to remember when testing a flow with delete elements.
DO
Dorthy
2 years ago
User 1: I think we should inactivate the flow to prevent the test record from being deleted.
AV
Avery
2 years ago
But what about option C? Records deleted by Flow during debugging are hard deleted, so that's something to keep in mind too.
NO
Novella
2 years ago
I agree with Skye, inactivating the flow is important to prevent test record deletion.
SK
Skye
2 years ago
I think the administrator should consider option D.
RO
Ronnie
2 years ago
I believe option D is the correct answer. The flow should be inactivated to prevent accidental deletion.
AS
Asuncion
2 years ago
Option D is the correct answer. Flows with delete elements need to be inactivated to prevent accidental deletion of test records during debugging.
TR
Tresa
1 year ago
Yes, that's right. Inactivating the flow will prevent accidental deletion of test records.
SH
Sherita
1 year ago
I think the administrator should inactivate the flow with delete elements before testing.
TI
Tiffiny
1 year ago
Yes, that's right. Inactivating the flow will prevent accidental deletion of test records.
CO
Cora
1 year ago
I think the administrator should inactivate the flow with delete elements before testing.
MO
Mona
2 years ago
I agree. We need to make sure the test record is not actually deleted.
LO
Loreta
2 years ago
I think the administrator should be careful when testing the flow with delete elements.