We’ve heard from customers a need to change their field or parameter values depending on the circumstances. Today, we’re introducing conditional values! Here are two examples:

• Change a design parameter — column count or spacing, based on screen size
• Check for the presence of a dynamic token and use a backup data resource if it is missing.

Criteria include — depending on the type of entity — the following:

• Dynamic tokens from data resources
• Quirk values
• Dynamic path segments
• Query string values

Architects must enable conditional values when configuring their components and content types. “Manage conditional values” may then be accessed from the ••• menu on each parameter or field.