Hi,
How should I name my custom patch for Content Server 16 (i.e. what patch number should I assign)?
Is there some kind of registry where I should reserve a number?
Thanks
Uldis
eLink : Custom patch nameCustom patch name Posted byŠilovs, UldisOn 01/20/2017 03:06 AM Hi, How should I name my custom patch for Content Server 16 (i.e. what patch number should I assign)?Is there some kind of registry where I should reserve a number?ThanksUldis[To post a comment, use the normal reply function]Forum:Content Server Development ForumContent Server:Knowledge Center CS16
CS16 OScript patches are still the old .txt format.
There is a bit more method to the naming madness… our OT patches all start with the version to which they apply.
i.e. pat100xxxxxxxx for CS10, pat105xxxxxxxx for 10.5 and pat160xxxxxxxx for 16.
Even just knowing that should help you pick a numbering scheme that won’t be clobbered by the official goods.
AK
From: eLink Entry: Content Server Development Forum [mailto:development@elinkkc.opentext.com]Sent: Friday, January 20, 2017 9:02 AMTo: eLink RecipientSubject: Re Custom patch name
Re Custom patch name
Posted by Nair, Krishnankutty On 01/20/2017 09:01 AM
Old one off patches started with pat and ended in a . Txt notation.Do not know if 16 has a different format. I usually give it s date time stamp notation and come up with numbers looking like a OT patch . You can even exceed a few.You will probably not get a lot of documentation of registry info because one is not supposed to patch. If your patch or an identically named patch came over that would be fun...If the OT patch was overlaid then what you expected with your code will not work.
Are you using customizations_rt to do this or using pachutils?Ciao, Appu
On Jan 20, 2017, at 2:09 AM, eLink Entry: Content Server Development Forum <development@elinkkc.opentext.com> wrote:
Custom patch name Posted by Šilovs, Uldis On 01/20/2017 03:06 AM Hi, How should I name my custom patch for Content Server 16 (i.e. what patch number should I assign)?Is there some kind of registry where I should reserve a number?ThanksUldis[To post a comment, use the normal reply function]Forum: Content Server Development ForumContent Server: Knowledge Center CS16
Custom patch name
Posted by Šilovs, Uldis On 01/20/2017 03:06 AM
[To post a comment, use the normal reply function]
Forum:
Content Server Development Forum
Content Server:
Knowledge Center CS16
Topic:
As a long-time technical partner, we write so many patches that we have a lengthy SOP for creating, distributing, testing, posting and release noting patches. We use the ranges of pat60###, pat85###, and pat80###; each range having different goals. Comments in the patch detail what versions of CS, the module, the bug and what the goal is for the patch. The longer your customizations are being used, obviously, the more chance you'll need patches of some kind or another. Having a standard procedure will reduce confusion.
However, with the release of CS 16, we had to make changes to how we write patches. Here's my CTO's explanation of what's different:
There are lines in a patch created with a Livelink 9.7.1 environment that cause issues on a CS 16 instance. In 9.7.1, a global object is automatically created and it gets added to the patch. This object messes with CS 16. If you’re using 9.7.1 to create a patch, you have to delete the global object before creating the patch. The object is not created in CS 10+.
I hope that helps.
Tammy Jakubowski
You should be aware that the patches are loaded in alphabetical order.
Hans
From: eLink Entry: Content Server Development Forum [mailto:development@elinkkc.opentext.com]Sent: Freitag, 20. Januar 2017 09:10To: eLink RecipientSubject: Custom patch name
Thank you all for your input!