erp5_upgrader: TemplateTool_checkCategoryNameConsistency constraint now runs...
erp5_upgrader: TemplateTool_checkCategoryNameConsistency constraint now runs only one activity per object susceptible of being updated, instead of one per object and per declared change. This commit divides the number of activities runned by the length of the list returned by Base_getUpgradeCategoryNameList
Showing
Please register or sign in to comment