Log and note unfound Process Names/Codes

I'm uploading large amounts of historical data from legacy systems, and because there was no coding standard in place when the files were produced, many of the process names are causing upload errors. The WATS client is moving these files into an error folder, regardless of file type (XML, JSON, etc.).

It would be extremely helpful if WATS could retain and segregate these files and provide a way to notify us or allow updates so they can be properly integrated afterward.

A feature similar to how WATS handles Unassociated Part Numbers would be ideal. In that case, WATS still imports the file but flags that the PN is not linked to a Product Group. Likewise, if WATS could import the file under an “UNKNOWN” process category, generate a list of these unknown processes, and allow users to associate them with an existing valid process name, it would streamline the cleanup and onboarding effort significantly.

For example, I'm seeing variations like "Unit Test", "UNIT TEST", and "Unit-test" all fail. OR can we have Alvea implement logic to resolve these variations automatically, or at least allow WATS to upload and hold the files until the process names are mapped?