4 results found
-
CMS 13 - DAM Asset Picker Showing Multiple CMP instances
In CMS 13 with CMP DAM integration, the DAM Library Picker currently prompts users to manually select a CMP instance when they have access to multiple instances. For users such as partners who frequently work across multiple instances, this creates unnecessary friction and interrupts the workflow.
The expected behavior is that CMS should automatically open or restrict the picker to a specific CMP instance based on its configuration, eliminating the need for manual selection. The DAM Library Picker already supports targeting specific instances (e.g., via instanceIds), but this capability is not currently utilized or exposed in the CMS integration.https://docs.developers.optimizely.com/content-marketing-platform/docs/library-picker#pass-options-in-url
…
2 votes -
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 -
Automated way of copying database and blobs to a lower environment in CMS SaaS
We need a way of deploying the current content and blobs from our production environment to a lower environment of our choosing in our CMS SaaS instance. We should have the option to completely replace all of the data that is currently in the lower environment as well.
8 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
- Don't see your idea?