GeoEvent Processor - Make outputs aware of coded value domains

Idea created by tmichael81 on May 29, 2015
    Reviewed
    Score50
    • GBLee2
    • mleibert
    • tmichael81
    • rawhousers
    • ken.carrier

    I am currently using GeoEvent processor to send an email when a feature (leak point) is created.  Certain fields in the source feature use coded values for drop-downs :

     

    leak_type ( type: esriFieldTypeDouble , alias: leak_type , editable: true , nullable: true , Coded Values: [1: Leak] , [2: Break] , [3: Other] )

     

    In the email output settings, I am using the GeoEvent field to show the value in the email (Leak Type: ${leak_type}).  The issue is that the Code value is sent in the email, rather than the Description, so the output looks like this:

     

    Leak Type: 1.0
    Pipe Condition: 5.0
    ...etc.

     

    It would be great if the GeoEvent processor was 'domain-aware' and was able to send the Description for field values.  Or, provide an option to let the user choose to send the Code or Description.