Which actions are possible with multi-object custom forms? (Select two.)

Question

Options

• AShare data across multiple project levels
• BControl form visibility through group permissions
• CStore financial data directly in the form
• DApply calculated fields across tasks, issues, and projects

• A
  82% (23)
• B
  7% (2)
• C
  11% (3)

Explanation

Multi-object custom forms are designed to attach to and operate across multiple object types (tasks, issues, projects), which is exactly what options A and D describe. A is correct because attaching one form to different object types allows field data to be shared and referenced across project levels, eliminating redundant data entry. D is correct because calculated fields in multi-object forms can pull values from and compute results across tasks, issues, and projects simultaneously - a core use case for this form type.

B is wrong because group-based visibility control is a permission/access feature managed at the system or form-sharing level, not a capability unique to or enabled by multi-object forms. C is wrong because custom forms store custom field data, not financial records - financial data lives in dedicated budget/billing modules and cannot be "stored" inside a form itself.

Memory tip: Think "multi-object = multi-level data flow." If an answer describes the form connecting or computing across object types, it's likely correct. If it describes access control or storing specialized financial data, those are handled by other system features, not the form itself.

No community discussion yet for this question.