Adding a tab to CCPro 6.7.1

On our current production environment (TS6.5 SP3 on Unix), we have added a tab to the CCPro view (in addition to the default Content, Workflow and Administration tabs). We've recently upgraded or development environment to TS6.7.1, and although all of our GUI customizations appear to be there, our customized tab isn't appearing. Before the upgrade of our development environment, the customized tab was there.

Has the syntax for adding a tab changed in this new version?

Thanks in advance for any leads.

~khan

Find more posts tagged with

Comments

gzevin

On our current production environment (TS6.5 SP3 on Unix), we have added a tab to the CCPro view (in addition to the default Content, Workflow and Administration tabs). We've recently upgraded or development environment to TS6.7.1, and although all of our GUI customizations appear to be there, our customized tab isn't appearing. Before the upgrade of our development environment, the customized tab was there.

Has the syntax for adding a tab changed in this new version?

Thanks in advance for any leads.

~khan

I guess you need to review the new syntax ('cause it did indeed change - not dramatically, but now they are custom roles and the need to cater for that). I am not sure why this should have affected the custom tab, but I'd definitely triple check your syntax against the new one, as you might have been restricting the access based on the role, etc, etc.

RonH

link id="deploy_edition.link"
label="Deploy edition"
description="Deploys the selected edition to a webserver"
url="/iw-bin/wdpro_menu.ipl/deploy.cgi"
target="_blank"
windowFeatures="scrollbars=yes,resizable=yes,width=800,height=600"
/>
link id="export_branch.link"
label="Export edition"
description="Exports the current branch to another teamsite server"
url="/iw-bin/wdpro_menu.ipl/export_script.ipl"
target="_blank"
operationID="cu.ccpro.export_branch.op"
windowFeatures="scrollbars=yes,resizable=yes,width=800,height=600"
/>

Here are 2 examples of how the new syntax look. The first example is shown to everybody in 6.7.1 since it lacks an operationID. This is what differs from 6.5. I believe you always had to specify an ID and assign that id to a role in roles_custom.xml. In 6.7.1 roles custom.xml is gone and replaced with userops_custom.xml.

The 2nd example is a menu item with operationID in 6.7.1. If you define a operation description in userops_custom.xml like this:

operation description="export_branch_menu_item"
display-name="export_branch"
id="cu.ccpro.export_branch.op"/>

...then you can assign this menu item to a role in the admin panel, under custom operations.

I am not 100% sure it works the same with tabs this way, but I assume it does.

Hope this helps.

khan

Thanks both for your replies. I didn't get notified that I even got replies to my post, and I just remembered I posted this. I'll try out your suggestions and let you know how it goes.