Jonas Bergqvist
Sep 25, 2024
  1664
(0 votes)

Required fields support in Optimizely Graph

It's been possible to have "required" properties (value must be entered) in the CMS for a long time. The required metadata haven't been reflected in Graph - until now. Its now possible to get the GraphQL schema updated, to get information about which fields that always has a value.

Configure CMS

The CMS must be configured to send metadata about required (value must be entered) properties to the GraphQL schema. We had to add this configuration setting, to not create a breaking change for the 3.11.0 release. The default value is 'false'.

Set property as required

Here is an example of the property "Heading" in the "TeaserBlock" content type. This property is set to be "required" (value must be entered).

GraphQL query with required support

The GraphQL query is now configured to know that the field always has a value

Sep 25, 2024

Comments

Please login to comment.
Latest blogs
Optimizely PaaS + Figma + AI: Auto‑Generate Blocks with Cursor

What if your design handoff wrote itself? In this end‑to‑end demo, I use an AI Agent (inside Cursor) to translate a Figma design into an... The pos...

Naveed Ul-Haq | Feb 5, 2026 |

Graph access with only JS and Fetch

Postman is a popular tool for testing APIs. However, when testing an API like Optimizely Graph that I will be consuming in the front-end I prefer t...

Daniel Halse | Feb 4, 2026

Best Practices for Implementing Optimizely SaaS CMS: A Collective Wisdom Guide

This guide compiles collective insights and recommendations from Optimizely experts for implementing Optimizely SaaS CMS, focusing on achieving...

David Knipe | Feb 4, 2026 |

A day in the life of an Optimizely OMVP: Learning Optimizely Just Got Easier: Introducing the Optimizely Learning Centre

On the back of my last post about the Opti Graph Learning Centre, I am now happy to announce a revamped interactive learning platform that makes...

Graham Carr | Jan 31, 2026