Q1S6.21 Release Notes
Release Q1S6.21 (04/12/21) This program, printed documentation, and documents should not be used as a substitute for professional advice in specific situations. The procedures, images, and examples in this document are for illustrative purposes only ...
Updated Apr 20, 2026
7 views
Miscellaneous
Miscellaneous
Release Q1S6.21 (04/12/21)
This program, printed documentation, and documents should not be used as a substitute for professional advice in specific situations. The procedures, images, and examples in this document are for illustrative purposes only and may not be applicable in your setting due to differences in preference, settings, and/or state and local regulations.
|
|
|
Release Q1S6.21 includes the
first of two phases focused on an enhanced 4473 kiosk and user activity
auditing as well as the simplification of FFL validations.
|
|
|
|
|
4473 Kiosk Enhancement (Phase
1)
|
|
|
Previously,
FFLs seeking to use the 4473 kiosk mode were required to login to the kiosk
screen at the beginning of each day. And, upon completion of Section A of
the 4473 the FFL would provide its customer with a private and random kiosk
“code.” Unfortunately, the FFL’s initial login only connected the kiosk to
their default book creating a challenge for multi-book retail operations.
With
this release the customer kiosk “code” directly links the customer to the
Section B of the 4473 regardless of which bound book was set as default.
In
Phase 2, we will be providing FFLs with both a customer text and print
feature for sharing the kiosk “code” with its customers.
|
|
|
|
|
User Access Auditing (Phase
1)
|
|
|
When a user makes a change to a record
using "Corrections Log", Orchid eBound will now retain the
username and date. The username and date is present on each of the
corrections, located both inside of the Corrections Log (report) and on the
Item Detail screen. Additionally, we’ve added a search bar so that you can
search for corrections by user.
In Phase 2 we’ll be adding similar features
to all other Orchid eBound transactions.
|
|
|
|
|
Remove eBound Validations of
FFL "Currency" in API and Upload Methods
|
|
|
Previously, Orchid eBound’s API and bulk
transaction uploads checked for the validity of an FFL license date and
would not permit a customer to proceed if the license was expired. This
occurs in all API transactions and in all excel file uploads.
Several customers had requested the removal
of this “over control” as it was causing the unnecessary resubmission of
transactions. Their rational was that the ATF does permit licensees to
continue acquiring and disposing of firearms after license expiration with
the presence of a "Letter of Authorization"
(LOA). Please note that the control was only removed from the
API and bulk uploads. All other transactions performed in the user
interface were left unaltered. And, in all cases, Orchid eBound continues
to check for: (1) the presence of an FFL number; and (2) that the FFL meets
the proper character string length/format.
|
|
|
|
|
|