Use this argument as a filter to determine which of the available fields will be included in the signature. The example implements the useParam argument as USES_PARM constant, in the setResourceDomain method near the end of the example.

The USES_PARM parameter is only meaningful when the parameter identified in the name argument and the parameter names in useParam parameter are in the same fieldMap, and the data type of the useParam parameter is boolean[]. When these conditions are satisfied, the adapter service editor treats the useParam setting as a filter on the resource domain association. When this occurs, the resource domain values are only applied to the name parameter row in the fieldMap if the corresponding value in the useParam is true which occurs when the user of the adapter selects the check box.

When the user of the adapter selects the fields to use for the notification by selecting the check boxes in the Uses column, values appear in the Signature column. When you save changes to the notification node, the signature changes are reflected in the associated document type.