> 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/deployment-manager/parallel-version-support-setting-prefix-and-postfixes-start-codes-and-library-links.md). # Parallel Version Support: Setting Prefix and Postfixes, Start Codes, and Library Links ## Description In v8.3, LogicNets introduced parallel version support functionality as part of the Deployment Manager. This adds support for publishing package names using startcode prefixes and postfixes, allowing you to create multiple versions of an application without overwriting previous ones. **Used With:** This function is used in the Deployment Manager. ## Details When you set the deployment configuration in the Deployment Manager you can configure prefix and postfix labels that the system will apply to all package names, start codes, and libraries in the configuration as part of the image, giving you greater control of what the system updates. This allows you to create updated or differentiated versions of an application without overwriting previous ones. The system also applies the prefix and postfix to associated frameworks in the package. With this function, you do not need to edit the start codes in your published projects and can still publish a unique version of the same application. You can also update related library applications and publish them without having to update the link between a project and a library. As an example, say you have a shared workspace with the following projects: * *Library A* * *Library B* * *Framework C* * *Framework D*, which is based on *Framework C*. * *App E*, which is based on *Framework D* and has two library links to package *Library A* and *Library B*. It also has startcode *appe*. Your deployment configuration looks like this: | Project | Revision | Start Code | Package Name | | ------------- | -------- | ---------- | ------------ | | *Library A* | 1 | | *LibraryA* | | *Library B* | 1 | | *LibraryB* | | *Framework D* | 1 | | *FrameworkD* | | *App E* | 1 | *start* | *AppE* | Note: "Framework C" is not part of the configuration. Before the prefix and postfix support, the resulting package list in the deployment image would look like the following: * *LibraryA* * *LibraryB* * *FrameworkD* and it is dependent on *FrameworkC* * *AppE* with start code "start" and it is dependent on *FrameworkD*, *FrameworkC*, *LibraryA*, *LibraryB* With the prefix and postfix functionality, you can create new packages with prefixes and postfixes; for example, you could use a prefix of *apps/V1/* and startcode postfix of *V1*. The resulting packages would look as follows: * *apps/V1/LibraryA* * *apps/V1/LibraryB* * *apps/V1/FrameworkD* and it is dependent on *FrameworkC* * *apps/V1/AppE* with startcode *startV1* and it is dependent on *apps/V1/FrameworkD*, *FrameworkC*, *apps/V1/LibraryA*, *apps/V1/LibraryB* Since *FrameworkC* is not part of this configuration, the system does not update the framework dependency of *FrameworkC* in the *Framework D* project. To remind you in this case, the deployment editor displays a warning that a dependent package is not part of the configuration. ## Create a New Configuration A configuration contains details of all the workspaces, projects, revisions, packages, and deployment images associated with that configuration. To add a new configuration, take the following actions: 1. Add a new configuration by clicking the ***+*** sign on the left side panel in the Deployment Manager. The system opens a popup window. 2. Enter the configuration name and optional description details. Note that the configuration name must be unique, and it can only contain lowercase letters, numbers, underscores, hyphens, and a dot. The system stores this configuration name in the manifest table in the registry. 3. Click the ***+*** icon in the green icon below the line to add an additional line. Once you have completed entering your information, click ***Create***. ![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-a9a00cc1760cc8bb511eb1134f8247b7c61138f2%2F58099700-3fcc-42a8-9626-06d825abd24e.png?alt=media) The system displays a list of all configured design instances on the dashboard in the ***Instance*** dropdown menu. Using this dropdown menu, add the list of projects and their version to the configuration screen. The system displays the available list of repositories in the repository dropdown based on the instance you select. You can choose the project and version to be deployed, and the system auto-populates the start code, framework, library projects, and package name field. You can change the package name, as needed, and package names can consist of lowercase letters, numbers, hyphens, underscores, or a dot. The system displays any validation errors. ![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-0b58954bf29163ee2c3ad263e1964ed9190c6aba%2Fe7702142-2b21-4de5-9bfa-82a56aab5d08.png?alt=media) ![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-3754aefa1dcb12b00ce1c65031cd884cc9b1416c%2F808e6dfc-fb34-41ff-abbb-a6910127f7eb.png?alt=media) ![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-e6f0ac30f25dcdaa6f42aff97724f58c3bd9f64a%2F2b4ddd62-8ef3-4763-b76f-ecad9a01a171.png?alt=media) ![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-4e42cc7373f9749d95bb0028bd9a1fb3ea317194%2Fcee525d6-4439-4900-a77f-6afba453db61.png?alt=media) ## Modify a Configuration You can modify an existing configuration, including modifying, adding, or deleting the package and startcode prefix and postfix values. When you save the configuration update, the system updates the package name, library projects, framework, and startcode with these new values. ![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-d3101ec384a2678086d834f5d780d8db18755d4d%2F729bb457-f9cf-47c4-b3fe-5e2d05089884.png?alt=media) ![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-e446295adca51f962fbebc4700bdc2b006464cb9%2Fc8bd03e3-a6fa-451c-acc2-d651a78017bd.png?alt=media) **Create an Image** ![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-a86d6a64db97f7f564f20e726c9c8a06a29d8f00%2F29cf2442-6509-4d25-8d41-f7d1ebf2d42b.png?alt=media) ![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-f680c5ecea4f6183e722ae5025bfa227eafa3f2b%2F4b063638-788d-4218-a14c-8d13cc2d564e.png?alt=media) **Deploy an Image** ![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-cbd3023ac0de1cee493faacd30dff7b88b10e500%2Fdeb0a4e3-3339-4712-b373-ba10dce08d61.png?alt=media) ![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-6cb77db527f9679cf7797346e38d8637d34ec088%2F846b3c75-bcc6-4c27-9aac-bd29347622cd.png?alt=media) ![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-7bd7549b95574eeb399e1ae6d10f6edc8bf7e5b9%2Fbeefa9c2-19e3-41bb-9629-64acb19ce835.png?alt=media) ![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-3461e15e53df291dbfb11fb74c3be4aa675d39d7%2F783e0012-f6b0-4227-b935-dfff19626e0a.png?alt=media) ![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-4e000ef4372b896a19130f737d2f9184da1c9b88%2F099da870-6297-41bb-9875-e322beb7ef8b.png?alt=media) --- # 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/deployment-manager/parallel-version-support-setting-prefix-and-postfixes-start-codes-and-library-links.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.