Clarity Studio Development
As a developer with administrative rights, use the integrated
Classic PPMStudio tools to customize your environment. Deploy local configurations and user interfaces that align the application with your exact business processes and information requirements.
You can propagate the objects and attributes that you create to portlets, pages, custom content packages, and the XML Open Gateway (XOG). Your custom configurations automatically carry forward to future versions of
Classic PPM. For example, use Studio to design a new portlet with custom filter options. Enable users to view the portlet data in their choice of a grid or chart including bar, bubble, column, funnel, line, pie, or scatter chart. Portlets dynamically adjust the data in charts and tables that are based on the access rights of the current user.
- When you log in at docops.ca.com, all content appears (including restricted content). However, some of the product documentation is not available in your language. For example, the Studio content is only available in English.
- Be aware of two popularStudioenvironments. Content developers can modify the application using the mainClassic PPMStudio features. Report designers can develop custom reports using the separate JasperSoft Studio application. Be advised that other third-party tools may also use the popular nameStudioin their titles.
Studio Access Rights
As an administrator, verify that Studio developers have the appropriate access rights.
Studio Access Rights
- Administration - Access
- Administration - Studio
Object Access Rights
- Custom Objects Editor
- Object - Create Definition
- Object Administration
Portlet Access Rights
- Portlet Create
- Portlet Definition Editor
- Portlet Definition Editor - All
- Portlet Navigate
- Portlet - View
- Portlet Viewer - All
Portlet Page Access Rights
- Page Definition Editor
- Page Definition Editor - All
- Page Definition Viewer
- Page Definition Viewer - All
- Page - View
- Page Viewer - All
Partition Model Access Rights
- Administration - Partition Models
- System Partition - Administer
Menu Manager Access Rights
- Menu Definition Editor - All
- Menu Definition Viewer - All
Content Add-in Access Rights
- Content Add-Ins - Administer
- Administration - XOG
Content Package Access Rights
- Content Package - Administer
- Content Pack - XOG Access
Install and configure the Document Management System before using content package JAR files built in Studio.
Install or Update Content Add-ins
Developers often require custom content from your choice of new or upgraded add-ins. An add-in is a collection of content that can include portlets, pages, access groups, processes, and jobs. The content in an add-in provides an efficient way to get started with specific functionality in
Classic PPM. The content from an add-in is available to users when the administrator deploys it to your environment.
As an administrator or developer, install and apply updates for each add-in before development starts. After installation, you have an opportunity to review and to accept the changes being delivered in the add-in. This option is not always available. For example, a fix being delivered is installed directly to the database.
If your environment was customized before installing or updating an add-in, note the following points:
- When you apply an add-in, the customization of objects such as portlets and pages in Studio can be overwritten. Your user interface changes.
- You cannot uninstall an add-in.
- To avoid overwriting any Studio customizations, consider what the add-in is going to change before installing or applying it.
Follow these steps:
- Open Administration, and from Studio, click Content Add-ins.
- Click the name of the add-in.The add-in details page appears showing the following columns.
- StatusIndicates whether the add-in item is applied inClassic PPM.Values:
- Not Installed. This value indicates that the items are new to this add-in version or that you did not apply them from a previous add-in version.
- Upgrade Ready. This value indicates modified items that you applied from a previous add-in version and then configured. An update to the item is included in the current add-in version.
- Installed. This value indicates items that are installed.
- TypeIndicates the item type.Values:Object, Lookup, Tab, Query, Portlet, Page, Custom View, Group, Menu, Project, Process, Role, and Job
- IDDisplays the add-in item code, which becomes the ID of the applied add-in item.
- Review each selected item. Accept only those changes you want. Only the items that you select are updated.When the items are selected to be updated, any items that are dependent on the selected items are also selected to be updated.
- Click Apply.
Attribute Value Protection (AVP) Performance Tip
Avoid heavy use of secure subpages and AVP display conditions.
Limit the number of secure subpages. When configuring object views, also minimize your use of the
Use display conditions and secured subpages to protect attribute values on this listAVP setting.
You can secure object subpage views. Each secure subpage results in a sub-query to check security. On the Project List and other large object list views, heavy use of secure subpages combined with AVP settings to enforce secure subpages might reduce performance.