I have a tricky and relatively complex workflow rule + field update in my mind, and I'd like to hear your comments on which approach I should use to make it work as designed.
The field update is just on checkbox, so that's not the issue. But the workflow rule, let me first explain the case a bit.
We have one custom object, that has multiple record types, I'd like to cover most of them with this rule. Then within these record types we have some formula fields, that needs to be read (existing value or not). And on top of this multiple other fields to check that they are filled (some text fields, some picklists, and dates).
I have tried to search examples of similar issues, but unfortunately didn't found any matches so far.
I'd like to ask your help, that should I use IF () or CASE() clause here, and when using those, how I can make them nested, or is that even be needed ?
Brief pseudo-code example:
IF (Setup.Record.Type = 1,
AND(
NOT(ISBLANK(Name)),
NOT(ISBLANK(Site)),
NOT(ISBLANK(Prefix)),
NOT(ISBLANK(Network Connection))
), TRUE),
IF (Setup.Record.Type = 2,
AND(
OR(Text(Asset.Model = HD100), Text(Asset.Model = HD220),Text(Asset.Model = HD50)),
NOT(ISBLANK(Name)),
NOT(ISBLANK(Site)),
NOT(ISBLANK(Prefix)),
NOT(ISBLANK(Network Connection))
), TRUE),
ELSE(FALSE)
Where Name ; Site ; Prefix & Network Connection are text/number fields, and Model is formula field from Picklist.
Please ask following questions and guide me to the right track. All together in this rule, there would be 9 record types and the top most 25 fields in one record type to go through, so it will be quite complex at the end. But this will be handling a key for higher level of automation, as the updated checkbox is observed by other system.
Thanks already in advance! :)
10 answers
Based on the complexity you have described I think you have a few options.
1) Wrapping an OR() statement around what you have above instead of IF statements.
2) Try to group common fields scenarios together - This sounds like there may be too many permuatations.
3) Begin looking at an Apex trigger to be able to handle the formula size complexity
4) Split the variations into multiple workflow rules. This may be the best option.
Do 2-4 record types per rules if possible.
