Filter DTLs in Rule Definitions

When defining a Rule and adding a Send action I would like to see better filtering on the list of Transforms listed in the UI

1. If the rule is Rule Type = HL7 Message Routing Rule it would seem that the only valid transforms to select are those where the DTL source class = EnsLib.HL7.Message

2. Does it make sense to show deprecated Transforms in the lookup? Many of these classes are formally marked as Deprecated in the class defintion, ie the ones in HS.FHIR.DTL.* but show up in the list. Automatically filtering these would make finding your DTL easier as the list would be more concise.

3. It is common with an implementation to

   1. Define package mapping in %ALL to map the customer specific package. For example we would package=Custom in %ALL.

   2. We then create facility specific implementations following the naming convention Custom.<FacilityName>, for example Custom.FacilityA, Custom.FacilityB, Custom.FacilityC

   3. This means all of the customer specific DTLs will show up in the drop down UI. I think it might be useful if we could define in the Rule a property called Package Filter which would limit the list of DTLs to just those DTLs that %STARTSWITH Package Filter. If I create a Rule with Package Filter=Custom.FacilityC I would only see DTLs that %STARTSWITH Custom.FacilityC.

While these changes would change what is displayed in the lookup they would not prevent you from simply typing the specific DTL you want if it was not found in the list.