What is best practice for configuring Conflict of Interest?

[matthew somers]

I have a requirement to add/edit the conflict types in conflict of interest.  In the docs, it just describes editing flows in flow designer, but it does not talk about the best practice for scaling conflict types.  I realize they are just the subcategories in the Conflict of Interest category in Compliance Practice Area, but there are more scripts in the background that won't work with the newly added subcategory conflict types.  In the OOB record producer, there is one variable set that contains all variables and 5 or 6 Client Scripts.  Most of the script includes/constants for Conflict of Interest that are called in the client scripts are SNC Read-only.  This seems limiting as there is no way to scale the conflict types via system property or some sort of table.  The constant script is just setting the 3 demo conflict_types OOB.

Has anyone successfully added/customized conflict types for the LSD COI process?  I would like to have something scalable and not recreate the wheel of the whole COI scope.

[AS2023]

@matthew somers , most of their new applications call script includes which are extended from the SNC Read-only ones, I'm not sure why they didn't configure it the same way - they were created in 2020 so that kinda explains it. 

Although I haven't really checked the details yet, the application looks pretty simple to me. Did you change the sources (client scripts etc.) where the script includes are called or just left them alone and created new ones calling the child script includes?

[matthew somers]

@AS2023 - yes, I copied the client scripts and refactored them to the requirements as necessary.  Then extended the SNC script includes to override what I needed.