> For the complete documentation index, see [llms.txt](https://knowledgebase.flaik.com/flaik-knowledge-base/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledgebase.flaik.com/flaik-knowledge-base/for-it-specialists/pos-integration-how-flaik-connects-to-your-pos/pos-integration-api-overview/release-notes/2.5.0.0.md). # 2.5.0.0 ### Installation * [Installation directory](https://drive.google.com/drive/folders/1j-eX5bd6AKdeKSv-5Un7yESbPaRQznBz) * This version is recommended for all POS Types * This release requires both flaik SQL scripts to be run in order * This release requires both Resort POS SQL scripts to be run in order ## \[2.5.0.0] - 2024-08-09 This release represents a significant update to the flaik Resort Service API. Along with regular bug fixes and performance improvements this update reduces the reliance on having a flaik specific database on Resort Infrastructure. For resorts using RTP|One this release adds new functionality for Lesson Sales and Employee Profile Management. It is recommended for all Resort partners. > Note: This install requires a full uninstall of the previous flaik ResortServiceAPI. Please reach out to the flaik team if you need assistance with this. ### New * Introduced new endpoints to retrieve POS configuration allowing resort specific settings to be validated. * Introduced framework for RTP|One resorts to handle Private Lesson sales from flaik. \[Instructor Booking] * Endpoint to retrieve product pricing and taxes for followed products. * Endpoint to validate Customer IP Code in RTPOne. * Endpoint to retrieve family members and head of household from RTPOne. * Endpoint to post a completed flaik private lesson transaction to RTPOne. * Introduced ability to synchronize HRIS systems with RTP|One via the flaik ResortServiceAPI * Create, Add Personal details * Name, Date of Birth, Gender * Primary Email address * Phone Number * Address * Create, update and delete Employee Profiles * Include Alternate ID profile * Ability to identify Guests in some RTP|One resorts that have Lift Access issued without a prepaid Access profile. * Updated Person Model to allow for contact information to be derived from an Order Header where that information is missing in a Guest profile or existing Guest relationship. ### Updates * .NET 7 to .NET 8 migration * Updated many data types to be explicitly declared to align with new .NET 8 * Removed Dependency for Employee Database and configuration to be declared in Appsettings.json file ### Fixes * Issue in RTP|One resorts where lessons could appear as cancelled after the lesson date * Issue when syncing Instructor Schedules to RTP|One * Issue in Siriusware where multi-day lessons did not come across for day 2+ * Encryption routine for Appsettings.json file - adjusting one string will not re-encrypt other settings anymore. --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://knowledgebase.flaik.com/flaik-knowledge-base/for-it-specialists/pos-integration-how-flaik-connects-to-your-pos/pos-integration-api-overview/release-notes/2.5.0.0.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.