Options

The Write Exceptions stage enables you to select which fields' data should be returned to the exceptions repository. The fields that appear depend upon the stages that occur upstream in the dataflow. If, for instance, you have a Validate Address stage in the dataflow, you would see such fields as AddressLine1, AddressLine2, City, PostalCode, and so on in the Write Exceptions stage. By default, all of those fields are selected; uncheck the boxes for any fields you do not want returned to the exceptions repository. The order of the fields is determined by how they are ordered when they come into the Write Exceptions stage. You can reorder the fields by selecting a row and using the arrows on the right side of the screen to move the row up or down. The order you select here will persist for all users in the Data Stewardship Portal, but each user can reorder the fields within the Portal to their own liking.

Select Allow user to create best of breed records in Portal to perform manual record consolidation when data matches cannot be made using standard rules. This feature copies a selected record within a group and uses it instead of the duplicates for processing. This option is available only for grouped exception records that are generated from a matching job, which is identified by the presence of the CandidateGroup field or the CollectionNumber field. When you use this option, a read-only field called “CollectionRecordType” will be added to the exception record. You can see this field at the bottom of the list; note that all options for that field are disabled.

Note: If your dataflow is also being configured for revalidation, you will need to manually add and expose the CollectionRecordType field in the Exception Monitor stage/subflow and the service itself.

After adding a Best of Breed record in the Resolve Duplicates view of the Data Stewardship Portal Editor, this field will be set to "BestOfBreed." If you choose to create best of breed records, you will be unable to use the Approve All option for those records in the Data Stewardship Portal. Read more about best of breed records in the Data Stewardship Portal here.

You may have input fields that you want in the repository but do not want to be viewable within the Data Stewardship Portal. This could be due to the field containing sensitive data or simply because you want to streamline what appears in the Portal. Check the Allow viewing box to designate which of the selected fields should be viewable once they are passed to the exceptions repository. By default, all fields are viewable. Uncheck the box for any field you do not want visible in the Portal.

Additionally, you can designate which of the selected fields should be editable in the Portal once they are passed to the exceptions repository. By default, the Allow editing column is checked for all fields coming in to the Write Exceptions stage. Uncheck the box for any field you wish to be returned to the exceptions repository in a read-only state.

Finally, you can use the Lookup function to assign a lookup to a field containing problematic data. You can select from the list of lookups that have been defined in the Data Stewardship Settings tool or you can manually enter the name of the lookup. For more information on lookups, see Lookups.

Note: Lookups can be assigned only to fields whose type is string.