Week of December 20, 2018
Week of December 6, 2018
Week of November 29, 2018
Week of November 8, 2018
Week of October 25, 2018
Week of September 26, 2018
FCRA Update Week of September 21, 2018
Week of September 6, 2018
Week of August 23, 2018
Week of July 25, 2018
Week of July 5, 2018
Week of June 7, 2018
Week of June 6, 2018
Week of May 22, 2018
Week of May 1, 2018
Document Server Migration - April 30th, 2018
Updated release - Week of April 9, 2018
March 9th, 2018
March 7th, 2018
VER 7.6.3 and VER 7.6.4
VER 7.6.2 - January 22, 2018
Verocity - December 20th, 2018
This week we have several small features, in anticipation of our QA release next week.
We added a required click-through "Certification" for consent on file for Swifthire Mobile! This is similar to the one used in the regular HR ordering screen. The HR user must check a box to acknowledge that they are providing correct "Disclosure and Authentications" to the applicant. The checkbox is required, so it must be checked to submit the order. The verbiage is as follows:
SwiftHire Certification
I hereby acknowledge that, by utilizing the SwiftHire process, the consumer will be provided with an electronic written Disclosure and their electronic written Authorization will be obtained before an order for a consumer report will be placed, and I agree to the content of those two documents; furthermore, I hereby certify that the appropriate adverse action process will be followed, where applicable, and that this consumer report is being obtained for employment [business transaction] purposes, all in accordance with the requirements of the federal Fair Credit Reporting Act, 15 U.S.C. §§ 1681 et seq.
Applicant/Global Link Certification
"I hereby acknowledge that, by utilizing the SwiftHire process, the consumer will be provided with an electronic written Disclosure and their electronic written Authorization will be obtained before an order for a consumer report will be placed, and I agree to the content of those two documents; furthermore, I hereby certify that the appropriate adverse action process will be followed, where applicable, and that this consumer report is being obtained for employment purposes, all in accordance with the requirements of the federal Fair Credit Reporting Act, 15 U.S.C. §§ 1681 et seq."Batch Orders Certification
"I hereby certify that, by using the Batch Upload process, the consumers will be provided with electronic written Disclosures and their electronic written Authorizations will be obtained, that the appropriate adverse action process will be followed, where applicable, and that these consumer reports are being obtained for employment purposes, all in accordance with the requirements of the federal Fair Credit Reporting Act, 15 U.S.C. §§ 1681 et seq."
Verifications in QA
You will now have some additional Verification statuses available for EDUV and EMVP searches when in the QA Screen:
Completed -Verified
Completed - Verified w/Discrepancy
Completed - w/Consumer Supplied Documentation
Completed - Not Verified
Individual Charges in QA
From the QA processing screen, you will now have a check box for each individual charge. You can easily delete or check each of these components.
Verocity - December 6th, 2018
We added Researcher Groups. This new feature allows you to accomplish two things.
1. Assign certain researchers to certain clients or client types
2. Round Robin load balancing of work. You can also create different groups of researchers in the researcher network search type assignments, and then assign either specific clients or client types to utilize a group of researchers. The system will then assign searches for the clients where they have a Researcher Group configured. It assigns based on the search types in the report, and which researcher in the group currently has the least amount of assigned searches. Searches are assigned on an applicant (whole report) basis.
For more information on the new feature please see this help center article.
Requirements for the identification of End Users for Samba.
We have updated the MVR process to include the required 'End User Identification'. There will not be any action required on your end.
Verocity - November 29th, 2018
We added the additional searches attached to the report to the QA processing screen. You will also have the ability to mark searches as follow-up for documentation purposes.
Client Notes will now be available in the QA screen. These can be set-up under the client editor, in "Client Notes".
A pop-up will show in special instructions in QA processing screen. Additionally they will be available by using "click here to view client notes."
Verocity - November 8th, 2018
We added the option to search by Document Type to Report Finder to allow CRAs to find applicant reports with Adverse and Pre-Adverse documents attached.
We added a Select All checkbox in QA for criminal searches (instant, county, statewide) to allow the CRA to quickly select or deselect all hits.
We fixed a bug with international phone numbers that prevented some applicants from moving through the Swifthire Mobile process. Phone numbers will now now be accepted in international format to accommodate the country selected.
We added the ability for the CRA to create, edit, print, and view custom adverse/pre-adverse letters from the report level screen in the admin module. The CRA can also cancel the letter before sending which will dismiss the dialog window, not email the applicant, and not add the letter to the report. Note: this feature is only available for Adverse/Pre-Adverse version 2.0.
Verocity - October 25th, 2018
We fixed an issue that was preventing a re-direct if an error occurred while completing an education verification during a SwiftHire Mobile Applicant Pay order.
We fixed an issue affecting OFAC searches through API ordering.
We removed city and state validation from SwiftHire Mobile. Applicants will receive a city/state mismatch error message if their city is misspelled.
We released a feature for SwiftHire Mobile that detects gaps in an applicant’s employment history and prompts the applicant for supplemental information. Please see Gap Employment Detection for more information.
Verocity - September 26th, 2018
We are releasing a new version of Adverse and Pre-adverse Action Letters V.2 that has been rebuilt from the ground up. What this means is that there may be features from the previous version that are not included in this version; no functionality should be assumed. This version is only available by request. It will replace Adverse Letters as a search type and move it to a document type, though search types will continue to be supported alongside this new version. Please see this help center article for full details on the new features including but not limited to -
Ability to configure multiple types of letters
Ability for HR user to edit letters
When the HR user creates a custom letter using the "Order Pre-adverse/Adverse Action Letter" option, a subject packet is emailed to the applicant containing the Pre-Adverse / Adverse custom letter along with the report. The subject line of the email will be formatted as Pre-Adverse - “FCRA Preliminary Notice of Adverse Action - Applicant Name” or Adverse - “FCRA Notice of Adverse Action - Applicant Name”.
We updated the Advanced Search screen in the HR Module to include the ability to filter by document type so HR users can find and view applicants with adverse and pre-adverse letters.
Once a letter has been ordered, the HR User who ordered the report will receive a notification 5 days after a Pre-Adverse has been sent, once for each applicant. The email that the HR User receives is not customizable but does have client specific details. This email also masks the YOB on any DOB being displayed. It contains a link to the specific applicant the email is notifying of, which allows the HR User to be able to view the Pre-Adverse letter, order an Adverse letter if necessary, verify the name and dob of the applicant, or view and verify any other applicant information contained in the report.
The price for the new service is $0.25 per pre-adverse and adverse letter created
We added the ability to save work in a "draft" status on Employment Verification searches, if all information has not been gathered on the first data entry point.
We resolved an issue in Swift Hire Mobile with pre-populated Driver’s Licenses.
We simplified School Name entry in Swift Hire Mobile.
Verocity - September 21st, 2018
The CRA still has the responsibility to make any additional updates in any custom consents and disclosure documents along with any special client pre-adverse/adverse letters. Any other documents in which the CRA provides the "FCRA Summary of Rights" should also be updated. If you have ever edited the pre-adverse/adverse letter template, the update will not apply to your system for that letter.
FCRA Compliance Wording Update
deverus is aware that the Bureau of Consumer Financial Protection issued an interim final rule to be effective September 21, 2018 to update the model Summary of Consumer Rights and model Summary of Consumer Identity Theft Rights provided in Appendices I and K to Regulation V, which implement the Fair Credit Reporting Act.
We are providing an update to the wording in 2 areas in which deverus provides the “FCRA Summary of Rights”, the pre-adverse/adverse letter template and “FCRA Summary of Rights” link (and PDF file) within SwiftHire Mobile.
The following text will be added:
“You have a right to place a ‘security freeze’ on your credit report, which will prohibit a consumer reporting agency from releasing information in your credit report without your express authorization. The security freeze is designed to prevent credit, loans, and services from being approved in your name without your consent. However, you should be aware that using a security freeze to take control over who gets access to the personal and financial information in your credit report may delay, interfere with, or prohibit the timely approval of any subsequent request or application you make regarding a new loan, credit, mortgage, or any other account involving the extension of credit.
As an alternative to a security freeze, you have the right to place an initial or extended fraud alert on your credit file at no cost. An initial fraud alert is a 1-year alert that is placed on a consumer’s credit file. Upon seeing a fraud alert display on a consumer’s credit file, a business is required to take steps to verify the consumer’s identity before extending new credit. If you are a victim of identity theft, you are entitled to an extended fraud alert, which is a fraud alert lasting 7 years.
A security freeze does not apply to a person or entity, or its affiliates, or collection agencies acting on behalf of the person or entity, with which you have an existing account that requests information in your credit report for the purposes of reviewing or collecting the account. Reviewing the account includes activities related to account maintenance, monitoring, credit line increases, and account upgrades and enhancements.”
Verocity - September 6th, 2018
We added an admin note to confirm payment has been received for Swifthire Mobile orders.
Email notifications will now be sent for credit card transactions associated with Swifthire Mobile Applicant Pay orders.
Verocity - August 23rd, 2018
We added data pre-population for Swifthire Mobile requests initiated through an ATS using Integration Manager or VeroConnect. Data population will not work for Hubworks requests. If data is provided in the request, it will be populated into the corresponding Swifthire Mobile field as required by the ordered package, with the exception of Custom searches which will NOT be populated. The applicant can edit pre-populated data. A help center article fully detailing the new feature has been added here.
Verocity - July 25th, 2018
This is an update to Verocity.
We added a CC option to the Swifthire application email screen to CC additional individuals on the initial Swifthire invitation and reminders. This option is available when creating a Swifthire request.
We implemented a type-ahead on Swifthire Mobile education verification searches to narrow the list of schools so the applicant can select the correct school from the NSC database.
Verocity - July 5th, 2018
We added a duplicate detection error message to Swifthire Mobile to alert the candidate to duplicate submissions.
A duplicate order will render the following message in the browser: "We have detected a duplicate order. Please ensure you have not completed the same application in the last 24 hours. If you feel you have reached this message by mistake, please contact your potential employer to verify."
The message is triggered by the following criteria:
same hr client
same package
same applicant email
24 hours
We fixed a bug that was preventing in-app notifications from being displayed in the Applicant Portal if the applicant does not provide SSN.
We added a "Copy URL" button under the Swifthire Mobile global link to resolve an issue with copying the link.
We refactored the Verocity document management process to read from S3 directly and bypass network storage for images.
We added the ability to enable or disable the NSC integration at the client level under the client's Additional Settings.
We added a resubmit button to Report Finder that allows the CRA to resubmit searches ordered with the wrong school to the NSC with the correct school, instead of canceling and re-ordering the search.
We added a SwiftHire Expiration section.
Verocity - June 7th, 2018
We fixed a bug that was causing custom search names to display incorrectly in the applicant portal and during the Swifthire Mobile ordering process.
We refactored the Verocity document management process to read from S3 directly and bypass network storage for archived documents.
Hubworks SSL Certificate Renewal
On June 7, 2018 at approximately 8:30P CT, the deverus Infrastructure Team will renew and update our SSL Certificate for hub.deverus.com, to enable ongoing secure connections between your integrations and our platform.
The endpoint and login credentials for integration partners will not change.
Integrated partners will simply need to import the new certificate into their keystore. Failure to do so could cause an interruption in the integration.
As with all planned integration maintenance events, we are sending this message to all of our major Researcher and Applicant Tracking Solution partners; but we wanted our CRAs to be informed and working in tandem with us to ensure all integrations meet this deadline. Based on our experience, the Researcher integration changes are often straightforward and easy for us to manage directly; it is the Applicant Tracking System integrations that sometimes require Client or CRA outreach to help us execute.
For any proprietary integrations (homegrown platforms that belong only to your customers) or exclusive Applicant Tracking Solutions (working with a short list of CRAS), we are asking that you (the CRA) forward this message on to their development teams on our behalf.
If you have any questions, please create a support ticket so our team can assist you.
Integration Security Update : Sunsetting TLS v1.0 - June 6th, 2018
The ability to use TLS v1.0 protocol for secure connections to the deverus platform will be expiring soon. Any requests sent with TLS v1.0 protocol will be denied and rejected as of June 30, 2018.
If you or your key clients are utilizing any API connections or one-off integrated solutions to connect to the deverus platform, you must patch or update your configuration to utilize TLS v1.1 or higher by June 30, 2018 to avoid a service disruption for your integration.
We are sending this message to all of our major Researcher and ATS partners; but we wanted our CRAs to be informed and working in tandem with us to ensure all integrations meet this deadline. Based on our experience, the Researcher integration changes are often straightforward and easy for us to manage directly; it is the ATS integrations that sometimes require Client or CRA outreach to help us execute. We will keep you informed if we receive any feedback from any ATS teams indicating that they will not execute this work without documented approval from the client.
For any proprietary integrations (homegrown platforms that belong only to your customers) or exclusive ATS (working with a short list of CRAS), we are asking that you (the CRA) forward this message on to their development teams on our behalf.
What can our integrated partners do to prepare?
If an application can make a successful GET request to https://hubworks.stage.deverus.com/hub/tlstest.cfc?method=verify it will receive a response of "Hubworks_connection_OK". This test will allow you to confirm that the application is running an acceptable version of TLS and service will not be impacted by the June 30, 2018 update. This endpoint can be used to verify connection for both requesters (ATS) and providers (researchers and vendors).
If you have any questions, please create a support ticket so our team can assist you.
Verocity - May 22nd, 2018
Integrated Drug Testing
We added a fourth drug matching option. This option will appear in Client Settings.
Option 4: "Always create new report and complete the search" - When a drug result is received for a set client, the system will ALWAYS create a new order, and complete it - no matching to client / order / donor is required. Please reference the following article to review the full list of options available.We added a fifth drug matching option. Option 5: "Associate all drug results with existing (donor + product) matches and hold all drug screening results that do not have a matching order (based on donor name + SSN + product code)". Please reference the following article to review the full list of options available.
Integration Manager
We fixed a bug in Integration Manager where the client reference was not being populated on certain searches.
Swifthire Mobile Modifications
We added the ability for international users of Swifthire Mobile to log into the Applicant Portal without having a SSN.
We added the ability for applicants to input additional previous addresses into Swifthire Mobile.
We added the ability for applicants to input additional names into Swifthire Mobile.
We added the ability to input international job locations on the "job for which I am applying" screen in Swifthire Mobile.
In the Applicant Portal we removed salary fields that were displaying in the Information Provided and Information Verified sections of EMPVs.
We modified the withdrawal of consent screen in Swifthire Mobile. The CRA name and email have been replaced by the HR client company name and user contact email. Instead of ""Please contact <CRA> at <CRA EMAIL> to discuss your options for proceeding," the screen now reads "Please contact <HR CLIENT COMPANY> at [email protected] to discuss your options for proceeding."
Verocity - May 1st, 2018
This is an update to Verocity.
We added a rule to the drug results queue that groups results with the same specimen ID as duplicate specimens.
We fixed an issue in the new HR portal where the Archived and Needs Attention categories in the My Reports right navigation pane are not showing the number of reports in each of the categories.
We addressed a formatting issue in the new HR portal where the preview (magnifying glass) and print titles are not aligned with the appropriate data in the table.
We fixed a bug that was triggering the Swifthire process when the user refreshes the preview pane to preview the consent form.
We fixed an issue where the screening stats report was not updating once a criminal database search had been cleared to a no record.
We fixed an issue where deleted users were still receiving Swifthire notifications.
We fixed an issue where the sentencing information was not being copied over when using the "previous hit reported" function.
Document Server Migration - April 30th, 2018
Root Cause:
On April 30th one of the three servers in our file server cluster failed. This failure caused system-wide issues with accessing and uploading documents across all modules. We removed the failed server from the cluster and at this point, we were only running two servers in the cluster until the third one could be repaired.
Despite removing the failed server, the network paths to that server were still cached. Until the network paths were cached there were still reports of issue accessing and uploading documents. After clearing the cached paths operations returned to normal but at a degraded performance.
On May 7th in an unrelated incident, we experienced a hardware failure on one of the file servers in the cluster. AWS automatically handled this failure and moved the server over to new hardware. While the new server was being built, the system load caused degraded performance on the cluster, which again impacted all modules in the system. It was not until the new server came online, and all of the files were synchronized that the system performance returned to normal.
Solution:
On May 7th, as a result of the issues with the current file system, the decision to move to a new file system was made. The deverus engineers have been working tirelessly setting up a new file store solution within AWS that is backed by S3. This system will provide more stability, performance, and scalability.
The majority of this week was spent testing this new solution in our Staging environment and then rolling it out to a demo site and testing it there as well. This testing showed a large improvement in all 3 aforementioned areas. With these results, we feel confident moving forward with this solution.
The migration plan has been created and we started executing it yesterday. We are going to slowly roll out the new file storage one client at a time and will be constantly monitoring the new system as each client is added. You will be notified at the point where your system is in the queue to be migrated and we will stay in close communication so that any issues you may experience can be swiftly addressed. Thank you for your patience and cooperation in this endeavor as we strive to improve the quality of our services.
Update:
As of Wednesday, May 16, 2018, all active deverus clients have been migrated to our new file server infrastructure. We expect that this migration will improve the performance of our document upload and access features for all documents created by users or automated actions from this date forward. We are continuing to migrate all historical documents behind the scenes and will notify you again when this work is completed. Again, we appreciate your patience and cooperation throughout this process.
Update 5/17/2018:
On Wednesday morning we started to move archived documents from the Gluster to the new S3 environment. This move has resulted in some unforeseen issues causing connectivity related problems with the new service. We are currently moving the archived documents out of the S3 environment so that we return to our baseline environment.
Update 5/18/2018:
On Wednesday, May 17, 2018, we were able to successfully remove the archived documents we had previously added to the storage device. Once the archived documents were removed, we successfully spun up a new Gateway and pointed the system to this new gateway. After the new Gateway was connected we started receiving complaints about SwiftHire not moving through the consent process. After some investigation, we discovered that the 8 of the 11 App servers were still trying to connect to the inoperable gateway. We cleared the network cache then restarted the affected App servers. This was completed around 8 pm Thursday night. After the restart of the servers, the connection to the new Gateway was established. We have been monitoring the App servers and there have not been any connectivity issues. We will continue to monitor and inform you if we see any issues.
Verocity - April 9th, 2018
This is an update to Verocity.
We are excited to make our updated HR Portal available to deverus' customers on Monday, April 16. This update modernizes the experience of the HR client with a minimal learning curve. We will activate this feature on an as requested basis in phased rollouts through May 31, 2018. Please submit a support ticket to request activation on April 16 or May 15 (limited to 5 clients per date). From June 1, 2018 onward, the original version will not be available.
We added the ability to show or hide the Integration Manager for non-admin users
We fixed an issue in Integration Manager where you could not sort clients by clicking the header field.
We are excited to introduce customized consents for Swifthire and Swifthire Mobile. Now you can create consents specific to your clients.
Good to Know for Custom Consents:
When previewing a SHM consent, it is possible to trigger the SHM process if the page is reloaded.
Client Type level preview will NOT be available unless there is at least one client with no client level Swifthire settings. Global level previews are not available.
Best Practices:
Existing custom consents will more than likely need some tweaks to work properly with SHM.
It is recommended that SH1 consents/templates are copied and renamed before modification.
Page Titles are not necessary as the Page Name will be used as the header for consents (both in app and pdf).
Complex html/css may cause display problems. Html/css can only be used in body field types (not labels, descriptions).
Signature is always required even if required is not checked in the form builder.
We enhanced the batch upload process for Swifthire so it can be used with branch only ordering.
We added a feature that retains the email address of a Swifthire applicant as well as the option to manually resend the invitation and change the email address in case of an error.
Verocity - March 9th, 2018
Vero 2 Vero Improvement
All custom searches will now be able to support Vero 2 Vero integrations, thereby enabling deverus clients to partner for research.
You will want to work with your Vero 2 Vero researcher to set up your custom searches so that the 'Custom Search Set Up' screen is the same in both systems.
You will then submit a support ticket with the 'Client' custom search number, the 'Vero Researcher' custom search number and the 'Vero Researchers' id from the 'Client' system.
If you need more custom searches added to you system you may submit a support request and will we be more than happy to add any amount of searches you may need.
Verocity - March 7th, 2018
This is an update to Verocity.
We have updated the enforce package options in the Admin module for Client/Client Type/Global Settings:
Enforce package ordering - will enforce the package number as a minimum
Enforce package limit by hiding "add" tabs - will enforce package numbers as a maximum
Enforce package limits on the confirm screen - will enforce package numbers as a maximum
Applicants will have the ability to add a la carte searches outside the package similar to SwiftHire1.0.
VER 7.6.3 and VER 7.6.4
February 14, 2018 release -Invoicing
We are excited to announce new features to be added to the invoice manager! We now have the ability to add more flexibility in how you bill your customers. This new service allows you to have a separate line item for Swifthire and Integration/Hubworks charges. More information can be found here: Report Level Invoicing - Line Items.
February 16, 2018 release - SwiftHire Mobile Improvement
SwiftHire Mobile will now allow bundles and packages to be ordered without review.
Within the Standard Employment Verification search, we have removed format checking for phone numbers if the employ is in a region outside of the United States. This will allow for candidates with international employment history to complete the form without additional outreach from the HR team or CRA.
We have updated the report status options to include Adjudication in the Integration Manager.
Within the Swifthire Review or HR Portal search ordering process, we have resolved an issue that allowed partial orders to be placed when an error occurs during the ordering phase (without notice to the user). The behavior seen by HR and Admin users of this were duplicated and/or incomplete packages.
We resolved an issue preventing additional Employment Verification builder entries if the first entry was marked as "Current Employer."
SwiftHire Mobile updates:
Resolved an issue with data validation, so that the "Background Check Submitted" screen is shown once an order has been placed.
Resolved an issue where the "Basic Information" screen is shown after starting the "Background Check Request" flow.
Resolved an issue where applicants could skip SwiftHire forms and proceed further by tapping the "Continue" button without entering any data.
Resolved an issue preventing the "Continue" button to become active only after all required fields are filled.
Resolved an error where SwiftHire orders were without Review orders were being routed to the Review queue.
Verocity - January 22, 2018
SwiftHire ordering improvement
This is an update to Verocity. We have updated SwiftHire client level settings so they no longer default from one user to another. This will prevent users from ordering a SwiftHire if they do not have settings configured. This was done to ensure that SwiftHire orders are placed and routed correctly.