How to fix Deployment Analyzer so that the On Demand ReleaseOps Pipeline Actually Works

[Jon G Lind]

The initial versions of ReleaseOps contained a Deployment Analyzer rule meant to be used as an example of how you could allow on demand deployments of updates that are deemed less risky due to their contents.  The samples are only meant to be an example and the tool can be expanded to check for a variety of conditions.

The initial example was to allow on demand deployments only for catalog item changes.  However, the list of allowed tables was so small that it was almost impossible to create a catalog item change that only referenced sc_cat_item or fx_price.  This will be fixed in Brazil, but in the meantime it's an easy fix.

We need to change the Deployment Analyzer Rule Definition and give it a more robust set of catalog related tables.

1. Navigate to Deployment Analyzer > Rule Definition

2. Open the record for Contains Catalog Item

3. Change the Tables variable to be the following: 

fx_price,io_set_item,item_option_new,item_option_new_set,question_answer,question_choice,question_regex,sc_cat_item,sc_cat_item_catalog,sc_cat_item_category,sc_cat_item_composite_producer,sc_cat_item_guide,sc_cat_item_producer,sc_cat_item_user_criteria_mtom,sc_cat_item_user_criteria_no_mtom,sc_catalog,sc_catergory,sc_item_option,sc_item_option_mtom,sc_multi_row_question_answer,sys_filter_option_dynamic

That's it.  The next time the On Demand ReleaseOps pipeline evaluates whether the update only contains catalog item related changes it should work.  And a reminder: this is just an example.  You may have a completely different set of policies, but hopefully this will get you off on the right foot.