> For the complete documentation index, see [llms.txt](https://docs.spectralink.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.spectralink.net/amie-essentials/release-notes/sam-1-7-0.md). # SAM 1.7.0 SAM Version: 1.7.0.xxx.860 For use with Versity versions: * Versity 92 Series R1.5 using Android 10 * Versity 95/96 Series R2.5 using Android 10 {% hint style="info" %} **upgrading anomaly** When upgrading to 1.7 and if using FQDN and also updating phones to R2.1 or above, you must generate a new CSR/cert and then push it to the phones in order for the phones to connect to SAM. {% endhint %} {% hint style="info" %} **SAM compatibility** SAM 1.7 was tested with Versity 92 Series 1.5 and Versity 95/96 Series 2.5. However, this version of SAM should work with any Versity smartphone software version. Any options that appear in SAM and are not in the phone menus will be ignored by the phone. Any options that are in the phone but not in SAM will be ignored by SAM unless programmed through Custom Attributes. {% endhint %} {% hint style="info" %} **What does the “xxx” stand for?** You will notice an “xxx” in the version number above. It signifies the build version of the VM the SAM software is installed on. When the SAM version is loaded at your site, the number will reflect the VM version in use at your site. SAM build versions change but VM versions do not change upon SAM software upgrade. {% endhint %} {% hint style="info" %} **Updating SAM to the current release** You will see two files for this and future releases. The upgrade version is an incremental release used to update code to the next released version. It is a smaller file with a faster download time and recommended for incremental updates. Always use the appropriate incremental file for your current release. i.e. Do not skip versions. Use the next released version. The New install file contains the full code for a new SAM VM and software deployment. {% endhint %} {% hint style="warning" %} **The full release version will install a new instance of SAM on the VM** The New install version will install a new instance of SAM with an empty database. If SAM is already deployed in your facility, do not try to “upgrade” with the New install version. Use the upgrade version unless you intend to start over. {% endhint %} {% hint style="warning" %} **Your account number is critical to SAM setup** Due to repeated situations where the SAM server was installed with a phony customer account number, a caution note is added here to help all installers understand that the correct customer account number will prevent future configuration and installation problems. Spectralink assigns a unique account number to each customer which is linked to your SAM license. If a different account number is used to configure the SAM server and it is not the assigned number, the installation of the SAM license will fail and the entire server must be reinstalled. {% endhint %} ## Enhancement ### Barcode #### Keyboard injection A new Data Manipulation setting for general and ScanFlex configuration. Formerly always on and not configurable, keyboard injection (barcode capture to a text field) can now be turned off. It is on by default. ## Fixes Key Summary SAM-942 Corrected upgrade version SAM-899 Log4j Security Fixes --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.spectralink.net/amie-essentials/release-notes/sam-1-7-0.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.