*Note - Please use textile markup to input code examples in the comments box (e.g. start and end the code sections with @ signs). Click the pencil icon in the word processor to remove the WYSIWYG.
Please submit your ideas on how to improve Cascade Server.
It would be beneficial to have a front-end to configure the LDAP
Authentication and Synchronization Configuration. The current approach,
which presents the XML in a textarea that is too small to actually edit
the file in, makes LDAP configuration difficult. It is easy to miss
configuration options which are required, as well, it is easy to make
mistakes when the configuration gets complex. A front-end for the LDAP
configuration would allow an administrator to set options through a GUI
and would provide some validation and error checking.
When creating dynamic fields in Metadata Sets, there is a DTD link under the Configuration box that users can reference when writing an XML configuration. It would be nice if a link like this would appear next to ANY box that requires XML input (like Workflows, Data Definitions, index blocks, etc).
It would be great to be able to restore data on a site-by-site basis.
For installations in which there are several sites in one installation,
if one site’s data is somehow corrupted, or they have data that needs
to be restored, you have to restore the entire database, which rolls all
sites back to the condition in the restored data. Restoring site-by-site would be ideal.
When an asset that is marked as “should be published” is modified, it should be displayed differently in the left nav until it is published again. This way it is easier to keep track of which assets are “dirty”; and by “dirty” i mean that the last modified time > last published time.
We have users who need to create their own online web based forms. I would like to see the editing tool be given the ability to insert form elements (accessibly, of course).
Instead of refreshing the entire page, use ajax to update publisher status. In addition, possibly include a publisher status for each user at the top right to allow them to keep working while still knowing the status of their last publish.
In the Administrator area of Cascade there is a place to view/download logs. It would be great if we could sort them by date. This would make it easier to find the appropriate logs for support
I would like to attach data definitions to blocks. The metadata sets are usually limited with fields such as no WYSIWYG editor and no date chooser.
I love the fact that I can edit roles but I would like to be able to create my own roles to get more granular with permissions
Allow more than six asset factories to display on the dashboard in the New Content Wizard area, as well as inherit the current folder order of the assets. The current folder order does not seem to translate to the dashboard.
Somehow provide an option to disable TinyMCE on individual pages or sections.
I’ve gotten feedback that it would be very useful to manually order asset factories in the New menu. It also would be great to be able to add separators between groups of items. Maybe have a container be configurable to be a group with a separator or a menu level that must be expanded?
Having a special date/time/date-time chooser in dynamic metadata would make it a lot easier for users to add things like “Original Publication Date” or add more finely granular expiration dates like “Home Page Expiration” and “Section Expiration”.
See CSNEW-253
It would be really cool to have a “tagging” metadata field type or a dropdown that also had a text box to add items. That way, users could add categories as needed, but would still receive a list of all existing categories. The interface could be like the search autocomplete or more like a traditional drop-down menu.
Offer a report in the administration area that helps new Cascade Server organizations explore the system feature set. Each row in the table would be a Cascade feature, number of components in use with an “In use” or “Needs to explore” indicator. Example: Content Type Indexes: count = 0; Need to explore. Offers ability for a project lead to quickly see how in-depth their usage of the product is at any time.
I’d like to see a Menu Block that would provide an easy way to create the most commonly used Menus:
*Note - Please use textile markup to input code examples in the comments box (e.g. start and end the code sections with @ signs). Click the pencil icon in the word processor to remove the WYSIWYG.