Enterprise Connection - Best practice

To configure a job you must create a unique name, set the report filter, provide an authentication token from the other WATS, and map your defined processes to the processes on the other WATS.

To initiate a new job, follow these steps:

1. Navigate to the top left and click on the "+ New job" button. An editor will open.
2. Fill out the properties, filter, connection details, and process mapping.
3. Confirm the job and start uploading reports to the destination WATS

To update an existing job, follow these steps:

1. Double-click on the desired job row, or
2. Click the "Edit" button associated with the job.
3. This action opens the job editor, allowing users to make the necessary modifications.

Properties

In the properties section users must specify the name of the job, which must be unique. Additionally, users have the option to include a description. For an existing job, the properties section shows the creator’s username and the last time the job was updated.

Filter

The filter allows users to refine their search criteria to select only the desired reports. Like filters found in reporting modules it offers options such as selecting levels, part numbers, processes, date from, and report types (UUT or UUR), except part numbers does not support wild card. 

A user can verify that the filter matches the desired reports by using the “Open UUT reports” or “Open UUR reports” buttons, redirecting them to a list of reports with the chosen filter applied. This ensures a comprehensive overview of the reports to be uploaded, for you to confirm the intended reports. 

Once all required fields are filled, users can proceed by clicking “Confirm,” prompting a confirmation message. Users have the flexibility to edit the filter at any time. However, upon modification, users must confirm the filter again to proceed with the process mapping.

When the filter is edited, reports that did not match before will be added to the queue and uploaded to other WATS. Reports that still match the new filter will not be reuploaded.

Connection details

In the connection details section, users are prompted to provide a URL and a security token for the other WATS. Upon successful connection, users gain access to the mapping grid, facilitating the process mapping. Connection details can be updated and reconnected at any time. However, users should exercise caution during reconnection, as modified process mapping data may be lost if it no longer aligns with the other WATS’s data.

Process mapping

Report processes must be mapped to a corresponding process on the other WATS. Cooperate with someone from the other WATS account to create or match up processes correctly.

The mapping grid will display the processes selected in the filter for mapping purposes. Users map their selected processes to those on the other WATS by selecting the process target from the cell dropdown, which lists all active processes from the other WATS.

The mapping grid will automatically map your processes to the processes from the other WATS if they have the same name.

Users can modify the process mapping at any time. In the event of issues later, such as errors or inactive processes, the status will be reflected in the job list overview or detailed statistics. Furthermore, the process mapping will display a warning icon if the process is no longer active or if error is detected.

Statistics

The statistics section provides an overview of the status of the active job. Hovering over the status provides detailed information on what each status indicates, aiding in troubleshooting issues or errors preventing upload. Additionally, the statistics section includes metrics such as reports processed in the last 24 hours, reports processed this year, reports processed in total, reports in the queue, and reports with errors. These statistics are visible only after the creation of a job, offering valuable insights into job performance and data processing.

Saving Changes

• Any changes made will be saved when clicking "Save".
• If you decide to leave without saving, all changes will be discarded.