Please document the limitations of triggers.
Description/Use Cases:
The current documentation doesn’t list any of the known limitations with triggers. It is impossible to know what is actually possible to do with triggers, without this information documented.
Business impact of limitation or missing feature:
It’s very frustrating to come up with a workflow, only to find out the entire thing won’t work because it turns out that for example, the “numeric" field type is not allowed to be referenced in triggers. There’s no way of knowing how many fields are missing, what actually is allowed, and what format they are allowed in (some allow “present or “not present”, others allow specific values to be selected, etc). There is no documentation on what user fields or organizational fields have limits in triggers, either, so it's a lot of stuff and places that you can get surprised by sudden limits that are not documented.
Other necessary information or resources:
I’m posting this here because I was told asking for documentation should be done as a feature request.
-
Hi CJ Johnson!
I believe some of what you are looking for is contained in the following document: Trigger conditions and actions reference.
There is a bit in there regarding custom fields under Table 1: Trigger Conditions:
Checkbox, drop-down, and date custom fields are available as conditions. For all other custom field types, you can only check to see whether a value is present or not.
Hope this document helps!
サインインしてコメントを残してください。
1 コメント