> For the complete documentation index, see [llms.txt](https://community-test.logicnets.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://community-test.logicnets.com/release-9/news/latest-news/release-notes-logicnets-release-7-3.md). # Release Notes: LogicNets Release 7.3 Release 7.3 includes the new features/functionality described below including the following major enhancements. Download the full Release Notes here. ### Multi-language Support The multi-language support feature allows you to provide language translations of the text in your modeled applications. You can create these translations in the Designer, or you can create them in Excel and import them into the Designer. This functionality includes default language configurations in the LogicNets Access Management module, where you can manage the default language settings for users and user groups. ### Cron Job Scheduler and Monitor This release introduces new Cron Job Scheduler and Monitor functionality that allows you to create cron jobs in logicnets and configure them using the Scheduler Monitor. Additionally, the Scheduler Monitor includes a monitoring function that displays the status of active cron jobs, allows you to actively disable or run them out of sequence, and also allows you to review details about previous runs. ### Logicnets as Functions It is now possible to model your logicnets as functions. A function is callable logicnet with a defined interface for inputs and outputs. The function logicnet can be called multiple times within an application, each time using different values for the required input and output parameters. Functions support the sharing and repeating of common logic, which makes the design task quicker and more efficient. You can use functions in conjunction with the library concept to offer reusable library modules to share between multiple projects. ### External Search The External Search feature allows you to include in your modeled applications the ability to search for documentation outside of LogicNets; for example, in the application's Knowledge Center or on an external website. The system returns search results as a hyperlink and includes a snippet of the matching documentation, which can be presented in the application. ### Web Services Framework This release includes a new Web Services Framework that allows you to easily build your application as a web service API to connect your application to others outside of LogicNets. The API can range from simple API to a complete RESTful API. ## Attachments * [Release notes - LogicNets release 7.3.pdf](https://github.com/logicnets/community-portal/tree/release-9/docs/.gitbook/assets/80l15g-Release-notes---LogicNets-release-7.3.pdf) --- # 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://community-test.logicnets.com/release-9/news/latest-news/release-notes-logicnets-release-7-3.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.