66 results found
-
Date/time element for forms
The current supported form types for SaaS CMS do not support a date/time element. This is a common element for dates, DOB etc
Reference
https://docs.developers.optimizely.com/content-management-system/v1.0.0-CMS-SaaS/docs/form-elements2 votesWe’re currently gathering additional feedback on this idea. If you have any more context, examples, or specific use cases, please share them - it really helps us understand how this would best support your workflow. Thanks for contributing to the conversation!
-
User experience improvement for Export Data
There is an Export property setting option that appears at the bottom of a screen ONLY when one or more Content Type options are selected. It is otherwise unexposed, and perhaps in the wrong place. I have a suggestion.
TL:DR The problem arises when you select the Content Types section on the Export Data window, which presents a long list of content types. (See attached screenshots.)The user might select a few content types from the top or Select All and click Export and never see that the Export property setting option "magically" appeared off-screen below three other sections (Export tabs,…
2 votes -
Pageview data per domain
Make it possible to see pageview data and performance data per domain in the IQI report and the DXP dashboard.
2 votes -
Feature request: Cloudflare Turnstile Support in DXP
Cloudflare Turnstile is a modern, privacy-friendly captcha solution that improves user experience. Since Cloudflare is already part of DXP, it would be great to see native support for Turnstile in the platform.
2 votes -
Execute Manually run Scheduled Jobs on the Scheduled Job Server
When a scheduled job is executed on a schedule it is executed on the special Scheduler server instance. When a scheduled job is executed by running it Manually it appears it executes on one of the front end servers. This feedback request is to suggest adding the manually run jobs to the queue or some other mechanism so they are executed on the scheduler instance. Running the scheduled jobs on the frontend web instances exposes the end users to poor performance when CPU and memory is peaked and can cause delays in executing the scheduled job when the server becomes…
2 votes -
Cloudflare 524 error page Statistics, Alerting and Customization request
When Cloudflare fails to load a page on our DXP hosted website we would like the ability to see statistics about the number of time the 524 error page was displayed to our users.
We would like to request that statistics and/or alerting be made available through the DXP portal to be able to determine the scope of issues involving 524.
https://developers.cloudflare.com/support/troubleshooting/cloudflare-errors/troubleshooting-cloudflare-5xx-errors/
https://developers.cloudflare.com/analytics/account-and-zone-analytics/zone-analytics/
We would also like to request the ability to provide customization to the 524 page to include our company's branding and/or the ability to add Google Analytics to provide statistics on these error page views.
https://developers.cloudflare.com/support/more-dashboard-apps/cloudflare-custom-pages/configuring-custom-pages-error-and-challenge/2 votes -
Automate Site Restarts
Currently the only way to restart and environment is via the PaaS portal. It would be nice to be able to automate a restart as the last step of a deployment pipeline from for instance Azure Devops. Perhaps this feature could be added to the EpiCloud powershell module:
https://www.powershellgallery.com/packages/EpiCloud/0.12.142 votes -
API for DXP environment restart
Currently you can restart an environment only manually from Optimizely paasportal.
We would need an API for restarting environments, which would be a more modern way of doing things and it would allow a better automation for managing environments.2 votes -
Ability to reset CMS SaaS environment
It would be great to have a way to completely reset a saas instance. It'd be really helpful to have a clean slate for our current work.
2 votes -
property-level permissions
Ability to set permissions either at the property level or the tab/property group level.
Example scenario: you have SEO fields on a page/experience type that only people in an "SEO Manager" role should be able to modify, while other roles can modify the rest of the page properties/content.
1 vote -
Restrict Content and Content types via API keys to a group or site
As a CMS admin, I want to provide access to my development team/delivery apis to a site or sites and content types with the right level of access. (Read, Edit, delete, Create)
This would enable teams to work in an isolated manner that.
One thought is to be able to assign a Content type to a Site or Sites.
1 vote -
Desktop/Tablet/mobile feature for preview is not available for standard page in visual builder
For content managers and editors, it is essential to have the ability to preview pages across multiple device types. Currently, this functionality is limited to Experience Types only.
This is a significant gap, as standard pages are also being created and previewed within the Visual Builder. Enabling multi-device preview for these pages would greatly enhance the content editing and validation experience for editors and managers.
1 vote -
Boosting to be be applied directly to a nested field like HeroBlock.Heading in the where clause.
I'm a developer, currently using optimzely CMS SaaS. My client would like to take advantage of boosting for specifc fields in a where clause of our GraphiQL search queries. I have learned however that in Optimizely Graph, boosting can be applied only directly to fields that belong to the top level content type, such as Title, MetaDescription, or _fulltext. These properties are directly available in the GraphQL schema for the content type, which is why boosting works as expected when applied to them.
Properties that belong to blocks placed inside a Content Area, such as the Heading property in a…
1 voteWe’re currently gathering additional feedback on this idea. If you have any more context, examples, or specific use cases, please share them - it really helps us understand how this would best support your workflow. Thanks for contributing to the conversation!
-
Isolated Optimizely Graph environment for automated & ephemeral testing
As a developer, I would like to run Optimizely Graph in an automated and isolated environment—such as CI/CD pipelines or GitHub Actions—so that I can reliably test features without relying on shared cloud instances.
A common example would be some kind of official container image that allows me to spin up a local or ephemeral instance of Optimizely Graph for integration testing.
1 voteWe’re currently gathering additional feedback on this idea. If you have any more context, examples, or specific use cases, please share them - it really helps us understand how this would best support your workflow. Thanks for contributing to the conversation!
-
PaaS Portal - Delete cached content also deletes Graph Cache
There should be a button (or by clicking the CDN-cache purge) that cleares/invalidates the Graph cache.
This is especially useful (necessary) when Graph synchronization fails, as the cache is only cleared upon sync completed.1 vote -
Assign approval workflow only to certain roles in CMS
When setting up approval workflows to publish content, the workflow gets automatically assigned to all roles.
However I only want to apply this review requirement to certian low level roles. I, as a Content Admin, should not have to send my own edits for review and then approve my own changes. It is multiple extra clicks, which is redundant.
When creating an approval workflow, I should have the option to assign it to specific roles. Roles not assigned to should be exempt from the need to send for review.
1 vote -
graph indexing
Request: ability to trigger Graph indexing job programmatically
If you update content types via import or API, my understanding is that you need to manually trigger the Optimizely Graph indexing job to sync those model changes to Graph.
The ability to trigger that indexing job via API would enable more automated processes for introducing changes to content types to a SaaS CMS instance.
1 voteWe’re currently gathering additional feedback on this idea. If you have any more context, examples, or specific use cases, please share them - it really helps us understand how this would best support your workflow. Thanks for contributing to the conversation!
-
Update the instance name in the CMS navigation URL
Customers have the ability to manage CMS product details in Admin Center, including the CMS navigation URL - https://support.optimizely.com/hc/en-us/articles/28866325868301-Manage-product-details
However, the instance name in the URL is not customizable from this customer facing feature and would require a some engineering effort. Customers have asked to update their instance names similar to their own naming standards.
1 vote -
Show "Versions" gadget by default
When a new user accesses the CMS for the first time, they must manually add the "Versions" gadget to the UI. Can we have that included by default?
1 vote -
Manage Permissions screen should use API Key Name instead of ID
When setting content access rights for an API key, the UI should use the API key's "Name" field instead of the ID field, to make it more user-friendly.
1 vote
- Don't see your idea?