The Partner Community Manager CM_CoreProcess has hard coded typing maps which limits our ability to extend functionality of the framework

The latest version of PCM comes with the typing map list in CM_CoreProcess hard coded. This means adding, removing and updating the typing list requires modification of a built in process. Not only will this BP be overwritten in future losing all changes but it also means any changes would require a full regression test of all data flows as CM_CoreProcess is central to all PCM processing.

This should be a data driven value where it can be pulled from a location outside of the code itself. A property file holding the typing list seems like an easy solution to this.

CM_CoreProcess Original
========================================
<operation name="GetTypingMaps">
    <participant name="TypingService"/>
    <output message="TypingServiceTypeInputMessage">
        <assign to="required_parmlist">SENDERID RECEIVERID DOCTRANS</assign>
        <assign to="typing_maplist">CM_Typing_EDI CM_Typing_EDIFACT CM_NoRoutingFound</assign>
        <assign to="validate_input_against_dtd">NO</assign>
        <assign to="PrimaryDocument" from="/ProcessData/PrimaryDocument/@SCIObjectID"/>
        <assign to="." from="*"/>
    </output>
    <input message="inmsg">
        <assign to="." from="*"/>
    </input>
</operation>

CM_CoreProcess Updates
========================================
<operation name="GetTypingMaps">
    <participant name="TypingService"/>
    <output message="TypingServiceTypeInputMessage">
        <assign to="required_parmlist">SENDERID RECEIVERID DOCTRANS</assign>
        <assign to="typing_maplist" from="sci-get-property('pcm_custom_props','TYPINGMAPLIST')"/>
        <assign to="validate_input_against_dtd">NO</assign>
        <assign to="PrimaryDocument" from="/ProcessData/PrimaryDocument/@SCIObjectID"/>
        <assign to="." from="*"/>
    </output>
    <input message="inmsg">
        <assign to="." from="*"/>
    </input>
</operation>

Create or setup in B2B Customization UI 
pcm_custom_props.properties
========================================
## Space seperated of list of typing maps that PCM will use
TYPINGMAPLIST=CM_Typing_EDI CM_Typing_EDIFACT CM_NoRoutingFound

Include a cache refresh BP to refresh the values on demand
=================================================================
<process name="ECG_CACHE_REFRESH">
    <sequence name="Cache Refresh">
        <operation name="Refresh pcm_custom_props">
            <participant name="CacheRefreshService"/>
            <output message="Xout">
                <assign to="cache_type" from="'properties'"/>
                <assign to="cache_name" from="'pcm_custom_props'"/>
            </output>
            <input message="Xin"/>
        </operation>
    </sequence>
</process>