Specifying monikers and mappings

If your GIS layers do not all use the same attribute as a primary key, you can also specify an object moniker or a GIS mapping to get the right records from the Infor Operations and Regulations database.

If you specify a moniker, this will be used along with the GIS key to get the correct IPS key from the sync integration records, such as using a GIS object ID and the moniker Hansen.Property.Address to get an address key.

The other option is to use one of the GIS synchronization mappings that you have defined in Infor Operations and Regulations. Each GIS mapping associates components in Infor Operations and Regulations with layers in the GIS, such as mapping the Hansen.Property.Address component to an Addresses layer.

To configure either of these options, open the GIS configuration and browse to the EVENTS node for the rhythm-civics-address-parcel-selector-mixin applet. You will need to modify the options for different events depending on whether you're working with address or parcels.

Addresses

For addresses, modify the options for the address-attribute-mapper and address-join-attribute-mapper events. This table shows the default values of the options that you will modify:

id value
in <%= address_location_line_1 %>, <%= address_location_line_2 %>, <%= sync_key_field %>
out locationLine1, locationLine2, syncKeyField

This table shows how to modify these values to use a moniker:

id value
in <%= address_location_line_1 %>, <%= address_location_line_2 %>, <%= sync_key_field %>, <%= sync_moniker_address %>
out locationLine1, locationLine2, syncKeyField, syncMoniker

This table shows how to modify these values to use a GIS mapping:

id value
in <%= address_location_line_1 %>, <%= address_location_line_2 %>, <%= sync_key_field %>, <%= sync_mapping_address %>
out locationLine1, locationLine2, syncKeyField, syncMapping

Parcels

For parcels, modify the options for the parcel-attribute-mapper event. This table shows the default values of the options that you will modify:

id value
in <%= sync_key_field %>
out syncKeyField

This table shows how to modify these values to use a moniker:

id value
in <%= sync_key_field %>, <%= sync_moniker_parcel %>
out syncKeyField, syncMoniker

This table shows how to modify these values to use a GIS mapping:

id value
in <%= sync_key_field %>, <%= sync_mapping_parcel %>
out syncKeyField, syncMapping

Exposing the endpoint

For this to work you must also expose the Rest Services endpoint that will be used. In the Portal configuration, select the Security > Service Model Whitelist > Allowing Models node. Add a child Model node with these attributes:

  • Name: Infor.PublicSector.Services.GIS.PrimaryKeyField
  • Http Method: Get