We renamed the setting "Enforce Verification Minimum. When enabled the # of verification searches set in the package must be used for HR and SHM (API)" to “Enforce a minimum of 1 search type each in package (Verocity only)” for clarification. Swifthire Mobile always mandates a minimum of 1 of each search type in the package. This setting only affects orders placed through the HR module (Verocity). Enabling this setting forces the HR user to enter at least 1 of each search type in the package.

We added back an option for client/client type Ordering Options that had been removed in error - "Enforce package limit on the confirm screen"

We added a field to the client's Additional Settings for the PA MVR access code.

When a search was resubmitted from SwiftReference to a different researcher, the search cost was not being updated to the new researcher's search cost. After this week's release the search cost will update based on the new researcher's cost.

We resolved an issue with SH 1.0 ordering that prevented an applicant from updating their SSN if international ordering was enabled, the applicant switched to an international country, then back to the United States. The Govt ID field was clearing the SSN and then not allowing the applicant to update. This has been fixed.

The "Verification Location Population" option was not working in HR module; we deployed a fix so that if this option is enabled in Ordering Options, the locations in verification searches are used to populate searches on the report.

An update has been released to change the verbiage on '30 year searches.' Instead of showing that 30 years have been searched, deverus has made an update to display:
'All Available Records.'
​
If you would like to revert to have the '30 years' display as before, please put in a ticket with support.

When an applicant selected Government ID on Swifthire Mobile, there was no SSN field available on the "Change Report Info" screen in the admin module; this issue has been fixed so the CRA will be able to enter the applicant's SSN.

The resubmit link on the search card for Past Address History and some other instant search types was not functional and produced an error if the search was resubmitted. The link has been removed from search types that cannot be resubmitted.

We rewrote the process for uploading Home Page ads to address an issue that was causing the ads to sometimes display as broken icons.

In certain cases if an error was thrown on Swifthire Mobile orders coming in through the API, a partial report without documents was created; this has been fixed so that a report will not be created without documents if the API returns an error response.

We fixed an issue that was preventing the applicant address from failing to populate on the initial load during the review process if the client was using Swifthire Mobile with review and the "Use Verification Location for Ordering" setting in client/client type Ordering Options was set to YES.

We removed the "Save Information" button from search types in the admin where a draft of results entry cannot be saved.

We fixed an issue where API orders for credit searches were not routing to grading.

We added additional validation for E-Verify search type orders:

For Swifthire Mobile Applicant Pay orders we added the status of Payment Pending to the report level so that it's easier to see from the hold queue if payment is pending.

We resolved an issue that prevented the HR client from moving a Swifthire Mobile out of the review stage when an international address is used in an education verification.

We fixed an issue that was causing E-Verify searches ordered using US birth certificates to return an error.

We resolved an issue with Swifthire Mobile with review where the Continue button was enabled but all required information was not filled in, if the applicant added a second employer without selecting the country.

For Swifthire Mobile Applicant Pay on Completed Report orders, sales tax was not being charged. This has been resolved so if the client has sales tax set up in the client editor, the sales tax will be calculated.

The Swifthire Mobile with Review process was not showing the government ID in the HR module. Additionally, if the candidate entered an international address as the primary or only address, the HR ordering screen displayed the UI for international, and the field for government ID replaced the SSN. This was causing multiple issues, including some reports to come across without the SSN if the applicant entered their SSN in this field. This has been fixed so the review process will show the government ID.

Applicants completing a Swifthire Mobile without Review orders containing an employment gap were receiving the error "There has been an error submitting this application on the server". This error has been resolved.

The I9 form in the deverus platform has been updated to the latest version (10/21/2019). For more information, please see https://www.uscis.gov/i-9.

Please view our help center documentation for full details on how to use this new feature, including an explanation of "client manager" permissions, the change log, how to set the data retention policy for clients, and when the purging process for reports will run.

It is important to note that once purged, client data cannot be recovered.

https://deverus.zendesk.com/hc/en-us/articles/360033543612

We fixed an issue that was preventing Swifthire Mobile from honoring the Applicant Result Delivery setting. Previously when set to No, there were some scenarios where the system was still emailing a copy of the final report.

​
Now, when set to No, the applicant will not receive a copy of their final report email. For Swifthire Mobile they will only receive the invitation to the Applicant Portal, where the background report is in progress and can be viewed when complete.

Document type adverse letters (2.0) will continue to be emailed to the applicant email address used by Swifthire and displayed in the report level activity log and the HR portal.
​
​

We also resolved an issue that was causing API orders to route to the NSC researcher, even when the client/CRA did not use the NSC integration.

Adverse/Pre-adverse 1.0

Adverse/Pre-adverse 2.0 Loggin on the Report Level

A limitation with Hubworks was causing apostrophes to be stripped out of first names when sent to researchers; this has been resolved.

We resolved an error that sometimes caused the incorrect state to display when the hold queue contained multiple jurisdictions.

We fixed an issue that was causing some Hubworks reports to get marked as complete and show in the Completed bin in the HR Module when not all searches were completed.

In progress, delay, needs more information, expire, QA, researcher editing, unassigned, review

A drop-down filter has been added to allow the CRA to filter by status; this filter works in conjunction with any other filter on the page.

The search buttons have been combined into one button.

Pre-Adverse Letter (if available), and then Report.

Adverse Letter (if available), and then Report.

If no letters are available, then only Report is shown. If Adverse letter is available, then Pre-adverse letter should not be included.

Please view our help center documentation for full details on how to use this new feature, including an explanation of "client mananger" permissions, the change log, how to set the data retention policy for clients, and when the purging process for reports will run.

It is important to note that once purged, client data cannot be recovered.

https://deverus.zendesk.com/hc/en-us/articles/360033543612

When viewing reports form the report level, not every report has the ability to add an adverse/pre-adverse letter. This has been resolved.

We added a header to Advanced Search feature ( in the HR module ) to make it easier to see branch and user distinctions when an HR client is searching by branch/user.

We fixed an issue that was causing phone numbers with parenthesis to be truncated when sent to i3.

We resolved an issue that was causing duplicate results to post to the i3 and labcorp integrations.

We added a new feature to allow the CRA to track and record consumer disputes within the deverus system. You will now have a custom search in which you can order a "Consumer Dispute" and attach it to a current report. This search type can be used to gather additional information, track progress on an investigation and complete any final findings.
​
Additionally, QA users will be able to identify when a subject has an existing dispute already recorded in the system for County or Statewide searches.
​
This will help ensure you are aware of any past disputes for a candidate, thereby helping prevent potentially misreporting the same information again. It will also serve as another alert for your QA team to take extra precaution when validating the information on the report. For more information on using the new feature please see https://deverus.zendesk.com/hc/en-us/articles/360039694332

We fixed an issue that was causing results from i3 to post to our system multiple times.

We fixed an issue with cumulative grading where canceled searches on a report were preventing the cumulative grading process from giving the report a final grade.

The Applicant Address is now displayed on the "Quality Review Process" screen in QA.

We resolved an issue with SwiftReference where multiple email addresses in the CRA's main customer service profile address were preventing email/text invitations from sending.

The new "Preview Reports" link in QA was not excluding current searches so the link was always active if there was more than one search on the report. This has been fixed.

We updated the client/client type ordering options to remove options for legacy features and relabeled others to clarify their function.
​

We fixed an issue where double quotes were appearing around the invoice number in the CSV export.

We resolved an issue with the MVR retry process that was preventing MVR searches from completing.

We changed the xml being sent to i3 for DOT Labcorp searches to use the correct casing for DOTAgency to resolve an issue placing DOT orders.

The I9 audit export process was breaking because documents that had once been stored on the gluster that were moved to s3; we resolved the issue with the file path so the audit export file can be emailed to the user.

We added the SSN for Swifthire subjects to the CSV invoice file export.

The word "comment" was being added to the Verified with Discrepancy field on Work Number results; it has been removed.

We created a process to map multiple locations in Integration Manager through an upload, similar to the CSV location upload in the legacy integration platform.

We expanded character limits for COCR results received through the hubworks integration to accomodate full sentencing information.

Performance in HR Module was improved by up to 50% in some areas, specifically around report management.

Email invitation to the referee is successful, the activity log on the search level displays

An email is not successfully delivered the activity log on the search level displays

The completion and/or cancellation of multiple searches was prompting the status email to be sent to the subject for each search in the report. This has been resolved.

The Integration Manager UI was not resetting when additional filters were selected so sometimes the user was left in a filtered "dead end" with no results. A fix has been applied.

Many of the longest running queries found during reported times of latency involve queries that use tables that are no longer necessary due to data architecting that was done to remove intermediary tables between the report and search table. The queries have been rewritten to free up database resources from having to do unnecessary joins on a large amount of data. We project this will increase targeted queries performance by 3-4X.
​

A new feature was added where the NSC School List will now be updated automatically on a monthly basis during the 3rd week of the month to keep up with the current list.

We added an additional column to one our database component tables that helped to eliminate unnecessary processing overhead.

We updated duplicate checking for Swifthire Mobile to include the status of the SHM invitation. Now when a new SHM request is initiated, then the platform will do a lookup in the SHM Invitation table based on the following attributes: First Name, Last Name, Email Address, Package ID, Client ID, as well as checked to see if the SHM Invitation is in a 'waiting' or 'ready' status. This solution will prevent duplicate orders, but allow legitimate different orders for the applicant to be processed.

We fixed an issue that was causing an error if an E-Verify search was placed by an HR user with a number in the username.

We will be scheduling the rebuild/reorganization for all databases based on fragmentation percentage on Saturday nights, excluding the last day of the month and the first day of them month.

Sometimes when a Swift Reference expired, the search went to a blank researcher. We implemented a fix that will produce an error if the researcher is blank so the process will retry.

When the last search on a report was completed by a Vero to Vero researcher, multiple email notifications were being sent out. This has been resolved.

We increased the character limit for the 'sentence' node on HubX federal criminal searches from 255 characters to a more suitable character count that will allow for larger sentence information.

The BIS statewide CoCourts integration was expanded to include Denver County.

New JTDS Drivers were deployed to all servers in preparation for AWS updates to prevent service disruption.

It was brought to our attention that on the CSV invoice export the applicant SSN and search reference were not included on services such as Swifthire, Grading, Admin Ordering, etc. This issue has now been fixed.

We changed the verbiage on the SHM consent button from 'CONTINUE' to 'I ACCEPT' to match the verbiage displayed on the disclosure when the applicant does NOT use the electronic wet signature, and instead clicks "Type Tab" to enter name and last 4 SSN.

When Cleara results contained sex offender records and no DOB, an error was being generated that prevented results from displaying properly in QA. We added an exception to the code to accommodate records returned without DOBs

Users were unable to preview SHM consents from the form builder due to an error that prevented the consent from being displayed. The issue has been addressed, and the fix was deployed.

When using SH1 and an integrated drug provider the applicant was unable to select the scheduling type or reason for test. This prevented the applicant from saving the search. The issue has been addressed, and the fix was deployed.

When using the consent placeholders in SH1, a number of placeholders were not being replaced with the correlating data. The issue has been addressed, and the fix was deployed.

Using the CSV batch upload option from admin, it was not possible to order single federal criminals or auto-populate federal criminals. For single federals the 'fdcr_1_state' was missing from the required columns. This column has been added, and the logic to auto-populate federal criminals has been updated as well.