Auto-Close Overdue Tasks Using

[@sweetpoodle]

This is amazing! You made flow designer so simple. I’m still trying to get a hang of it. I love this series Rob. Keep up the great work! I look forward to seeing more.

[@robertthedukefedoruk5607]

Very much appreciated!

[@amanthabbhatla1168]

I cannot thank you ENOUGH. I was trying out a use case and it didn't work for the longest time until you mentioned that there is Lookup Record and lookup Records 😭😭😭

[@robertthedukefedoruk5607]

If it saved you some time, I'd be honored if you'd share this video with your network.

[@KevinClark1]

I like this shirt :)

[@darleneyork2391]

Hi Robert, your videos are amazing. I love the error handler. So I've never thought about this? How can I make a flow fail so I can test the error handler? Any thoughts?

[@Ghyll]

Hi, very interesing video. Can we get a lesson on how to send approval reminders for pending RITMs but for specific catalog item?

[@robertthedukefedoruk5607]

I'll see what I can do.

[@Ghyll]

​@@robertthedukefedoruk5607 another queston: in this video example when you do testing and then you check updated records in execution details, first record has task number, but remaining ones has sys_id. Is that okay?

[@robertthedukefedoruk5607]

@@Ghyll - I never noticed that. But I did go and check the vtb_tasks to make sure they all updated as expected (which they did). Suspect it *might* be a visualization bug in flow designer. You see the Doc ID field actually stores a sys_id in the database... but for some reason that first record uses the display value instead. Plus, that value is coming from hte system... I don't tell the testing function what to display.

[@philipscherry7743]

Why don't you SAVE before TESTING?

[@robertthedukefedoruk5607]

To make sure you're paying attention. :)