A project manager needs to create a new project template with predefined custom forms and conditional fields. How should they configure this?

Question

Options

• AAssign task-level permissions to the project template
• BSet up conditional visibility for custom form fields
• CEnable auto-provisioning for the template
• DAdd resource-level calculations to the project form

• A
  18% (5)
• B
  71% (20)
• C
  4% (1)
• D
  7% (2)

Explanation

Option B is correct because conditional visibility for custom form fields is precisely the mechanism that controls when specific fields appear based on user input or project context - making it the direct tool for building smart, adaptive forms within a project template.

• A is wrong because task-level permissions govern who can do what on tasks, not how form fields behave or appear.
• C is wrong because auto-provisioning automates the creation/setup of resources (like user accounts or environments), not the configuration of form logic.
• D is wrong because resource-level calculations relate to workload or cost computations, not the structural display of form fields.

Memory tip: Think "conditional fields = conditional visibility." The word conditional appears in both the question and the answer - if a field's appearance depends on a condition, you need conditional visibility, not permissions, provisioning, or calculations.

No community discussion yet for this question.