> 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/advanced-topics/system-integration/using-the-logicnets-designer-via-an-external-workspace-management-system.md). # Using the LogicNets Designer via an External Workspace Management System All of the LogicNets Designer features are available when you are using it through an External Workspace Management System, with a few exceptions highlighted below. ## Basic Functionality ### Opening and Closing the Designer Creating a new LogicNets project and opening an existing project are both tasks initiated in your Document Management System. Check the appropriate user manual of the DMS for instructions on how to open or create a LogicNets project. When the DMS opens the LogicNets project the LogicNets Designer starts loading the project(s) from the DMS. The system displays a progress bar. When the projects are loaded the Designer application is started, and in the DMS mode a ‘Save’ and ‘Cancel’ button will appear. When the cancel button is used nothing is saved back to the DMS-system. The LogicNets Designer is closed and a page is shown to close the browser-tab (this page is shown since most browser-versions do not allow closing a browser-tab automatically). When the save-button is used the projects are saved back to the DMS-system, the LogicNets Designer will be closed and a page is shown to close the browser-tab. ### Troubleshooting the DMS-to-LogicNets Connection #### Designer is Not Closed Properly During the loading of projects an error page will be shown when the LogicNets Designer is started with a DMS-session-id that has been used previously and if the previous LogicNets Designer session wasn’t closed properly (using the ‘Save’ or ‘Cancel’ button). When the “Cancel”-button is pressed the loading of projects is aborted and a page is shown to close the browser-tab. If the “Continue previous session”-button is used the projects are not reloaded from the DMS, but the LogicNets Designer is started with the previous state of the projects (as last known and stored by LogicNets). The Reload-button will reload the projects from the DMS and starts the LogicNets Designer. #### The Loaded Projects are Corrupt An error message will be shown when the DMS returns corrupt projects. The LogicNets Designer cannot be started. #### Connect Setup to the DMS Web Service Failed An error message is shown in case an error occurred during the connection-setup to the DMS. In most cases this error is caused by a misconfiguration of the DMS connection. In all these cases you must connect your system-administrator for further information and help. The most common error messages are below: | Error Message | Description | | --------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Unknown connect error. | The host can be reached, but the socket on the DMS is not opened for receiving a connection. | | Cannot connect. | The DMS hostname is not correctly configured in case HTTPS is used. | | Host not found. | The DMS hostname is not correctly configured in case HTTP is used. | | Error initializing locations. | Path to HTTPS server certificate is not valid or the certificates in that configured path are not valid. | | Unable to get local issuer certificate. | The server certificate cannot be validated. Please check whether all certificates in the server certificate chain are saved in the configured certificate file. | | Could not set client certificate key. | The configured client certificate private key is corrupt or the private key does not belong to the configured client certificate. | | Failed to set client certificate. | The configured client certificate is corrupt. | | HTTP Error 403.16 - Forbidden | Your client certificate is either not trusted or is invalid. | ## Designer Functionality ### Tree The Designer shows a file and folder-tree in the left panel. This tree shows all the projects existing in the workspace. (Note that compared to the standalone Designer, this workspace does not allow the user to create, add or delete projects. It is also not possible to create folders in the root of the tree. The DMS can mark one or more projects as read-only. In that case read-only folders and files (logicnets, data-table and other resources) cannot be edited and the name of the files and folders are greyed out. It is not possible to paste, paste-link or create new files or folders in a read-only project. However, it is possible to copy a file or folder from the read-only project to a non-read-only project. In case a file or folder is copy-paste-linked from a read-only project to a non-read-only-project, the file or folder is also marked as read-only in the destination project. ### Project Properties In the DMS-connected Designer it is not possible to change the title or version of a project. This is true for both editable and non-read-only-projects. The project title and version is created and maintained by the DMS system. If the DMS system updates the title or version then the title and version will be updated in the LogicNets Designer too during the loading of the projects. ### LogicNets Designer Tab The LogicNets Designer tab behaves differently for read-only logicnets. All menu buttons on the top are shown as disabled and the context menu (accessible via right-mouse-click) is not available. ### Node and Part Details It is possible view node and part parameters of nodes in a read-only logicnet. However, it is not possible to change any of the parameters. --- # 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/advanced-topics/system-integration/using-the-logicnets-designer-via-an-external-workspace-management-system.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.