Entry in templating.cfg is not working

Entry in templating.cfg is not working .

Getting error as - Unable to create a new form of type ca/CFIntranet under the branch //cidcsts65dev/default/main/FBU/CFIntranet.This form was not configured for this branch or you do not have permission to access it.

This error is due to wrong entry of catagory in templating.cfg file.

This is my current entry in templating,cfg. - as per Entry.txt (attached)

and branching - as per branching.txt ( attached)

According to branching the entry is wrong.

So there is any limitation that the category name should be at first level under the templadata only and data type in only after the category.

coz If I remove the CFIntranet and put category as - ca and datatype as IndexPage then it works.

I am using here CFIntranet as category because it will remain same for all folders i e. - ca, csa, eng etc and there are total 27 such folders are there. So wanted to keep one entry insted of 27 diff enties .

If I use catagory as ca , cse, eng then there will be 27 different entries. and which coz size limit of templating .cfg file.

So any idea abt the entry for such branching?

Find more posts tagged with

Comments

Ambuj

Entry in templating.cfg is not working .

Getting error as - Unable to create a new form of type ca/CFIntranet under the branch //cidcsts65dev/default/main/FBU/CFIntranet.This form was not configured for this branch or you do not have permission to access it.

This error is due to wrong entry of catagory in templating.cfg file.

This is my current entry in templating,cfg. -

and branching - as per branching.txt ( attached)

According to branching the entry is wrong.

So there is any limitation that the category name should be at first level under the templadata only and data type in only after the category.

coz If I remove the CFIntranet and put category as - ca and datatype as IndexPage then it works.

I am using here CFIntranet as category because it will remain same for all folders i e. - ca, csa, eng etc and there are total 27 such folders are there. So wanted to keep one entry insted of 27 diff enties .

If I use catagory as ca , cse, eng then there will be 27 different entries. and which coz size limit of templating .cfg file.

So any idea abt the entry for such branching?

The branching structure should be like below..

Workarea -> templatedata -> category -> datatype -> datacapture.cfg

Adam Stoller

Entry in templating.cfg is not working .

Getting error as - Unable to create a new form of type ca/CFIntranet under the branch //cidcsts65dev/default/main/FBU/CFIntranet.This form was not configured for this branch or you do not have permission to access it.

This error is due to wrong entry of catagory in templating.cfg file.
...

As was pointed out, and as is documented (somewhere, I'm sure) - you can only have a two-level hierarchy for templating: category, data-type - whereas your directory structure is attempting to impose a three-level hierarchy:

FBU
  CFIntranet
    WORKAREA/
      CFIntranet_wa/
        templatedata/
ca/
CFIntranet/
IndexPage/
                datacapture.cfg
                presentation/ (not shown for other entries)
                data/         (not shown for other entries)
MainPage/datacapture.cfg
SubPage/datacapture.cfg
csa/
CFIntranet/
IndexPage/datacapture.cfg
MainPage/datacapture.cfg
SubPage/datacapture.cfg
eng/
CFIntranet/
IndexPage/datacapture.cfg
MainPage/datacapture.cfg
SubPage/datacapture.cfg

You could collapse, or merge, the second-level with either the first- or third-level (e.g.: "ca_CFIntranet", "csa_CFIntranet", or "CFIntranet_IndexPage"), or merge the first-level with the third-level (e.g.: "ca_IndexPage", "ca_MainPage"), or possibly get rid of either the first- or second-level altogether (assuming that the DCTs for "IndexPage", "MainPage", and "SubPage" are identical accross the differnt boundaries). One way or another though, you have to get rid of one of those levels.

sniv

Thanks a lot for your comments...

So as per provided inputs from both of you ..There are 27 categories going to be come into picture...so is it any problem with the templating .cfg file size or performance?

Once again thanks a lot for your valuable inputs !!

Adam Stoller

Thanks a lot for your comments...

So as per provided inputs from both of you ..There are 27 categories going to be come into picture...so is it any problem with the templating .cfg file size or performance?

Once again thanks a lot for your valuable inputs !!

Different folks have seen different things performance-wise with large templating.cfg files - if you search the forums, you'll see some suggestions for ways to modularize the file - however I'm not sure what difference that makes in terms of performance (I think it's more of a maintenance solution).

Are you saying there are going to be 27 categories? or 9 categories with 3 data-types each? - in either case I don't think it's that bad.

Are all these categories and data-types going to be available on all branches - or are only some going to be available on each branch?

If the latter - you might be able to offset performance issues (if any) by utilizing the branch regex directive (RTM for details)

There are a number of approaches one can take - but a lot depends on the intended usage (e.g.: if your previously shown "super-"category were branch specific, then you could modularize the DCTs such that they called an inline script that took into account the branch name and programmatically provided the actual DCT contents - if that were the case - you would have (from what I gather of your previous posting) one category and three data-types, and possibly 27 to-be-included DCT-snippets.

However, I wouldn't worry about performance issues until you actually notice performance problems - try to solve the design issue first.