Skip to Main Content
Customer Feedback

We love feedback from you on our products and the problems in your daily work that you would like us to solve. Please describe the challenge you're encountering and your desired outcome. Be as detailed as possible.

For technical issues or bugs please head to Support or our Developer Community. You can assign up to 20 votes in total. Thank you for your feedback.

Status explanation: 'Future Consideration' = Continuing to collect further feedback, not planned at this time. 'Investigating' = Prioritized for deeper customer and feasibility investigations ahead of planning development.

ADD FEEDBACK

Optimizely Graph

Showing 12 of 1643

Support for JSON scalar type for XhtmlString field in OptiGraph

We would want to have support for JSON scalar type for XhtmlString fields in OptiGraph. The format is already use in the CD API (check the image attached). In OptiGraph response the XhtmlString appears now just in one JSON string.
5 months ago in Optimizely Graph 2 Investigating

Short-lived instances for QA

Customers running automated test need a way to quickly setup and teardown short lived graph instances for the purpose of verifying code changes.
about 2 months ago in Optimizely Graph 0

UI for managing items in the Graph

Super users and developers troubleshooting Graph content would get a lot of value from a tool to inspect and trim the actual graph entities in a way that's simpler and more intuitive than iGraphQL. Example scenarios Whitelist in CMS was updated an...
7 months ago in Optimizely Graph 0 Future consideration

Support blue/green deployment

As a Customer, I would like to have a blue/green deployment mechanism so that I can confidently implement substantial changes, encompassing both code and content updates, in production. Description I am planning to deploy a new feature to my app t...
8 months ago in Optimizely Graph 0

Full support for CMS language settings

It should be simple to get language behavior consistent with CMS language settings around fallback and replacement languages.
over 1 year ago in Optimizely Graph 0 Future consideration

Support geo-point and geo-search

The Graph should support the geo-point type that consists of coordinates. Then I want to query with this field type with the following new operators only for the geo-point type: distance and boundingBox. I also want to sort the results by distance...
almost 2 years ago in Optimizely Graph 0 Planned

GraphQL Mutations idea

We've managed to implement nested blocks in the Content Delivery API so we're past that point. The Graph API seems promising and it was easy to set up, however we wonder how far away it is to be able to create mutations? Is there any documentation...
over 1 year ago in Optimizely Graph 0 Investigating

_ancestors support in query language, similar to _children

Its possible today to query for _children in several levels. I would also like to have the same support but for ancestors. You would then query for ancestors under a content item, where the items could be several levels down in the content tree.
over 1 year ago in Optimizely Graph 1

Better graph support

Instead of only having parent-child relation, Content Graph should support graph relation model. e.g. enabling querying “hotel” content items by Country, even though hotels are only related to cities.
over 1 year ago in Optimizely Graph 0

Content Graph availability in a Saudi Private Cloud (eg. STC Private cloud)

As a Customer in Saudi I want to use Content Graph from a data centerer within the Kingdom
over 1 year ago in Optimizely Graph 0