Modified content

Author: Donna-Marie Smith

content/en/docs/2025.1/Guides/user-guides/user-interfaces/gateway/Admin/studio-export/_index.md

@@ -9,7 +9,7 @@ weight: 50
 
 ## Summary
 
-Studio Export is a feature that enables one or more flowsto be exported into a Studio Package file, which may be used for achieving purposes, or importing flows into another CORTEX Studio. A Studio Package file may contain a mixture of distinct CORTEX and CORTEX 7 flows.
+Studio Export is a feature that enables one or more flows to be exported into a Studio Package file, which may be used for archiving purposes, or [importing][Studio Import] flows into another {{% ctx %}} Studio. A Studio Package file may contain a mixture of distinct {{% ctx %}} and {{% ctx %}} 7 flows.
 
 |                              |                                                                 |
 |------------------------------|-----------------------------------------------------------------|
@@ -21,9 +21,9 @@ Studio Export is a feature that enables one or more flowsto be exported into a S
 
 Any flow in the system may be exported; it is not necessary for the administrator to have View or Edit authorisation for the flows to be exported.
 
-Individual flows are selected by clicking by clicking the Export? column adjacent to the flow to be exported. If a Group is selected, then all the flows contained in that Group, and any sub-Groups, will be implicitly set; any implicitly set may be individually deselected by clicking the checkbox adjacent to the flow.
+Individual flows are selected by clicking the checkbox in the `Export?` column adjacent to the flow to be exported. If a group is selected, then all the flows contained in that group, and any sub-groups, will be implicitly set; any implicitly set may be individually deselected by clicking the checkbox adjacent to the flow.
 
-Clicking Export will create the Studio Package from the Master Versions of the selected flows in the Master Repository, including their Group hierarchy, and then download the package to the host’s browser as file named export.studiopkg or export (<n>).studiopkg, where <n> represents an integer to avoid naming conflict with other Studio Package files contained in the same folder.
+Clicking `Export` will create the Studio Package from the Master Versions in the Master Repository of the selected flows, including their group hierarchy, and then download the package to the host’s browser as a file named `export.studiopkg` or `export <n>.studiopkg`, where `<n>` represents an integer to avoid naming conflict with other Studio Package files contained in the same folder.
 
 ## Remarks
 
@@ -42,3 +42,4 @@ TODO
 * [Export Individual Flows][Export Individual Flows tutorial]
 
 [Export Individual Flows tutorial]: {{< url path="Cortex.Tutorials.Administration.StudioExport.ExportIndividualFlows" >}}
+[Studio Import]: {{< url path="Cortex.Guides.UserGuides.UserInterfaces.Gateway.Admin.StudioImport.MainDoc" >}}

content/en/docs/2025.1/Guides/user-guides/user-interfaces/gateway/Admin/studio-import/_index.md

@@ -9,7 +9,7 @@ weight: 25
 
 ## Summary
 
-Studio Import is a feature that enables individual flows, contained in a Studio Package on the local host, to be imported into {{% ctx %}} Gateway.
+Studio Import is a feature that enables individual flows, contained in a Studio Package, to be imported into {{% ctx %}} Studio.
 
 |                              |                                                                 |
 |------------------------------|-----------------------------------------------------------------|
@@ -19,13 +19,13 @@ Studio Import is a feature that enables individual flows, contained in a Studio
 
 {{< figure src="/images/Studio Import.png" title="Studio Import" >}}
 
-Individual flows contained in the Studio Package may be individually selected for importing into CORTEX Studio; it is not a requirement that all the flows contained in the Studio Package are imported simultaneously.
+Individual flows contained in the Studio Package may be individually selected for importing into {{% ctx %}} Studio; it is not a requirement that all the flows contained in the Studio Package are imported simultaneously.
 
-By default, the display favours the Group hierarchy of the destination CORTEX Studio, showing how the imported flows will map into the existing system hierarchy. If an imported flow already exists in the destination, the imported flow will map to the same Group in the CORTEX Studio hierarchy. If an imported flow does not exist in the destination, the existing CORTEX Studio hierarchy will be extended using the hierarchy contained the package for that flow.
+By default, the display favours the `system hierarchy` of the destination {{% ctx %}} Studio, showing how the imported flows will map into the existing system hierarchy. If an imported flow already exists in the destination, the imported flow will map to the same Group in the {{% ctx %}} Studio hierarchy. If an imported flow does not exist in the destination, the existing {{% ctx %}} Studio hierarchy will be extended using the hierarchy contained the package for that flow.
 
-Alternatively, it is possible to have the display favour the hierarchy contained in the Studio Package, displaying the hierarchy of the Studio Package. If a version of the flows already exists in the destination CORTEX Studio, it will be moved to the hierarchy contained in the Studio Package, extending the destination hierarchy if necessary. If a flow does not exist in the destination CORTEX Studio, the hierarchy of the Studio Package will be created in the destination when the flow is imported.
+Alternatively, it is possible to have the display favour the `package hierarchy`, displaying the hierarchy conmtained in the Studio Package. If a version of the flows already exists in the destination {{% ctx %}} Studio, it will be moved to the hierarchy contained in the Studio Package, extending the destination hierarchy if necessary. If a flow does not exist in the destination {{% ctx %}} Studio, the hierarchy of the Studio Package will be created in the destination when the flow is imported.
 
-The ‘Edit import hierarchy’, available for imports favouring the system hierarchy or favouring the package hierarchy, enables any individual imported flows to be assigned to any Group in the hierarchy of the destination CORTEX Studio. The display will show the entire existing hierarchy of the destination CORTEX Studio, extended by any necessary Groups from the Studio Package hierarchy where the imported flows do not already exist on the destination CORTEX Studio; it is not necessary for the administrator to have View or Edit authorisation for any flows to view the entire system Group hierarchy.
+The `Edit import hierarchy`, enables any individual imported flows to be assigned to any Group in the hierarchy of the destination {{% ctx %}} Studio. The display will show the entire existing hierarchy of the destination {{% ctx %}} Studio, extended by any necessary Groups from the Studio Package hierarchy where the imported flows do not already exist on the destination {{% ctx %}} Studio; it is not necessary for the administrator to have View or Edit authorisation for any flows to view the entire system Group hierarchy.
 
 When the selected flows from the Studio Package are imported, they will become the Master Version of the flows in the destination Master Repository, replacing any existing Master Versions.
 

content/static/2025.1/images/Studio Export.png

@@ -871,6 +871,8 @@
                                 SetDefaultVersion = "/docs/guides/user-guides/user-interfaces/gateway/admin/packages/package-version-editor/#set-as-default-version"
                                 Triggers = "/docs/guides/user-guides/user-interfaces/gateway/admin/packages/package-version-editor/#triggers"
                                 Unpublish = "/docs/guides/user-guides/user-interfaces/gateway/admin/packages/package-version-editor/#unpublish-a-package-version"
+                        [Cortex.Guides.UserGuides.UserInterfaces.Gateway.Admin.StudioImport]
+                            MainDoc = "/docs/guides/user-guides/user-interfaces/gateway/admin/studio-import/"
 
 [Cortex.Reference]
         MainDoc = "/docs/reference/"