How to minimize the maintenance cost of the customization of a TKU pattern? What is the best practice?

Version 2

    This document contains official content from the BMC Software Knowledge Base. It is automatically updated when the knowledge article is modified.


    BMC Discovery


    BMC Atrium Discovery and Dependency Mapping


    BMC Atrium Discovery and Dependency Mapping


    How to minimize the maintenance cost of the customization of a TKU pattern? What is the best practice?


    There are 3 ways to customize a TKU pattern

    1. edit an existing TKU pattern (no new pattern added)
    3. disable a TKU pattern and replace it with a new custom one (different name)
    5. leave the TKU patterns activated and create a new custom pattern that triggers on nodes created by the TKU. 
    About option 1:
    It is frequently chosen by customers. It's faster and if you don't change the versions of the pattern/modules/definitions, it should not lead to a conflict at next upgrade. However, each TKU upgrade will override your customizations and you will have to merge your code into the new TKU code. This merge will allow you to take advantage of the next RFE and bug fixes but it may require more maintenance and it has to be done after each upgrade. 

    About option 2:
    This could lead to some dependencies issues. Once the deactivation is done, you can add a new custom pattern (different name/version) to replace the one that you deactivated. The next TKU upgrades won't override your customization, you will be free to merge (or not) your code into the TKU code and you can do that when you want (not necessarily after each TKU upgrades). However, you will have to deactivate the TKU pattern after each upgrade and you may have to adapt your customization to the new code (especially in case of imports). 

    About option 3:
    It removes the risks of dependency issues at TKU upgrade and reduces the maintenance cost. The new pattern can modify the nodes created by the TKU, add new attributes, create new relations, etc. It can also change/delete the attributes/relations created by the TKU pattern but this information can have an impact on the other TKU patterns that use it. As long as this risk is correctly managed, this option is probably the best one. 


    Article Number:


    Article Type:


      Looking for additional information?    Search BMC Support  or  Browse Knowledge Articles