> 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/system-settings/external-references-system-map-and-process-overview.md).

# External References System Map and Process Overview

In LogicNets-based applications, users may need to check more detailed information or view-related information on the question or current context. You can store this information as a resource, which is typically a piece of formatted text or graphics. Resources are stored in different locations, including the following:

* in the LogicNets application itself in the *content* folder
* in the LogicNets KnowledgeCenter
* in an external location, such as a content-management system

This article explains the interaction between an external content/document management system (DMS), the LogicNets Designer and the runtime application.

### During "Design" Phase

1. The Designer user starts from the DMS system via the LogicNets Designer Starter.
2. The Designer user can create a new reference in the LogicNets Designer by selecting a pre-configured source. The LogicNets Designer starts the External Reference Browser and selects a reference.
3. The External Reference Browser sends the selected reference meta back to the LogicNets Designer in JSON format.
4. The Designer user saves this information in the existing references structures in the logicnets. This is a Lua-based data structure.
5. When the Designer user closes the LogicNets Designer application, the system scans all of the logicnets references and stores them in a meta-xml file. The project, including this meta-xml file, is saved back into the DMS system.
6. The DMS user may update some properties of the meta-xml file on the DMS system.

### During "Publish" Phase

1. The DMS system can ask the LogicNets system to publish a project. The LogicNets system returns a published package and the corresponding meta-xml.
2. The DMS user may update some properties of the meta-xml file on the DMS system.
3. The DMS system sends the published package (+XML) to an end-user-production system and installs the package.

### During "Run-time" Phase

1. The end user starts the application and the LogicNets runtime engine reads the meta-xml, converts it to Lua-structure, and stores it in the session for quick reference.
2. When the end user navigates to a reference link, the LogicNets runtime engine detects the reference details in the logicnet and checks whether there are updated properties available in the references structure in the session.
3. The Logicnets runtime engine uses the latest properties and renders the link content on screen.

### Configuration

You can find information on configuring external reference sources [here](/release-9/platform-documentation/system-administration/system-settings/external-reference-sources.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/system-administration/system-settings/external-references-system-map-and-process-overview.md?ask=<question>&goal=<user_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.