Ryan Thomas - 4 years ago
If you use a formula [e.g. (Today()- DATEVALUE(CreatedDate)) >= 90 ], then you have to create all other filter criteria via formula instead of through Field/Operator/Value picklists. So there is a workaround for this.
I still upvoted the idea though.
On a related, but different note, I am creating an idea to allow for a second criteria (decision point) after the 'TRUE' determination path. It allows you to add more criteria in the 'FALSE' determination path, but not the 'TRUE'. It doesn't make sense.
Dave Masom - 4 years ago
Following on from Matt Shonkwiler's helpful workaround, if, like me, you need multiple different TODAY() + x inputs, you can do the following:
Have a number field correspond to x
Have a formula field that equals TODAY() + the field you just created
Then in process builder you can define x (the number field) and have a second process update your date field with the formula field when the number field is changed.
We used this to trigger a schedule of tasks with different due dates that occur when a custom object's status is changed. It's a bit clunky, but it works. It saved us from having to create 60+ fields for different dates!
Matt Shonkwiler - 4 years ago
A workaround that I'm using is... create a field that uses the formula you need. Then just use the "field picker" option to reference your newly created formula field.
It's not ideal, but maybe this will help you get by until formulas become officially supported within Process Builder.
Ashley Webster - 4 years ago
Agree with all comments. Create and Update record processes are close to useless without dynamic field values.
Please Salesforce, I beg you, take a close look at your culture of half baked and neglected ideas. I know you can't please everyone, but the number of times that a search for a solution brings me to one of these frustrating idea threads is innumerable. Hopefully this one won't languish for 7 years.