How to create an "old-school" patch (PAT000000000.txt)
1. Create a new OSpace2. In the new OSpace, Orphan objects (or objects containing features) you want to patch/modify3. Modify features in orphans4. Open a script editor window and enter $PatchUtils.Dump('[OSpaceName]') Where [OSpaceName] is the name of the ospace created in step 15. You should then normally find a file named [OSpaceName].txt in the same folder where you created your OSpace. If not, try to do a search in the whole Livelink folder6. Verify that everything is as wanted in the txt file7. Validate that EVERY dependency is listed (ie that if a patch module is not present, it will not crash). See Note.8. Move the file in the livelink patch folder9. Rename the file to something like pat[1. Create a new OSpace2. In the new OSpace, Orphan objects (or objects containing features) you want to patch/modify3. Modify features in orphans4. Open a script editor window and enter $PatchUtils.Dump('[OSpaceName]') Where [OSpaceName] is the name of the ospace created in step 15. You should then normally find a file named [OSpaceName].txt in the same folder where you created your OSpace. If not, try to do a search in the whole Livelink folder6. Verify that everything is as wanted in the txt file7. Validate that EVERY dependency is listed (ie that if a patch module is not present, it will not crash). See Note.8. Move the file in the livelink patch folder9. Rename the file to something like pat[000000000].txt (Don't exceed this number length or LL won't recognize your patch). I suppose this format was meant to be something like pat[yyyymmdd(count)].txtNote: Dependencies made with m{'module_name'} are for the whole patch file. Normally, dependencies are automatically created by the dump script so you shouldn't have to worry about it.How to add Comments:If you want to add comments at the top of your patch, add a feature named Comments in the root object. This feature must either be of type String or Script. If you use String, you're limited to one line. If you choose Script, format it as you want without any preprocessor line nor # starting character.How to make dependencies with other sub-patches:In the root object, you can add fetures named MustInclude and MustExclude. These 2 features must be of type List and contain number of subpatch but honestly, I don't really understand right now how it works. In fact, after taking a closer look to the way the patching script uses these 2 features, I would say that OT has a bug in it since it uses a counter that is never incremented instead of the patch number so as for LL9.5.0.1, don't use it. From what I understand, this should be used in monthly patches but even there, there is no way of using it.How to manually add comments to existing patch:Simply add a line to the patch file which begins with # . Don't forget the space after the # or else your first comment character will be removed.How to make a "hook" on a feature:Name your feature _hook_[featureName]. When the patch will be applied, the existing feature will be called _hook_[FeatureName] and the patched one will be inserted in its place.].txt (Don't exceed this number length or LL won't recognize your patch). I suppose this format was meant to be something like pat[yyyymmdd(count)].txtNote: Dependencies made with m{'module_name'} are for the whole patch file. Normally, dependencies are automatically created by the dump script so you shouldn't have to worry about it.How to add Comments:If you want to add comments at the top of your patch, add a feature named Comments in the root object. This feature must either be of type String or Script. If you use String, you're limited to one line. If you choose Script, format it as you want without any preprocessor line nor # starting character.How to make dependencies with other sub-patches:In the root object, you can add fetures named MustInclude and MustExclude. These 2 features must be of type List and contain number of subpatch but honestly, I don't really understand right now how it works. In fact, after taking a closer look to the way the patching script uses these 2 features, I would say that OT has a bug in it since it uses a counter that is never incremented instead of the patch number so as for LL9.5.0.1, don't use it. From what I understand, this should be used in monthly patches but even there, there is no way of using it.How to manually add comments to existing patch:Simply add a line to the patch file which begins with # . Don't forget the space after the # or else your first comment character will be removed.How to make a "hook" on a feature:Name your feature _hook_[featureName]. When the patch will be applied, the existing feature will be called _hook_[FeatureName] and the patched one will be inserted in its place.
