What does prune-missing-files suppose to do?

This attribute was added to templating.cfg to enable pre 6.x kind of filtering - i.e. check if datacapture.cfg exists in the IFS. By default only templating.cfg is parsed to create a list of available Templates/Forms.

... Per Interwoven release notes they said it is suppose to enable customers to enable availabe forms filtering but I am not seeing that...

Not sure what exactly you are asking. If you can explain a little about what you are trying to achieve and how, maybe somebody can help.

Dwayne

That attribute is designed to re-enable the old 5.5.2 (and earlier) logic used to determine which categories and types should be shown to the user when they choose to create a new DCR.

The default behavior (and the only behavior available in TS 6.0) is to base the list of categories and types exclusively on the regex pattern provided in templating.cfg. Overriding this, by setting prune-missing-files="t" should add the extra logic of verifiying that the correct directory structure exists under templatedata in the current branch before showing a given data type to the user.

--

Current project: TS 5.5.2/6.1 W2K

Here's my problem. When I go to ccstd the new forms portlet lists all my forms per category/type but not all the categories have datacapture.cfg files in them. These categories that do not have datacapture.cfg files in them I don't want to show up in my new forms portlet, but they are.

Here's a sample of my templatedata directory:

templatedata
aboutCountry_CT (this category does NOT have a datacapture.cfg)
cwcCommon_CT (this category has a datacapture.cfg)
financialSecurity_CT (this category does NOT have a datacapture.cfg)

but all aboutCountry_CT and finacialSecurity_CT DCTs are showing up in the new forms portlet and I don't want that. I only want the forms to show up that have a datacapture.cfg file.

I was hoping that prune-missing-files was my solution to this. Am I wrong?

Thanks,
Dustin

Senior UI Designer
COUNTRY Insurance & Financial Services

How did you use this attribute in your templating.cfg ? Can you post your templating.cfg (or a snippet of it)?

I recall reading somewhere that there was a documentation error regarding this tag.

Disclaimer: I have not tried/tested this attribute myself.

This was a fix in TS 6.1 SP1. Although you didn't mention in your previous posts, I assume you have installed SP 1 ?

Here is a snippet of my templating.cfg file

<templating prune-missing-files="t">
<category name="aboutCountry_CT">
<locations>
<branch vpath-regex="/default/main/Audrey|/default/main/CountryPassportProd|/default/main/CorePassport|/default/main/Integration|/default/main/Release3"/>
</locations>
<data-type name="MD_Base" dcr-type="iwov">
<viewoptions actionlist="save; saveas; settings;"/>
</data-type>
<data-type name="CN_News" dcr-type="iwov">
<viewoptions actionlist="save; saveas; settings; generate;"/>
<presentation>
<template name="CN_News_XML.tpl" extension="xml">
<locations>
<branch vpath-regex=".*" preview-dir="/">
<directory dir-regex=".*"/>
</branch>
</locations>
</template>
</presentation>
</data-type>
</category>
<category name="cwcCommon_CT">
<locations>
<branch vpath-regex="/default/main/Audrey|/default/main/CountryPassportProd|/default/main/CorePassport|/default/main/Integration|/default/main/Release3"/>
</locations>
<data-type name="MD_Base" dcr-type="iwov">
<viewoptions actionlist="save; saveas; settings;"/>
</data-type>
<data-type name="CN_News" dcr-type="iwov">
<viewoptions actionlist="save; saveas; settings; generate;"/>
<presentation>
<template name="CN_News_XML.tpl" extension="xml">
<locations>
<branch vpath-regex=".*" preview-dir="/">
<directory dir-regex=".*"/>
</branch>
</locations>
</template>
</presentation>
</data-type>
</category>
<category name="financialSecurity_CT">
<locations>
<branch vpath-regex="/default/main/Audrey|/default/main/CountryPassportProd|/default/main/CorePassport|/default/main/Integration|/default/main/Release3"/>
</locations>
<data-type name="MD_Base" dcr-type="iwov">
<viewoptions actionlist="save; saveas; settings;"/>
</data-type>
<data-type name="CN_News" dcr-type="iwov">
<viewoptions actionlist="save; saveas; settings; generate;"/>
<presentation>
<template name="CN_News_XML.tpl" extension="xml">
<locations>
<branch vpath-regex=".*" preview-dir="/">
<directory dir-regex=".*"/>
</branch>
</locations>
</template>
</presentation>
</data-type>
</category>
</templating>

Senior UI Designer
COUNTRY Insurance & Financial Services

Sorry...Yes, I have installed SP 1.

Senior UI Designer
COUNTRY Insurance & Financial Services

You might want to look at the templating6.0.dtd for the prune-missing-files attribute.

Your templating.cfg file refers to the new 6.0 DTD ?


<!DOCTYPE templating SYSTEM "templating6.0.dtd">

TS 6.1, SP1 on W2K.
From my testing for this attribute, it appears that it checks for the presence of the (category and data-type) directory not datacapture.cfg.
If removing the directory is not an option, i don't know how you can achieve this.
But maybe i missed something.
Please post if you find a solution as we have similar issue.

Thanks.

Rishi Athalye
TeamSite 5.5.2>>6.1 on W2K

That was want I was hoping wasn't the case and that is what I have seen. That is that it looks like it check for a category and type not for a datacapture.cfg.

In my environment I can not remove the category and type and was looking for it to check for the datacapture.cfg file instead because I can and have removed the datacapture.cfg.

Senior UI Designer
COUNTRY Insurance & Financial Services

Let me ask one more thing. Am I the only one out there that has DCRs in categories and datatypes within a workarea that editors and authors are not allowed to modify with a DCT?

Because unless theres a work around for this the New Forms portlet is going to be useless to my user because it is going to list DCTs/forms that aren't even there.

Senior UI Designer
COUNTRY Insurance & Financial Services

If you want to restrict certain users\roles from accessing certain templates...
maybe you can use the allowed tag. which lets you set an ACL to specify which users can or cannot use a specific
data type.
check the templating developer's guide.

Thanks.

Rishi Athalye
TeamSite 5.5.2>>6.1 on W2K

It's not a user or role that I need to restrict for using them. It's everyone. I have sets of DCRs in my workareas that no one can/should modify.

Senior UI Designer
COUNTRY Insurance & Financial Services

How about restricting the role to MASTER so at least no business users can acces it.
You could also choose to allow only a test user that you create for this purpose.

Rishi Athalye
TeamSite 5.5.2>>6.1 on W2K

The problem with that is that these DCRs are editable in other WAs. These categories and types are brought down into the WAs other than the creation WA via a get latest from staging.

So for example if I have a category and type with DCRs in WA1 and I stage that content. Then in WA2 I do a get latest. This brings all of the categories and types that I staged from WA1 into WA2. Thus the New Forms portlet list in WA2 two sets of forms. WA2's forms and now WA1's forms. I don't want WA1's forms to show up under WA2's forms.

Dustin

Senior UI Designer
COUNTRY Insurance & Financial Services

Migrateduser

With this prune thing, does it check for the existence of the type directory itself or does it check for the existence of a datacapture.cfg within that directory?

Oh! sorry. I had a post for exactly similar type of situation but not found a solution...
http://devnet.interwoven.com/forums/cgi-bin/showthreaded.pl?Cat=&Board=PRODUCTS_TEMPLATING&Number=38148&page=&view=&sb=&o=&vc=1#Post38148

Rishi Athalye
TeamSite 5.5.2>>6.1 on W2K