I have performed the following test on 6.0.1, and am VERY SURPRISED at the result:
-
Created a new application DB with a “large design”
-
Copied the db (using Notes-copy) to an NTF-file.
-
Made a small design-change to the NTF (background color on a form).
-
Set up the appl.db to inherit design from the NTF, and flag the NTF as Single Copy Template.
-
Run design-task on the server.
-
Compact the application db.
There is no doubt that SCT “works” - I can see that from the size of the DB - but it is the OLD design that is being used:
-
The background color on old and new documents made with the form is the OLD color.
-
If I open the application DB in the designer, I see the new color on the form (the color on the NTF), but if I preview it - I get the OLD color!
This is not the behavior I was expecting!! Why isn’t the NTF-design being used? Where is the design that IS being used?
Furthermore, I can’t see any “flag” anywhere on the application DB that SCT is in effect.
Subject: The doc suggests some other steps
We tried this:a) Create a Template “MasterBig” (MB)
b) Make a copy of it into MasterSCT (SCT)
c) Let SCT inherit its design from (MB) !!!
d) Flag SCT as Single Copy Template
e) Apply SCT as Template to production
f) Design/Compact etc.
Changes are only to be applied to MB.
They are transported nicly to production
Hope that helps
Subject: RE: The doc suggests some other steps
My comment posted here an hour ago was incorrect…
(To those who may have read it, it “worked” becuase I had turned the SCT-flag off!)
Subject: RE: The doc suggests some other steps
Sorry Stephan … I tried your suggested set-up, but it is not working as you described.
I can update SCT’s design by refreshing design from MB, but I have found no way of getting this design to be “active” in production.
I don’t know which documentation you are referring to, but the Release Notes indicate that the design in SCT is not supposed to be changed.
SCT seems to be a space-saver only, not a mechanism to simplify implementation of design changes.
Subject: RE: The doc suggests some other steps
Hi Per,
it’s a bit strange. What worked in our case: manual design refresh on the sct from the “master” template. Then the design process does the rest…
How about your side?
stw
Subject: RE: The doc suggests some other steps
Stephan,
I am not able to get it to work as you say.
I do a manual “refresh design” on the SCT-template from the “master” template. This works (of course).
Then I load the design task (“load design” on the server console). I see messages that it is updating the form’s design.
But when I USE the form (either by creating a new document or opening an existing one), it is the OLD design that is used.
AND - if I open the application DB in the DESIGNER, then I see the NEW design on the form, but if I PREVIEW the form in the Notes Client, I get the OLD design.
I know this sounds impossible, but it is happening. There is some cache’ing here.
I have not tried every possible combination of re-starting server/client -only some of them.