To configure custom fields for NFC and Camera

The default field for using the NFC reader is NFC and the default field value for Camera is 'Barcode' which is set at the Tenant Level. You can configure custom fields at Tenant/Organization/Plant level to use the NFC reader or Camera with AVEVA Mobile Operator app. The Custom fields allows the NFC or Camera enabled mobile devices to read, parse, and format the data (in the specified formats) using NFC tags or Barcode/QR code.

1. From the installation media, navigate to the Install/SQLScripts folder, and then edit the UpdateCustomFieldInfoPerPlant.sql script.

2. In the script, do the following steps:

   1. Provide the Peripheral Name.

   2. Provide the required Tenant/Organization/Plant name as PlantOrOrgName.

   3. To add the Custom fields in Management Center, update the PropertyBagDefinition in the script by entering the required custom field names in the DataItem tag under the Field Name control. Refer the sample provided in the script.

      • In the Field Name control, the DisplayValue and the Value must be the same.

      • The default value of the IntegrationType label will be the Peripheral name.

      • Field Name label value will be the value that you had provided in the DataItem tag. For example, if the value for the DataItem is ‘CustomField1’, then the Field Name label would be: "Field Name:CustomField1".

   4. To add the Custom fields in the Mobile, update the FieldCustomInformationBag parameter by adding the following in the Datasegment.

      • Field Name: Provide the field name that you had provided in the <DisplayValue> field in PropertyBagDefinition.

      • DataType: Supported Data Type is plain text and the value will be ‘MimeTypePlaintext’.

      • Format: The supported format is ‘ASCII’.

      • PrefixToken and SuffixToken: If the response data has any prefix or suffix, then enter the prefixtoken and/or suffixtoken. For example, In /~FLOCAWS10234~/ the prefixtoken is ‘/~’ and the suffixtoken is ‘~/’.

      • IsFieldInResponse: Is of type Boolean and therefore, can take the value in ‘0’ or ‘1’. If the fieldname is in response, the value is ‘1’ and if not, then the value is ‘0’. For example, in /~FLOCAWS10234~/, the fieldname ‘FLOC’ is a part of response and therefore, the value for IsFieldInResponse is 1.

      • Reader Name: Name of the Peripheral for which you want to create the custom integration. For example, Camera or NFC.

3. Run the script.

   The custom field configured for the peripheral will be available for integration in the Procedure Builder module of Management Center. For more information, see the topic "Procedure Creation - Peripherals" in the AVEVA Management Center User's Guide.

4. Sync data between the Server and the AVEVA Mobile Operator app.

   The custom fields will be available in the Search Field list under the Search/Input Device screen. For more information, see the AVEVA Mobile Operator App User's Guide for Android and Windows 10.