> 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/external-workspace-management-overview.md). # External Workspace Management Overview ## Overview The External Workspace Management functionality enables the management of LogicNets projects and workspaces outside the LogicNets Designer Environment. ## System Definitions ### Document Management System (DMS) * Provides a UI to manage LogicNets projects in the DMS * Allows creation and deletion of projects * Handles version management of projects and avoids parallel editing of the same project * Handles access rights * Allows selecting of a project for editing * Starts the LogicNets designer environment to edit the selected project * Offers a web-service for loading projects * Offers a web-service for saving projects ### LogicNets Design Environment (LDE) * Creates a temporary workspace for all selected projects * Loads the actual project data from the document management system and starts the designer UI * Supports all normal LogicNets Designer functionality * Allows the user the close the designer * Saves the project data to the document management system and closes the designer UI ## Detailed Process Flow The DMS manages the workflow of an LogicNets project. When user open a LogicNets project in the DMS, it launches the LogicNets Designer with a DMS session id. The LogicNets Designer then receives the start request and places a web request with this DMS session id to pull the related LogicNets project and dependencies. The purpose of this web service is to provide a gateway for LogicNets Designer to pull the LogicNets project from the DMS. The LogicNets Design Environment (LDE) provides an URL interface to start the LDE by the DMS. The DMS must provide an interface to load and save projects. The DMS interface are REST services. The LDE allows to configure https and certificates in case the DMS REST interface requires this. The DMS can also request the LDE to publish a project. The LDE provides a REST service for this purpose. Since the publishing process will take some time this call will return immediately. The LDE will call the DMS to save the published package. See the following articles for more information: * [Open LogicNets Design Environment Flow](/release-9/platform-documentation/advanced-topics/system-integration/external-workspace-management-open-lde-flow.md) * [Publish Runtime Application Flow](/release-9/platform-documentation/advanced-topics/system-integration/external-workspace-management-publish-runtime-application-flow.md) * [Using the LogicNets Designer](/release-9/platform-documentation/advanced-topics/system-integration/using-the-logicnets-designer-via-an-external-workspace-management-system.md) --- # 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/external-workspace-management-overview.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.