hi question, whats the difference between making f...
# generalb
blue
11/15/2019, 7:09 AMhi question, whats the difference between making fields mandatory in the workflow through the Set Field Mandatory Action versus making them mandatory through the form(screen fields)?
k
KevinJ of Kansas
11/15/2019, 1:22 PMPrimarily impacts csv imports and other workflows And scripts. Also doing it in workflows gives you more finite control.
If it should always be mandatory, then do it on the form. Sometimes. Do it with workflow or script
b
blue
11/15/2019, 1:25 PM@KevinJ of Kansas Hmm alright. Do you know of a usual situation where a field would sometimes be mandatory? I'm thinking fields are tied to business processes which should be standard so I can't think of why a field should only be mandatory sometimes
k
KevinJ of Kansas
11/15/2019, 1:26 PMLead vs customer. You must have certain info on customer to transact, but at lead stage you don't.
KevinJ of Kansas
11/15/2019, 1:27 PMAlso, in larger or more diverse businesses with different processes within same organization
KevinJ of Kansas
11/15/2019, 1:28 PMCase types is another good one
b
blue
11/15/2019, 1:35 PMIn the case of a large business, are you talking about diff subsidiaries all using one workflow for a record but they have diff fields in their own forms?
k
KevinJ of Kansas
11/15/2019, 5:13 PMI suppose that's one way
KevinJ of Kansas
11/15/2019, 5:13 PManother would be multiple divisions
KevinJ of Kansas
11/15/2019, 5:17 PMI once worked with a client that did projects and repairs. All their processes were similar enough to not require additional forms - with only a couple fields that were different in required fields. (The service/repair group needed less)