Approch Needed For : Editing a common DCT present in more than one branch

Hi ,

Using TS 6.1 on Win 2000 SP4 .

I have 3 branches . These 3 branches are for three different Languages .

The structure of each branch is same same having same DCTs .

Now suppose there is a bug in one DCT . So if I have a copy of this DCT in all the branches , then I have to fix the bug of this DCT in all 3 branches .

Is there any approach which I can follow for the Braching Strategy so that i need to fix only one DCT & this changes in DCT will be updated in all the other DCTs of other branches .

Regards
Rohit pathak

Find more posts tagged with

Comments

ravio

You could have one more branch called dev (or whatever you prefer)
And you could set up a deployment in OD in such a way that it picks up the DCT you fixed in dev and deploys it to a number of branches which use it.

If the branching structure you use is fairly complex, you will need a map of branches which use a particular DCT etc.

Migrateduser

Create a master template branch and copy all the common templates across all the 3 branches. And in each DCT template in the 3 branches use an inline script that reads from the master DCT templates.

Bjorn

I'd use the open deploy suggestion by ravio. You could also set up a workflow or more generic automation that would update all the "children" DCTs when the "parent" is updated. But that's just me.

I also wanted to take the opportunity to rip on the product for calling itself an enterprise solution when (at least in terms of formspublisher) it's a compartmentalized, branch-based solution which could only be considered "enterprise" because it's a webapp and allows a bunch of users.

Of course, this has nothing (and everything) to do with your question, but I couldn't resist.

nipper

You can also make the DCT basically a pointer to a master DCT located somewhere else (iw-home). You can use an inline to reference it.

jbonifaci

You can also make the DCT basically a pointer to a master DCT located somewhere else (iw-home). You can use an inline to reference it.

I believe that's what batasari was trying to say.

I would recommend doing this as well. Although I would put the xml for the DCT somewhere in beneath iw-home/custom and have your inline read it from there.

~Jeff

Adam Stoller

You also might want to look at [thread=7019]this post[/thread] which documents a feature request for making this, IMO, a lot easier. Won't help you in the here-and-now, but the more customers who sign up for it, the better chance it has of getting implemented...

gzevin

I believe that's what batasari was trying to say.

I would recommend doing this as well. Although I would put the xml for the DCT somewhere in beneath iw-home/custom and have your inline read it from there.

~Jeff

inline is a good approach, in general. However there could be some performance issues, so, IMO, the ideal approach could be -

using inlines to build a DCT (especially if there is a lot of pre-processing/DB interaction to be done).
Test/QA, etc.
Run a preprocessing script to build DCTs in an 'admin' branch
OD them to respective sub-branches

At the moment we are running inlines, and I saw some performance issues already

sureshm

Hey Rohit,
I feel what Batasari has said is an easy approach. Since you have three branches and all the branches has the same DCT, do this:

Create a master template branch. And make an XML file that will contain all the items which are common in your DCTs in all the three branches. Now use and call an ipl program from your DCTs in the three branches. This ipl program should parse the XML file of the master template branch and should include all the items to your current DCT.

May be this would help you out...

bye
sureshm

rohitspathak123

Hi sureshm / Batsari

Pls let me know ..performance wise ..is it wise to use

Regards
Rohit Pathak