Summary
Release Notes
Polaris 7.3 is currently in general release.
New features in Polaris 7.3
- Enabling and Using INN-Reach Visiting Patron
- Creating Purchase Orders Manually
- Expanded Support for Invoices in Leap
- Creating , Editing, and Copying Authority Records in Leap
- Replacing Duplicate Records in Leap
- Consolidated Views on the Leap Item Record Workform
- Use Borrow By Mail in Leap
- Canceling Holds in Held Status
- Using the Picklist Cancelled View
- Improvements to Patron Passwords
- Opting Out of Self-Registration Duplicate Detection
- Updates to the OCLC ILL Integration
- Support for Azure AD Authentication with Leap SSO
- Access to LX Starter
- For more information on these new features, see the What's New in Polaris and Leap 7.3 document
New and Modified Polaris Administrative Settings
- The following table lists the new and modified profiles, parameters, and permissions in Polaris Administration.
Setting | Purpose | Level |
Modified Parameter | ||
ILL options | The Polaris OCLC ILL integration now supports the latest standard (ISO 18626) for ILL transactions. If you use OCLC’s ILL Direct Request service, you must configure two new settings on the ILL options dialog. For details, see Updates to the OCLC ILL Integration. | System, Library, Branch |
New Parameters | ||
Permit cancellation on: Held | Specifies whether patrons and staff can cancel hold requests with a status of Held. For details, see Canceling Holds in Held Status. | System |
INN-Reach: Enable visiting patron check out | Specifies whether you can perform visiting patron check-outs in Leap. When this parameter is enabled, the Visiting Patron Check Out (INN-Reach) option appears in the Utilities menu in Leap. For details, see Enabling and Using INN-Reach Visiting Patron. | System, Library, Branch |
New Profile | ||
Perform duplicate detection | Specifies whether the system performs duplicate detection when patrons selfregister using PowerPAC, MobilePAC, or Polaris API. For details, see Opting Out of Self-Registration Duplicate Detection. | System, Library, Branch |
Polaris API changes
- The following methods have been updated:
- HoldRequestCancel
- This public method now cancels a specific hold request or cancels all local hold requests for a specific patron whose hold requests have a status of held (6), library-enabled. This method still cancels the statuses:
- inactive (1)
- active (2)
- pending (4)
- shipped (5)
- not supplied (7) library-enabled
- located (18) library-enabled
- Note: Now, submitting a zero for the RequestID forces a “cancel all” operation.
- This public method now cancels a specific hold request or cancels all local hold requests for a specific patron whose hold requests have a status of held (6), library-enabled. This method still cancels the statuses:
- PatronBasicDataGet
- The method now returns both the patron code and patron statistical class values.
- PatronRegistrationCreateData
- The method now allows patrons to selfregister and generate a barcode, even
if a matching patron record exists. This happens only when the SA setting Profiles > PAC > Patron Access Options, self-registration tab has duplicate detection disabled.
- The method now allows patrons to selfregister and generate a barcode, even
- HoldRequestCancel
- PatronRegistrationUpdate
- The method now returns patron registration information, such as name, username, and barcode.
- PatronRegistrationUpdate
- For more information on these updated methods, see the Polaris API Reference Guide 7.3 document.
Preparing to update your system
System Requirements
SQL Server 2014 or above is recommended for Polaris 5.6+ due to improved Unicode performance.
Windows 7 is End of Life by Microsoft in January 2020, customers are recommended to upgrade to Windows 10.
Polaris 6.4 is the last supported version on Windows 7
Polaris Leap on 6.6+ requires .Net Core 3.1.x which only supports Windows 2012 R2+.
The MyLibrary and Payments Microservices were also updated to .Net Core 3.1.x in Polaris 6.7 and will require Windows 2012 R2+.
PAPI was also updated in Polaris 7.0 to .Net Core 3.1.x and will require Windows 2012 R2+
Polaris 7.1 will be the last supported version for SQL Server 2012
Polaris 7.1 has a web based Polaris SA, it requires OAuth to login. To use OAuth, Windows Server 2019+ is required
Windows Server 2022 was tested by Polaris DevOps and is working with Polaris 7.1, full testing will not be done until the next Polaris version
Windows 11 was tested by Polaris DevOps and are working with Polaris 7.1 and Polaris 7.2. We also have several customers running Windows 11 already
Windows Server 2022 is working with Polaris, however Microsoft has removed support for local SMTP and an external SMTP server will now be required
Polaris 7.2 has included OAuth support with Leap. To use OAuth, Windows Server 2019+ is required for the server that runs ADFS.
- Polaris 7.3 is the last supported version for Windows 8.1.
- Detailed requirement information can be found in the Polaris Operating System Requirements solution
NOTE: When the new Polaris release is installed on a workstation, the file path changes from 7.2 to 7.3 as in the following examples:
- C:\ProgramData\Polaris\7.3
- C:\Program Files\Polaris\7.3
- C:\Program Files (x86)\Polaris\7.3
Updgrading Your System
In order to schedule your upgrade to Polaris 7.3, please log a ticket with your Site Manager or utilize the Polaris Upgrade Request Form.