> 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/platform-documentation/system-administration/package-installation/package-installer-configuration.md). # Package Installer Configuration ## Introduction The Package Installer tool centralizes your ability to manage published packages, and it allows those users with access to view and manage all packages that are available on a LogicNets installation. It can be used to install new packages and make them available to users. The Package Installer can be used in conjunction with configuration options set up in your project. ## Configuration Options In addition to managing packages your users see, you can manage the ability for administrative users to open your published applications in the Package Installer. To do this you set configuration properties at the Package Installer Framework project level. The following sections walk you through how to do that. ## Set Framework To create a custom version of the Package Installer, you create a project and set the *PackageInstallerFramework* as the framework option for your project. 1. In your Designer, click the icon to add a new project. From the list of framework options, go to *Advanced* and click the ***Blank*** project option. 2. Name your project and click ***Create***. 3. The system will allow you to set the *Type* and *Framework* for your project. Use the dropdown menus to select ***based on framework*** for the *Type*, and select ***PackageInstallerFramework*** for the *Framework*. 4. Click ***Create***. ![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-d2a21e3ceb4867e4123dd845e4a7aea7408a3724%2F57fbcbf4-6a3f-4017-93f9-040a6703caac.png?alt=media) 5. Again, click the name of your package and click the ***Modify*** button. 6. Click the ***Framework*** tab to update the configuration options possible. ![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-6e0f517013783d84eaf6976fbc327bf624f4cd7d%2F90f290e7-860b-4f55-a9fc-4954720f61bf.png?alt=media) ## Start Package in Admin Mode To allow administrative users to open your package in admin mode from the Package Installer, set the ***Show start in admin mode button*** dropdown menu to *Yes*. The default value is *No*. NOTE: The system will only start a package in admin mode if that package is active. ![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-da1302ea789db9f589cdf689e55d9591903c1770%2F06af7a75-b833-4170-b3a3-7f3bb6df1ee1.png?alt=media) ## Show Scope in Category List/Set Scope *Scope* provides an additional field you can use together with *category* to more clearly identify your packages. If you have multiple installations or companies within one installation you can use this field to avoid creating packages with a conflicting category. When used together, the scope and category determine the way the system groups packages: in the Package Installer the system makes active one package active per scope/category combination. The system also uses this category/scope combination to move package data from a previously active package of the same combination. The category is the name of your package and you set the scope at the company level. ![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-c24c161575202551023ed0496402bdb5ecfeffbb%2Fce83fb12-1935-458d-a95d-d8a8e10cd87f.png?alt=media) 1\. When you want to use scope in combination with category, you set the category in the project *Framework* tab and then you go to your dashboard and click on the *System Configuration* tool. ![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-ba8fcd0977b8da5b6640bd2cacd279a8caa21935%2F37b504c7-b008-40c4-b287-4d81ab987615.png?alt=media) 2\. Click the ***Designer*** tab and enter the scope in the *Category scope* field. ![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-b1ff0b54a479c4f18a8637bb92b34d36e4353a51%2Fe23040e1-3311-48a8-a439-57fc22112b48.png?alt=media) 3\. Click ***Save*** to save your changes and then return to your project in the Designer. 4. When you publish your project and click to see your published package details the system shows you the scope and category. The category is the name of your project. ![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-6645b403c496f5a7718afcecbcd6c8449160582a%2F8a4c8a7b-a677-4848-bb68-20e8f34d820e.png?alt=media) ![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-1f1f4092099f1725939bd3a2f95104c88fb1ff47%2F81b0319d-9458-4dbf-9512-727641a7b79c.png?alt=media) ## Hide Tabs You have the option of hiding the *Start code* and/or *Tag* tabs. To do this, click the checkbox in the *Hide tabs* section. If you hide both Start code and Tags, they system will not show these options in the installer. ![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-c4e1eee912f8145f65adb554036559eb5ddf592f%2F28b055bc-4cbd-46c6-87b1-06432d18375d.png?alt=media) ## Package Install Rules You can use this table to specify any installation rules; for example, if your package name contains a particular term. Enter the rule in the ***Rule*** field and enter in the ***Message*** field a message you want the system to display when the rule is satisfied. The installation rule can contain xpath. ![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-1d24c477bd51ef5962a4d86637753fa9e8c70b4b%2F40c7ba6c-945d-4b87-8d4e-a4a078fef78d.png?alt=media) ## Package Uninstall Rules This table allows you to specify rules for the uninstall of your package; for example, if your package name contains a particular term. Enter the rule in the ***Rule*** field and enter in the ***Message*** field the message you want the system to display when the rule is satisfied. The rule can contain xpath. ![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-e6495f3390f4165b3dc024e9d70bf4a296a4a764%2F046d518b-fcb8-455c-8b0e-5d863f795fa4.png?alt=media) ## Package Activate Rules The *Package activate rules* table allows you to set any rules for activating your package; for example, if your package name contains a particular term. You enter the rules in the ***Rule*** field and in the ***Message*** field enter the message the system will display when the rule is satisfied. The rule can contain xpath. ![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-955975734e2f26146761c3c7a34de60baa757ba5%2F659f1671-00eb-4995-aaeb-e3a7379a7611.png?alt=media) ## Package Deactivate Rules The *Package deactivate rules* table allows you to set any rules for deactivating your package; for example, if your package name contains a particular term. You enter the rules in the ***Rule*** field and in the ***Message*** field enter the message the system will display when the rule is satisfied. The rule can contain xpath. ![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-cdb37fd706d2a6e4db3ba0d6108ea5420822d53c%2Fb4f3b7d5-60f8-4552-a995-824452b52a18.png?alt=media) ## Categories Filter The *Categories filter* option allows you to filter the list of packages shown in the categories section; for example, if you want to show the packages with scope 'Local' only, then you enter a condition here to filter the packages with scope local. --- # 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/platform-documentation/system-administration/package-installation/package-installer-configuration.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.