Webpage with URLs to link straight to DCRs

Hi everyone,

Got a rather newb question to ask:

Is it possible to have a webpage with URLs pointing to specific Teamsite DCRs in contentcentre and if so how is this done?

The aim here is for somewhat of a customized GUI with a sitemap of all CMS-able pages/components to make the navigation to DCRs within contentcentre easier and less confusing for non Teamsite trained users.

Regards, KennethL

Find more posts tagged with

Comments

vaibhav2288

Hi everyone,

Got a rather newb question to ask:

Is it possible to have a webpage with URLs pointing to specific Teamsite DCRs in contentcentre and if so how is this done?

The aim here is for somewhat of a customized GUI with a sitemap of all CMS-able pages/components to make the navigation to DCRs within contentcentre easier and less confusing for non Teamsite trained users.

Regards, KennethL

You can use the URL commands for editing the DCR outside the Content-center.

See below code, it might help you. Change it according to your needs -


<div id="DCR_edit">
 <a href="http://SERVERNAME/iw-cc/command/iw.ccpro.launch_edit_form?vpath=//Server/default/main/Sub-Branch/WORKAREA/Inetpub/templatedata/Category/DataType/data/TestLinkDCR.dcr">
    Link To DCR
 </a>
</div>

Here we have used the command "iw.ccpro.launch_edit_form", for editing the DCR. Use proper vpath.

Thanks...

kennethl

Thanks vaibhav2288 for your reply,

Would I be right to assume that the contentcentre interface will open, prompt the user to login and after that, fast forward right to the DCR?

Would logged in users be able to access subsequent pages via these external URLs without having to login again?

Cheers,

KennethL

vaibhav2288

Thanks vaibhav2288 for your reply,

Would I be right to assume that the contentcentre interface will open, prompt the user to login and after that, fast forward right to the DCR?

Would logged in users be able to access subsequent pages via these external URLs without having to login again?

Cheers,

KennethL

Yes, your both the assumptions are correct.

kennethl

Great... Thanks..

Cheers...

Migrateduser

This also works.

http://SERVERNAME/iw-cc/edit?vpath=//Server/default/main/Sub-Branch/WORKAREA/Inetpub/templatedata/Category/DataType/data/TestLinkDCR.dcr

ISCBorisB

This also works.

http://SERVERNAME/iw-cc/edit?vpath=//Server/default/main/Sub-Branch/WORKAREA/Inetpub/templatedata/Category/DataType/data/TestLinkDCR.dcr

This is IMO how it should be done. Another proposal is an unsupported hack.

I like hacks as much as the next guy but if supported mechanisms exist one should use them.
It will not change without notice, you can get support if something does not work quite
as documented and so on.

Migrateduser_427

This also works.

http://SERVERNAME/iw-cc/edit?vpath=//Server/default/main/Sub-Branch/WORKAREA/Inetpub/templatedata/Category/DataType/data/TestLinkDCR.dcr

Using the this URL, we have made a simplified simi in-context editing tool, where we have a call to the DCR URL invoked by a key press from the preview site for all of the site pages that get output from TS. When the user makes a change and saves, it kicks off a deploy workflow to the preview site.

Even uploading of images, PDFs, etc. can be done via the DCR and get included in the WF for that particular DCR change; the end user never has to navigate through TS directories which saves on training.

P.S. Also, the same is being used to open and edit SP .page files.

ISCBorisB

Using the this URL, we have made a simplified simi in-context editing tool, where we have a call to the DCR URL invoked by a key press from the preview site for all of the site pages that get output from TS. When the user makes a change and saves, it kicks off a deploy workflow to the preview site.

Even uploading of images, PDFs, etc. can be done via the DCR and get included in the WF for that particular DCR change; the end user never has to navigate through TS directories which saves on training.

P.S. Also, the same is being used to open and edit SP .page files.

This is often called "Surf and Edit" or SnE for short.

Prior to the introduction of SitePublisher, there were few home-grown implementations on the concept in TS.
I remember some Cruise Company (Royal Caribbeans?) presenting a Demo of such implementation on GearUp 2006.

Nowadays SitePublisher has elaborated SnE out of the box.