Dynamically create your own object's menu

Create you own object's menu items, for any object or any type on Content Server. With a few lines of code you will be able to provide your users with the most appropriate function menu.

In the script you use to create your custom menu, you have access to all the information regarding the object; it is thus very simple to create urls having, for example, the node id among their parameters (${url}?func=ll&objAction=Edit&objId=${node.ID}).

A few common usage scenarios:

•   Reduce the menu size (filter items) for a given group of users
•   Start a workflow having the object as an attachment
•   Execute a request handler, having the object ID among its parameters
•   Update object's properties (Office documents) on the basis of the attached categories
•   Update object's categories on the basis of the object's properties (Office documents)
•   Create, inside container objects such as a folders or projects, documents based on an existing templates (e.g. an offer, a quotation, an inquiry report etc..)
•   Apply a watermark to a document
•   Display information about the object (e.g. a single page where to show: categories, classifications and permissions)
•   etc.

Grid view made easy

Dynamically filter columns to provide users with the most relevant and tailored information. Inject custom columns and set their values with information coming from external systems.

A few common usage scenarios:

•   Hide standard 'size' and 'modify date' columns (e.g. in views with multiple columns, to optimize space usage)
•   Hide standard 'checkbox' column (e.g. to prevent even authorized users from performing multi-items actions)
•   Present in the browse view information coming from a database query result, thus eliminating the need for the creation of custom data-sources and column objects (works together with Manage browse view)
•   Present in the browse view information coming from an external system, thus eliminating the need for the creation of custom data-sources and column objects (works together with Manage browse view)
•   Display columns dynamically (e.g. display a column only if a given category attribute is valued)
•   Change the way columns are displayed (interpret column's values as HTML code instead of raw data)
•   etc.

Inject new column definition to present your data more effectively

In this example we are providing users with access to the documents (invoices) as well as to the folder used to store invoices from the same supplier. Both these columns feature a standard object's menu.

A standard presentation... for custom information

Use the standard Browse View "paradigm" to present your information (not necessarily resident on Content Server, such as ERP records) taking advantage of the default pagination and sorting mechanism, thus breaking down development and maintenance costs

Content Script Extension for UI not only allows you to decide which data to display, but also how it should be displayed, providing users with easy-to-read, easy-to-understand interfaces. Look at the example below where we used weather icons to represent projects' status.

Updating category attributes has never been easier!

Our module gives you unconditional freedom, the only limit is your imagination. For example, including a slider to quickly update documents' categories and related columns, is just a matter of 30 lines of code.

Create domain specific objects without writing Oscript code

Content Server provides several features which allows power users and administrators to model domain specific objects without having to rely on hard core development skills. For example, one could define a generic container folder, apply specific metadata categories and classifications (date, partecipants..) in order to represent a concept such as a "meeting". This approach, though flexible, has its limitations in terms of user experience. In order to gain full control of the whole process, the only effective solution would be to create a new custom subtype of objects in Oscript.

Categories and classifications are great, but whenever you use them to model domain-specific objects you end up fighting with the standard "create new item" dialog, which is all but user-friendly when the object you would like to create is a "meeting" (and not a "folder"). Content Script allows you to define custom "add item" menu entries. By binding a custom "add item" menu to a Content Script you will be able to present users a simplified and tailored "create new object" custom dialog, while under the hood you could be doing a lot more: associating categories and classifications, creating complex folder structures, fine-tuning user permissions, etc. This feature works at its best if used in combination with the "manage form dialogs" feature.

A few common usage scenarios:

•   Limit the object types one can create in a space
•   Provide simplified "new item" dialog
•   etc.

Forms, Forms, Forms

Whenever it comes to collecting information, you will most probably need a form. With Content Script UI Extension you will be able to leverage all the features of our Beautiful WebForms module without having to go all the way and actually create Form objects on Content Server. Forms can be used as primary interface for scripts to run. Being able to build form dynamically means that you can "programmatically" adapt your form to meet at best users needs.

A few common usage scenarios:

•   Collect information to be used in a script
•   Create simplified dialogs to manage documents categories and classification
•   Display custom "create new object" dialogs
•   Create forms to be used as highly-tailored search masks (for example, to filter browse view documents list)
•   etc.

Do it for all of them, please.

Multi Items buttons are an extremely handy feature of Content Server, but one that does not allow for an easy customization. Content Script UI extension allows to alter the appearance of the custom menu by showing or removing items, and also to add completely custom new actions.

A few common usage scenarios:

•   Merge a set of PDF documents in a single document and download it.
•   Perform massive workflow action on multiple documents.
•   Start multiple workflows at once, attaching each document to its own workflow
•   Show a specific action only to specific users
•   Hide standard actions from all users