Adding agency fields

In addition to adding and removing Infor Operations and Regulations fields to your mobile views, you can add fields for agency-defined data.

For example, an agency has added two custom fields to the Case Inspection InfoViewer in Infor Operations and Regulations. The # of Complaints field specifies the number of calls the county has received regarding a vacant property, and the County Code field specifies the code section that applies to the complaints. The data for these fields is stored in an agency table called InspectionDetail, which is linked to the inspection record through the inspection key.

The agency can add the same two fields to the inspection viewer in the mobile app. The process involves two main steps.

  1. In the Rest Services configuration, the appropriate models must be extended to handle the agency data.
  2. In the Mobile configuration, the agency fields must be added to the inspection view.

These steps assume that the agency table has been defined in Infor Operations and Regulations, and the agency business object has been generated. If you're using a stand-alone installation of Rest Services, also be sure to copy the Enhancement folder from Infor Operations and Regulations to the Rest Services application directory.

The agency table must be linked to the inspection table, so it should have an inspection key column with a foreign key constraint. You can create the agency table in the Schema Manager, or you can create it by adding a business object link to the Inspection InfoViewer in the Content Manager. If you create the table while adding a business object link, it will be linked to the inspection table automatically.

Finally, take note of the moniker of the agency business object, because this will be used to connect the object to the Rest Services. If you don't know the moniker, you can look it up in the Schema Manager. First, select the node for the agency product family that the table belongs to. The first part of the moniker consists of the owner of the product family followed by the product family name. The last part of the moniker is the common ID of the agency table.

For example, if the InspectionDetail table belongs to a product family called Details, and the owner of the product family is InforClient, then the moniker of the agency object is InforClient.Details.InspectionDetail.