MENU
When a timecard is submitted into an Approval process, you would like to capture the Submitted Date in a field to use for reporting purposes. You've already created the new Submitted Date field on the Timecard object.
What is the easiest approach to use in setting up this configuration within an Approval process?
Suggested Answer: B
Get Premium PSA-Sysadmin Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
49 comments · newest first
FI
Filiberto
10 months ago
Why not just use a Flow instead? Seems like a missed opportunity!
IR
Ira
11 months ago
I agree with A, super straightforward!
DE
Delsie
11 months ago
Wait, can you really use a Workflow Rule for this? Sounds off.
IR
Irene
11 months ago
I think B could work too, but it seems more complicated.
BL
Blair
11 months ago
A is the easiest way to do it!
FL
Florinda
12 months ago
I’m a bit confused about option C. I don’t recall using Flow for this type of update. Is it really necessary when we have the Approval Process?
LU
Luis
12 months ago
I feel like I’ve seen a question like this before, and I think the Approval Process is usually the best place to handle it. So, A might be right.
PH
Phillip
12 months ago
I'm not entirely sure, but I remember something about using Workflow Rules for similar scenarios. Could option B work too?
SA
Sabrina
1 year ago
I think option A makes the most sense since we can directly add a field update in the Approval Process itself. That seems straightforward.
RU
Ruthann
1 year ago
I'm feeling pretty confident about this one. The Approval Process field update seems like the most straightforward solution to capture the Submitted Date. I'll go with that approach unless I see a clear reason why the other options might be better.
BE
Bettye
1 year ago
Ah, I see. Using a Flow to update the date field when the Timecard is submitted could also work. That might give me a bit more flexibility than the Approval Process or Workflow Rule options.
JU
Julene
1 year ago
Hmm, I'm a little unsure about this one. I'm trying to decide between the Approval Process update or the Workflow Rule approach. I'll need to think through the pros and cons of each before deciding.
SA
Sabina
1 year ago
This looks like a straightforward configuration question. I think the easiest approach would be to update the date field directly in the Approval Process when the Timecard is initially submitted.
MA
Marlon
1 year ago
I feel pretty confident about this one. The Reference Library is where you'd find the standards and specifications that architectures need to conform to, so I'm going with D.
SH
Sheron
1 year ago
I'm thinking option A, but maybe we can also add a little celebratory dance move when the Submitted Date is updated. You know, to liven things up a bit.
RE
Rebbecca
1 year ago
Option A is the way to go, no doubt. It's the Approval Process - that's where the action is happening, so that's where we need to be.
VI
Virgina
1 year ago
Option B with the Workflow Rule is interesting, but I'm not sure if it would capture the exact Submitted Date we're looking for. The Approval Process update in option A seems like the safest bet.
AN
Annice
1 year ago
Hmm, I'm not sure. Option C with the FinancialForce Flow seems like it might be more robust, but it could also be overkill for this use case. I'll have to think about it some more.
NE
Nenita
1 year ago
I was thinking the same thing. Adding a field update to the Approval Process seems like the simplest solution here. No need to overcomplicate things with a Workflow Rule or Flow.
PA
Pamella
1 year ago
C) I think using a Flow might be too complex for this scenario.
NA
Nan
1 year ago
A) Exactly, it keeps everything related to timecards in one place.
CH
Chara
1 year ago
B) I agree, keeping it within the Approval Process makes it easier to manage.
AU
Augustine
1 year ago
A) Go to the active Approval Process for Timecards and add a field update to update the new date field upon Initial Submission
DI
Diane
1 year ago
I think option A is the way to go. It seems like the most straightforward approach to update the Submitted Date field when the Timecard is initially submitted.
EL
Elke
1 year ago
I'm thinking option A, but maybe we can also add a little celebratory dance move when the Submitted Date is updated. You know, to liven things up a bit.
CL
Claribel
1 year ago
User 3: Sounds like a plan! Let's make updating the Submitted Date a fun process.
TA
Tammara
1 year ago
User 2: I agree, let's go with that. And I'm all for adding a celebratory dance move!
JA
Jaime
1 year ago
User 1: Option A sounds like the easiest approach to me.
FA
Farrah
1 year ago
Option A is the way to go, no doubt. It's the Approval Process - that's where the action is happening, so that's where we need to be.
ER
Ernest
1 year ago
Yeah, it keeps everything related to the timecard submission in one place.
PA
Paz
1 year ago
I agree, updating the field in the Approval Process makes the most sense.
VI
Virgie
1 year ago
Option A is the way to go, no doubt. It's the Approval Process - that's where the action is happening, so that's where we need to be.
TA
Tambra
1 year ago
Option B with the Workflow Rule is interesting, but I'm not sure if it would capture the exact Submitted Date we're looking for. The Approval Process update in option A seems like the safest bet.
BR
Brittney
1 year ago
Let's go with option A to make sure we have the correct Submitted Date for reporting purposes.
TY
Tyra
1 year ago
Workflow Rules may not always capture the exact date needed, so option A is more reliable.
OT
Otis
1 year ago
I agree, using a field update in the Approval Process ensures accuracy.
EV
Evangelina
1 year ago
Option A sounds like the best choice for capturing the exact Submitted Date.
BE
Bettina
1 year ago
Hmm, I'm not sure. Option C with the FinancialForce Flow seems like it might be more robust, but it could also be overkill for this use case. I'll have to think about it some more.
AU
Audria
1 year ago
I was thinking the same thing. Adding a field update to the Approval Process seems like the simplest solution here. No need to overcomplicate things with a Workflow Rule or Flow.
JA
Jamey
1 year ago
I agree, that seems like the most straightforward approach.
KI
Kiera
1 year ago
A) Go to the active Approval Process for Timecards and add a field update to update the new date field upon Initial Submission
KI
Kimbery
1 year ago
I prefer creating a Workflow Rule to update the date field when the Timecard Status changes to Submitted. It gives more control over the process.
JO
Jolene
2 years ago
I agree with Merilyn, adding a field update in the Approval Process seems like the most straightforward option.
MI
Mirta
2 years ago
I think option A is the way to go. It seems like the most straightforward approach to update the Submitted Date field when the Timecard is initially submitted.
TE
Temeka
1 year ago
Definitely. Option A is the most efficient approach to set up this configuration within the Approval process.
XU
Xuan
1 year ago
That makes sense. It's important to have the Submitted Date captured for reporting purposes.
ME
Merlyn
1 year ago
I think so too. It's simple and direct to update the new date field upon Initial Submission.
AN
Annabelle
1 year ago
I agree, option A seems like the easiest way to capture the Submitted Date in the Approval process.
ME
Merilyn
2 years ago
I think the easiest approach is to go to the active Approval Process and add a field update.