Component templates

Pick one of these templates for the defined event. (See the configuration examples for more information.)

<COMPONENT moniker="Hansen.CDR.Building.BuildingApplication">
  <EVENT name="Hansen.CDR.Building.BuildingApplet:BeforeWorkbench" 
   dependprop="ApplicationType.ApplicationType" dependpropval="MT">
    <DATAMINER source="GIS">
      <HANDLER handlerid="HansenGIS" />
      <BINDINGS></BINDINGS>
    </DATAMINER>
  </EVENT>
</COMPONENT>

The next two events are also defined for the Hansen.CDR.Building.BuildingApplication component:

<EVENT name="Hansen.CDR.Building.BuildingApplet:AfterLocationSet" 
 dependprop="ApplicationType.ApplicationType" dependpropval="DONTRUN">
  <DATAMINER source="GIS">
    <HANDLER handlerid="HansenGIS" />
    <BINDINGS></BINDINGS>
  </DATAMINER>
</EVENT>

<EVENT name="AfterLoad" dependprop="ApplicationType.ApplicationType" 
 dependpropval="DONTRUN">
  <DATAMINER source="GIS">
    <HANDLER handlerid="HansenGIS" />
    <BINDINGS></BINDINGS>
  </DATAMINER>
</EVENT>

<COMPONENT moniker="Hansen.CDR.CodeEnforcement.Case">
  <EVENT name="Hansen.CDR.CodeEnforcement.CreateCodeEnforcementApplet:BeforeWorkbench" 
   dependprop="CaseType.CaseType" dependpropval="AB">
    <DATAMINER source="GIS">
      <HANDLER handlerid="HansenGIS" />
      <BINDINGS></BINDINGS>
    </DATAMINER>
  </EVENT>
</COMPONENT>

<COMPONENT moniker="Hansen.CDR.Planning.PlanningApplication">
  <EVENT name="Hansen.CDR.Planning.PlanningApplet:BeforeWorkbench" 
   dependprop="ApplicationType.ApplicationType" dependpropval="AB">
    <DATAMINER source="GIS">
      <HANDLER handlerid="HansenGIS" />
      <BINDINGS></BINDINGS>
    </DATAMINER>
  </EVENT>
</COMPONENT>

<COMPONENT moniker="Hansen.CDR.Project.ProjectApplication">
  <EVENT name="Hansen.CDR.Planning.ProjectApplet:BeforeWorkbench" 
   dependprop="ApplicationType.ApplicationType" dependpropval="MNI,ET">
    <DATAMINER source="GIS">
      <HANDLER handlerid="HansenGIS" />
      <BINDINGS></BINDINGS>
    </DATAMINER>
  </EVENT>
</COMPONENT>

<COMPONENT moniker="Hansen.Property.Address">
  <EVENT name="Hansen.Property.AddressViewerApplet:InitView">
    <DATAMINER source="GIS">
      <HANDLER handlerid="HansenGIS" />
      <BINDINGS></BINDINGS>
    </DATAMINER>
  </EVENT>
</COMPONENT>

For assets, change the component moniker as needed:

<COMPONENT moniker="Hansen.AssetManagement.Sewer.SewerMain">
  <EVENT name="Hansen.AssetManagement.AssetInfoViewerApplet:DetailPage">
    <DATAMINER source="GIS">
      <HANDLER handlerid="HansenGIS" />
      <BINDINGS></BINDINGS>
    </DATAMINER>
  </EVENT>
</COMPONENT>

<COMPONENT moniker="Hansen.CRM.ServiceRequest">
  <EVENT name="Hansen.CRM.TakeACallApplet:SubmittalQuestionnaire" 
   dependprop="RequestType.RequestType" dependpropval="MapTest">
    <DATAMINER source="GIS">
      <HANDLER handlerid="HansenGIS" />
      <BINDINGS></BINDINGS>
    </DATAMINER>
  </EVENT>
</COMPONENT>

For the moniker attribute of the <COMPONENT> element, specify the moniker of the business object that encloses the event that invokes the Data Miner. There should be only one <COMPONENT> element for a given moniker. It can have multiple <EVENT> elements as children. For example, the Hansen.CDR.Building.BuildingApplication component might include events for both BeforeWorkBench and AfterLocationSet.

For each <EVENT> element, use the name attribute to specify the event that invokes the Data Miner. You can use the dependprop and dependpropval attributes to set conditions for invoking the Data Miner. For example, if you specify ApplicationType.ApplicationType as the dependprop and list one or more application types for the dependpropval, then the Data Miner will only be invoked for those application types.

For the <DATAMINER> element, leave the source attribute set to GIS.

For the <HANDLER> element, leave the handlerid attribute set to HansenGIS.