Restricted access to the presentation templates.

Hi

This may be a fundamental question .

I am using two tpls (preview_staging.tpl & generate_production.tpl)
[color=#333333]for a particular data type. The tpls uses different database connectivity .
I want to restrict the users from using the tpls[/color]

For example , author’s can use only preview_staging.tpl
While the editors can use the preview_staging.tpl & generate_production.tpl
I tried with allowed tag .. it will only help to restrict the data type.

Any explanation is helpful

Vin

Find more posts tagged with

Comments

moonkhanna

use formapi in your DCT to get the role of the user and accordingly set the PT for the user automatically.. User should not be able to select a PT of his choice in that case.. there is no simple or direct way of accomplishing this..

lisadeveloper

Does anyone else know about this?
I'm looking at an Interwoven Education manual (TeamSite 6.5 FormsPublisher Development, p.59) that states "<allowed> can optionally be used in a data-type or template element, to control access based on a user's role and/or username". So it sounds like you should be able to restrict access to PTs but I haven't had any luck yet.

ISCBorisB

Does anyone else know about this?
I'm looking at an Interwoven Education manual (TeamSite 6.5 FormsPublisher Development, p.59) that states "<allowed> can optionally be used in a data-type or template element, to control access based on a user's role and/or username". So it sounds like you should be able to restrict access to PTs but I haven't had any luck yet.

<allowed> Tag is an optional sub-element of several DCT Instance Tags.

This Tag allows Template Developer to specify which contributors can or cannot use a specific instance to enter data into
particular DCR Item(s), that's it. It has no direct relation to PT or PT access rights.

What exactly is the problem you are trying to solve?

lisadeveloper

I want two presentation templates available for the one data capture type but have one of the PTs available to everyone and restrict access to the the other PT to only specific people.

I'm referring to using the <allowed> tag in templating.cfg to control access to data-types and templates, not within a DCT. It works fine for data-types, but when you try and restrict access to a presentation template, those restrictions will apply to the whole data type instead of just the PT.

The example given in the manual is:


<data-type name='careers'>
  <allowed ...>  
  <presentation>
    <template name='jobDesc.tpl' extension='html'>
    <allowed ....>

ISCBorisB

I want two presentation templates available for the one data capture type but have one of the PTs available to everyone and restrict access to the the other PT to only specific people.

I'm referring to using the <allowed> tag in templating.cfg to control access to data-types and templates, not within a DCT. It works fine for data-types, but when you try and restrict access to a presentation template, those restrictions will apply to the whole data type instead of just the PT.

The example given in the manual is:
<data-type name='careers'>
  <allowed ...>  
  <presentation>
    <template name='jobDesc.tpl' extension='html'>
    <allowed ....>

According to templating6.0.dtd optional <allowed> sub-element belongs to the data-type Tag only.

Seems like you can not do what you want from the templating.cfg alone. Perhaps you can consider a workflow with the combination
of CGI Task (or WF Instantiation Form) to present user-dependent choice of available Presentations plus External Task(s) to generate
your assets accordingly