One application development guardrail limits the number of shapes(excluding connectors) in a flow rule. Why should a flow rule obeys this limit?

Question

Options

• AFlows with too many shapes cannot be updated
• BFlows with too many shapes cannot be saved
• CLimiting the number of shapes allows developers and end users to more easily understand the
• DAdding too many shapes in one flow rule may result in performance issues

• A
  3% (2)
• B
  11% (7)
• C
  80% (52)
• D
  6% (4)

No community discussion yet for this question.