1.23 The Solution SHALL provide the capability to M convert an existing record, with prints, into any other transaction type submission (e.g., converting an IDN TOT to a CRM/REG/APP/DNS or a CRM to a REG/APP/DNS), as required by the County. 1.24 SHALL have passive communication M The Solution capability (i.e. chat window) for the LACRIS Help Desk to communicate with the User. 1.25 The Solution SHALL have the ability to import a M NIST file and print a copy of the booking slip and finger/palm print cards. 1.26 The Solution SHALL store all transaction files M for each local Livescan device, of only the transaction files currently retained on that device. Transaction files stored on the local livescan can be printed even if network connectivity to the central server is not available. 1.27 The Solution store transaction files from M SHALL every Livescan device within the central server (including a backup), for a County-designated duration. 1.28 The Solution be capable of utilizing M SHALL permission-based context menus for administrative tasks to include, but not be limited to, opening the data directory folder of a highlighted transaction record selected on the inventory screen, deletion of highlighted transaction records, and export of highlighted transaction records to a NIST-compliant file.
1.23 The Solution SHALL provide the capability to convert an existing record, with prints, into any other transaction type submission (e.g., converting an IDN TOT to a CRM/REG/APP/DNS or a CRM to a REG/APP/DNS), as required by the County. M 1.24 The Solution SHALL have passive communication capability (i.e. chat window) for the LACRIS Help Desk to communicate with the User. M 1.25 The Solution SHALL have the ability to import a NIST file and print a copy of the booking slip and finger/palm print cards. M 1.26 The Solution SHALL store all transaction files for each local Livescan device, of only the transaction files currently retained on that device. Transaction files stored on the local livescan can be printed even if network connectivity to the central server is not available. M 1.27 The Solution SHALL store transaction files from every Livescan device within the central server (including a backup), for a County-designated duration. M 1.28 The Solution SHALL be capable of utilizing permission-based context menus for administrative tasks to include, but not be limited to, opening the data directory folder of a highlighted transaction record selected on the inventory screen, deletion of highlighted transaction records, and export of highlighted transaction records to a NIST-compliant file. M