JusticeTrax is pleased to announce the much awaited release of LIMS-plus v3.8.40!!
Over 40 issues have been included in this release that include bug fixes and enhancements to Portal, Evidence Tranfers, Main Case View and Attachments just to name a few.
Please take a minute to review the release notes below (and attached). Questions and requests regarding upgrades can be submitted via you ZenDesk support portal.
When using the LIMS-plus DNA integration, the Evidence Type in LIMS-plus maps correctly to Substrate field in LIMS-plus DNA.
Previously, when a sample was imported into LIMS-plus DNA, the sample's Substrate property would not be populated. This has been fixed so the DNA integration will now populate the Substrate if a possible value matches the Evidence item's Evidence Type in LIMS-plus.
Cross-case Evidence/Request relationships can be submitted to LIMS-plus DNA using the LIMS-plus DNA integration.
When a user relates an Evidence item in one Case to a Request in another, a corresponding sample can now be automatically imported by the LIMS-plus DNA integration. The sample will use the Case number where the Evidence item originated, not the Case number of the Request.
Database upgrade scripts insert only one AGCREP_CASEIMPORTS_LOGIN permission per Portal user role.
Previously, the upgrade scripts inserted a duplicate AGCREP_CASEIMPORTS_LOGIN permission entry in the AgencyRepRoleFunction table in the database for the Agency Admin role. This has been corrected.
The Agency Admin security role is now associated with three additional functions.
The database scripts have been modified to associate the Agency Admin role with AGCREP_REP_ADD, AGCREP_REP_EDIT, and AGCREP_REP_ROLES_EDIT in the AgencyRepRoleFunction table.
Barcodes can be printed while a user is logged in to more than one computer with JTTray installed.
Previously, barcodes would fail to print if a user's Windows account was logged in to more than one computer where JTTray was installed. This has been resolved.
This applies to single barcode print requests. Batch barcode printing is scheduled to be refined in a future sprint. Additionally, if the user logs their Windows account out of one computer, barcodes will fail to print with no apparent error as the printer list does not automatically refresh. Clicking the Refresh Printers button will fix the issue.
Users may log in to LIMS-plus even if a Custom Form exists with an invalid SQL statement.
Previously, the login screen would encounter a fatal error if a Custom Form contained an invalid SQL statement. LIMS-plus v3.8 validates all SQL statements in Custom Form layouts before they are saved, but a bad value may be carried over during a migration from 3.7. The login error has been fixed so that users are now able to log in and use the application as normal regardless of valid/invalid statements in Custom Forms.
Containers can now be edited effectively.
An issue was identified where an error message would be thrown when the user attempted to edit a Container in Transfer | Containers. This error has been corrected to allow Containers to be edited as expected, including printing barcodes.
In the Evidence Transfer screen, Hold and Returned use separate translation keys.
Previously, the Hold and Returned labels in Transfer | Transfer both displayed the Translated Value text from the same translation key. This has been corrected so each option uses a separate translation key under Administration | System Administration | Languages/Translations.
In the Evidence Transfer screen, the Transfer Receipt checkboxes and Clear button now have associated translation keys.
The 1st Transfer Receipt and 2nd Transfer Receipt checkboxes and the Clear button labels in Transfer | Transfer did not have translation keys. The appropriate keys have been added under Administration | System Administration | Languages/Translations.
In the Evidence Transfer screen, Selected Transfer being Returned checkbox now has a translation key.
Previously, the Selected Transfer being Returned checkbox label in the Transfer | Transfer screen did not have a translation key. The appropriate key has been added under Administration | System Administration | Languages/Translations.
Assign Requests for Analysis functionality has been improved to allow handling of large numbers of requests.
Previously, when a Department had very large numbers of unassigned requests available, the screen in Analysis | Assign Requests for Analysis would fail to load. This area has been improved to display results in pages with better search implementation, allowing it to handle Departments with thousands of requests. The results grid will now only display search results once the appropriate filters have been set and applied. Some issues were identified with the column size, column filters on the search results, and pagination. These issues will be resolved in a future sprint and do not cause a large impact on functionality. Additionally, users should be aware that large numbers of Requests (around 4000+) each containing a large number of associated evidence items will load in the results grid but may take some time. Research will be done on potential performance enhancements to improve this wait time in a future sprint.
In Assign Requests for Analysis, a Department may be selected even if it has no Services configured.
Previously, when a Department with no attached Services was selected in the Analysis | Assign Requests for Analysis search options, the page would display an error message and could not be closed until a different Department was selected. This has been corrected so that no error displays.
Analytical Instrument sequence files may be encoded in ASCII for instruments that require it.
Previously, for Administration | Instrument Administration | Analytical Instruments, the sequence files were exported only with UTF-8 encoding. This caused the files to be incompatible with instruments that required ANSI encoding. Users now have a choice of ASCII/ANSI encoding in addition to UTF-8 encoding when configuring Analytical Instrument sequence files. "UTF8 Text File" and "ASCII Text File" options have been added to the File Type dropdown in the Edit Analytical Instrument screen. Instruments with an existing File Type of 'ASCII Text File' in LIMS will be switched to 'UTF8 Text File' upon upgrade as the existing corresponding database value matches the UTF-8 encoding.
Agency Reps may be enrolled in Portal from within LIMS-plus.
Given the appropriate permissions, Agency Reps may now be assigned a Security Role for use in Portal from within the Agency Reps Administration portion of LIMS. Portal Enrollment and Account/Login Details options have been added to the Agency Reps menu that allow for selection of a Portal Security Role for an Agency Rep as well as giving direct access to the Account/Login Details screen without having to go into Edit Rep. If an Agency Rep is inactive in LIMS, a Portal Security Role cannot be selected for that Rep. A Rep can be set to Not Enrolled when Inactive in LIMS.
Phone Numbers display correctly in Edit Agency and Edit Agency Rep
Previously, for Administration | Add Agency/Representative | Edit Agency/Edit Agency Rep, the 3rd and 4th rows in the Phone Information grid displayed the same Phone Number. This has been corrected so all rows display the correct value in that column.
Autotext can now be used in Rich Text fields.
The Autotext menu and Autotext names can now be used in the Lab Notes and Results entry fields in Main Case View | Requests for Services configured to use Rich Text fields. Plain text Autotext values are permitted to contain line breaks, but the line breaks will not apply when the Autotext is used in Rich Text fields.
Autotext can now be used in Custom Form text fields.
The Autotext menu and Autotext names can now be used in Single Line and Multi Line Text fields within Evidence, Results, and Request Custom Forms. Please note, applying Autotext may add more than the permitted number of characters to a text box. In that instance, the form cannot be saved until the excess has been deleted. Additionally, when the text box fails validation because of Autotext exceeding the permitted number of characters in the field, its character count will revert to the last valid saved value. Items to resolve issues with the character count have been added to the backlog to be resolved in a future sprint.
Autotext can now be used in selected fields in other areas of the application.
The Autotext menu and Autotext names can now be used in the following fields: Case Message (Main Case View | Case Info tab), Note (Transfer | Transfer screen), Cancelled Notes (Main Case View | Case Activities | Subpoena tab), Other Id (Main Case View | Evidence tab | Add/Edit Evidence), Last Name and Company (Main Case View | Individuals tab | Add/Edit Individual)
Edits to the Agency Case Number are immediately displayed on the Agency tab. Previously, after editing an Agency Case Number, the new value would only be visible in Main Case View | Agency after the user logged out of LIMS-plus entirely. This has been fixed so that Agency Case Number edits are visible immediately.
Additional Agencies show up immediately in the grid on the Agency tab when added to a Case.
Previously, after adding an Agency to a Case already containing one, the new Agency would not be shown in the grid under the Main Case View | Agency tab until the user either navigated away from the Agency tab or logged out and back in to the application. This has been fixed so that additional Agencies are now shown in the grid immediately after being added.
The DL No. field in the Individuals tab on a Case now has an associated translation key.
Previously, the DL No. field in the Main Case View | Individuals tab did not have a translation key. The appropriate key has been added under Administration | System Administration | Languages/Translations.
In the Add Individual screen, labels for DL State and State apply to the correct fields.
Previously, the labels for DL State and State were swapped in the Main Case View | Individuals | Add Individual. This has been corrected so that both labels are appropriate for the adjacent fields.
The Edit Individual Audit Trail menu displays the correct text for SSN.
Previously, when the Audit Trail button was clicked when editing an Individual in the Main Case View | Individuals tab, the Audit Trail menu option for SSN used the text "lblRace." This has been corrected so the appropriate text is displayed for SSN.
In the Add Evidence Initial Transfer section, Lock Via and Note and Lock for THEN TO location checkboxes have been added. From/To/Then To is cached between Evidence item additions as occurs in v3.7.
Some changes have been made to Main Case View | Evidence | Add Evidence | Initial Transfer to restore functionality from v3.7. Information for FROM, TO, and THEN TO locations is now cached for the user session based on the last entered locations (with exceptions for Kits and Itemization). A checkbox for Lock Via and Note has been added that allows the user to retain entries for the Via dropdowns and the Notes fields within the Initial Transfer. A Lock checkbox was also added that allows the user to retain the entry for the THEN TO location within Initial Transfers. Further information on these changes can be found in the application Help Files.
If a Kit is configured with a default destination, the Kit's value will not update the cached value unless the user edits and resaves the Initial Transfer while saving the Kit's Evidence item. An issue with the Clear Transfer option was discovered where the option does not appropriately clear the cached entries for a subsequent Evidence item. This will be resolved in a future sprint.
The Lock Apply checkbox has been added to the Add Evidence screen to restore v3.7 functionality related to the Save button.
Previously, in Main Case View | Evidence | Add Evidence, multiple items of Evidence could be added by clicking the Save button in succession without making changes to the information on the Add Evidence screen. This functionality is still present but requires that the Lock Apply checkbox be checked. This checkbox essentially locks the Save button as active. If the Lock Apply checkbox is not checked, then after an item of Evidence has been saved, a change must be made to the information on the Add Evidence screen in order to activate the Save button.
In the Audit Trail menu when editing an item of Evidence, both the Container and Source menu options display the correct text.
For the Audit Trail menu in Main Case View | Evidence | Edit Evidence, both Container and Source each have their own separate translation keys and appropriate default text in Administration | System Administration | Languages/Translations. Previously, these options did not appear correctly in the Audit Trail menu.
The Evidence Numbering Schemas allow for Evidence items to be appropriately numbered when the total number of items exceeds 101 in a given Case.
Previously, auto-numbering only worked up to the 101st value in the configured Evidence Number schema, and the Evidence Number needed to be manually entered for every subsequent item added in the Main Case View | Evidence tab. This error has been fixed.
The NCIC Evidence Label now displays correctly in the Evidence screen.
Previously, the NCIC Evidence Label field in Main Case View | Evidence | Add Evidence/Edit Evidence and the Evidence Information pane at the bottom of the Evidence grid only showed a code from the NCIC Property Codes Picklist, not the corresponding description text. This has been fixed so that both code and description are shown in NCIC Evidence Label dropdowns and display fields for all three locations.
When adding a new Request, the Department label displays correctly.
Previously, when adding a new Request to a Case, the label for the Department field (in the Select - Service Name modal window) was blank. This has been fixed so text from the Department label's translation key appears in the correct location.
The text for the tab names in Main Case View | Requests | Request Relations now display appropriately.
Previously, when related entities were viewed for a Request, Request was repeated an extra time before the translation value on the Related Evidence and Related Offenses tabs. An s was also added after the translation value on the Related Offenses tab. This has been fixed so that all Request Relations tab names show only the value from their appropriate translation key.
In the Set Milestone menu for a Request, the Draft Complete, Tech Review, and Admin Review options now have associated translation keys.
Previously, the options available under Main Case View | Requests tab | Request right-click menu | Set Milestone did not have translation keys. The appropriate keys for Draft Complete, Tech Review, and Admin Review have been added under Administration | System Administration | Languages/Translations.
Users can Admin Review their own work when the Service setting Enforce rule 'Analyst cannot Admin Review their own work' is disabled
Previously, a Lab Rep could not Admin Review a Request if they themselves had been assigned to it, even if the Service setting Enforce rule 'Analyst cannot Admin Review their own work' was disabled. This has been fixed so that Lab Reps are prevented from Admin Reviewing their own Requests only if the relevant setting is enabled.
If "Enforce rule 'Analyst cannot Admin Review their own work'" is enabled, a signature is required for Admin Review, and the logged-in user was assigned to the Request, the user will be allowed to attempt to set Admin Review and sign if they enter another user's barcode and PIN. However, they will not be permitted to complete the process.
The Draft Complete milestone can be set on Requests using the Toxicology module without first requiring a screen.
Previously, Requests using the Toxicology module required screen results to be entered before the Request could be set to Draft Complete. This has been corrected, allowing users to set Draft Complete as long as at least one result (screen or confirmation) has been entered.
To mark the Request as Draft Complete when only screen result(s) have been entered, the user must still disable "Confirmation Required" when editing the screen result's findings.
When editing findings on a Request, changes to results must either be saved or cancelled before the user can move to another item. Previously, after result data was entered for an Evidence item or Request in Edit Findings, it was easy to click on another item in the Edit Findings tree view and lose all data entered. Edit Findings has been altered to disable the tree view after the user has made edits to result data, forcing the user to specifically either save or cancel their changes before they can navigate elsewhere.
Two issues were identified with the use of the Esc key to cancel result entry in Edge and with use of Rich Text fields. These issues will be resolved in a future iteration.
The Weight field in the main result screen for the Controlled Substances module allows the appropriate number of characters to be entered.
Previously, the Weight field in the main result screen for the Controlled Substances module allowed entry of more than the 10 characters allowed in that field. This has been resolved so that the Weight field only allows entry of 10 characters or less.
Static Reports are now rendered after the associated Milestone is updated.
Creating a Request's report file after the Final Report Milestone is set allows data to be accessed from the Milestone operation like Date or Rep ID, consistent with Final Reports in 3.7.
The handling of temporary files from non-static reports has been improved.
files from creating or viewing a non-static, un-released report are now housed in ~\app_data\MiscTempFiles instead of RadUploadTempFiles\Temp Files. They are cleaned up if they are over a certain age when new temporary files are created, unless they are open in a separate application at that time.
When the Lab Option Lock Images Related to Draft Complete Requests is disabled, new Attachments can be added to Released Requests.
When the Lock Images Related to Draft Complete Requests, new Attachments cannot be added if the Request has passed the Draft Complete Milestone. Previously in LIMS-plus v3.8, Attachments could not be added to Released Requests when this setting was disabled. This has been resolved to restore the functionality previously seen in LIMS-plus v3.7.
GDPicture was updated to the latest version.
The applications related to uploading and viewing Attachments were updated to the latest version, which includes FIPS-compliance in its features. Previously, a "This implementation is not part of the Windows Platform FIPS validated cryptographic algorithms" error would display when trying to use the application while FIPS Policy Enforcement was enabled on the server.
Please note .xlsx, .csv, .xls, and .doc files are supported by the uploader but not the viewer. These file types can be attached and downloaded using the Multiple Upload option but will not be available for any of the View operations (including Review and Electronic Case File). Additionally, the max page limit for the attachment viewer is 3000 pgs, and files added through single upload should be less than 50 MB. A few issues with Word and Excel based attachments and with Scanning attachments using Edge or the 'Append to Current Document' option were identified that will be resolved in a future iteration.
The Attachment tab now supports user data imported by legacy Mideo LIMS Connect.
The Attachments tab in Main Case View correctly recognizes the userid for an image as provided by legacy Mideo LIMS Connect. Attachments added with legacy LIMS Connect behave in the same way as Attachments added directly through LIMS in terms of actions such as viewing, printing with the Batch Print button, printing in Electronic Case Files, etc.
When Batch Print cannot add an item in the middle of the Attachment list because that item was not uploaded by a valid LIMS-plus Lab Rep, a partial PDF will be generated with the Attachments that came before the invalid Attachment.
V3.8.40 Known Limitations
-Case - Evidence - Add Evidence - Special Handling icon
Special Handling icon won't highlight until the Special Handling window is opened and cancelled once. This will be resolved in a future release.
-Case - Evidence - Add/Edit Evidence - Special Handling
Translation key is missing for Applied Evidence Handling. This will be resolved in a future release.
-LIMS-plus DNA Integration
Request Reason/Priority transfers even if IncludeReason = 0. A current workaround is to manually delete the Priority value before accepting the sample in LIMS-plus DNA. This will be resolved in a future release.
-Case - Evidence - Add Evidence "A1-Z9" schema starts counting from 0 after adding A1-Z9.
Users can manually edit the Evidence Number. This will be resolved in a future release.
-Case – Evidence Performance issues with very high numbers of Evidence items (~10,000).
This problem is unlikely to be encountered in a customer environment but will be resolved in a future sprint.
-Case - Attachments - Batch Print
When Batch Print cannot add an attachment, it uses the attachment description instead of name. This will be resolved in a future release.
-Paged grids throughout the application
Pagination controls disappear when item count drops below currently selected page count. Although this issue is not commonly encountered (most paged grids are in locations that don't need a lot of browsing with page size changing), it will be resolved in a future release.
-Custom Forms - Publish Form
Form always publishes to the first service with a particular name. This will be resolved in a future release.
-File - Accept Evidence - Blood Alcohol and Toxicology Requests
Requests can be accepted without Evidence Source if items are accepted in the wrong order, breaking the relationship set up in Portal. As a workaround, Users can accept items starting at the top of the Accept Evidence screen and working downward, accepting Individuals, Evidence, and Requests in that order. This issue will be resolved in a future release.
-Analysis - Worklists - Create Worklist
Assigned To and Move All Down cannot be used to assign services of different types to a worklist at once. As a workaround, services of different types may be assigned one at a time. This issue will be resolved in a future release.
-V3.8 PORTAL specific tickets:
41371, 48640, 48362, 48402, 48326, 48179, 46074, 48442, 48441
Portal v3.8 has been created for use submitting Case records to LIMS-plus v3.8 The first portion of the Portal v3.8 application has been developed to allow the submission of Case records to LIMS-plus v3.8, providing a replacement for the iPrelog application. Case records can include Case information, Evidence items, Individuals, Offenses, and Requests. Requests can be related to the other Case entities prior to submission. Further information regarding the acceptance of Cases into LIMS-plus v3.8 can be found in the product documentation.
Please be aware, the portion of Portal v3.8 that will adequately replace the iResults application is still in development and will be incorporated in a future iteration of the application. Also, edits made to the Agency Case Number for an Incomplete Submission are not currently retained. If a correction to the Agency Case Number is needed, a new submission must be made. In Case Submission | Requests tab |Add Request, the Department and Service Type dropdowns do not clear after a Request is saved using Save and Add Another. The dropdown fields refresh once a Lab is selected for the subsequent Request. Additionally, the fields within the entity forms for a Case (Evidence, Individuals, Offenses, Requests) will not save the changes if the fields are edited to be cleared. The existing values may be edited, but currently, if a field needs to be cleared once entered, the value should be replaced with a dash or edited in some other way, or the entire entry should be deleted and re-entered. These issues will be resolved in a future iteration of Portal v3.8.
48182, 51469, 51207, 51378, 51845, 51848, 51850, 51918
The administrative portion of the application has been developed for Portal v3.8 which allows Agency Administrators to administer Agency Reps and Agency information for their Agency from within the application.
The Administrative section of Portal v3.8 has been developed to incorporate an Agency Reps section, Add Rep option, and Edit Agency option. The Agency Reps portion allows for the administration of all Agency Reps for the Agency Administrator's Agency, including profile information, roles, and credentials. The Add Rep option (and the Add New Rep option in Agency Reps) allows for the addition and enrollment of a new Rep. The Edit Agency option allows for the Administration of profile information for the Agency Administrator's Agency, such as contact and address.
Agency Reps with access to Portal v3.8 are able to change their passwords from within the application.
An Account Settings option was added to the Agency Rep menu (found by clicking on the name of the logged in Rep) in Portal v3.8. From Account Settings, the password for the logged in Rep can be changed by entering the Old (or Current) Password, entering a New Password that meets the complexity requirements, and confirming the value for New Password.
The logos for Portal v3.8 have been updated.
Updated logos were created to differentiate Portal from Portal v3.8. The logos for this application now accurately reflect Portal v3.8.