yesterday I spent nearly 3 hours solving consequences of a bug in Replace Design action.Problem is that Replace Design action removes option “Prohibit design refresh or replace to modify” from design’s elements.
Here are steps to reproduce the issue:
create a test teplate
create a folder in the test template and check option “Prohibit design refresh or replace to modify”
create a database from the template
check that option “No Refresh” is correctly set on the folder in the database
note: …Results:
Notes version V65_M1_04032003NP ... BAD (option is not set)
Notes version 653HF719 ... OK (option is set)
create another database from blank design and then replace design of this database with the test template
check that option “No Refresh” is correctly set on the folder in the database
note: …Results:
Notes version V65_M1_04032003NP ... BAD (option is not set)
Notes version 653HF719 ... BAD (option is not set)
Could someone test this on Notes version 7 and possibly report the bug to IBM?
It’s not quite so clear-cut which behavior is “BAD”. Suppose template B inherits from template A, except for one design element in template B which you want to be different from A, so you check “Prohibit design refresh” for that element.
However, when you create NSF files from template B, you don’t want the NSFs to Prohibit design refresh of this element – if you edit the element in template B, you want to update your application databases.
In other cases, this is a design element that maybe you do not want to update in the NSFs during a design refresh because you have some code in the application to customize that design element automatically based on user selections.
That’s why we added an option “Propagate this prohibition of design change” to let you control whether this occurs.
You don’t have to work for IBM to access this forum with the Notes client. There’s a procedure described somewhere on this site, for requesting permission to do it. I have that access automatically so I don’t know how exactly, but I suspect there’s something in the FAQ.
If you still want to work for IBM anyway, we don’t use this forum for recruiting, but since you were the one to bring it up… you can certainly send along your resume and I’ll pass it to appropriate people.
thx for your explanation. It gave me new insight on this problem.
What would you suggest as best solution in following scenario:
a user archives his emails to his archive. It happens that only emails are archived, folders are missing in the archive (I do not know why but it happens time to time) and user wants to correct this.
template from the current user’s mailfile is created and applied to the archive. User’s mailfile is restored from backup and information about which document is in which folder is transmitted to the archive by a script.
Now: In mailfile, user’s folders have set the flag “Prohibit Design Refresh” (default Notes behavior when folder is created by user). However they do not have set the flag “Propagate this prohibition”. As Design Replace does not set the flag “Prohibit Design Refresh” on the user’s folders in archive, these folders will get removed with next design refresh.
