From 1b60c4670a44b908a16fbdb17a90d02b6aa46827 Mon Sep 17 00:00:00 2001 From: Crispy-Salesforce Date: Mon, 13 Jan 2025 18:21:58 -0300 Subject: [PATCH] W-17453211-Remove-page-aliases-from-v7-20-CP --- .../ROOT/pages/add-another-output-transform-studio-task.adoc | 2 -- .../pages/change-target-output-transformation-studio-task.adoc | 3 --- .../ROOT/pages/graphically-construct-mapping-studio-task.adoc | 3 --- modules/ROOT/pages/index.adoc | 1 - .../pages/move-transformations-separate-file-studio-task.adoc | 2 -- .../ROOT/pages/preview-transformation-output-studio-task.adoc | 2 -- modules/ROOT/pages/proxy-settings-task.adoc | 1 - modules/ROOT/pages/studio-update-sites.adoc | 2 -- modules/ROOT/pages/to-download-and-install-studio-lx.adoc | 2 -- modules/ROOT/pages/to-download-and-install-studio-wx.adoc | 1 - 10 files changed, 19 deletions(-) diff --git a/modules/ROOT/pages/add-another-output-transform-studio-task.adoc b/modules/ROOT/pages/add-another-output-transform-studio-task.adoc index a56e2089..6a987bab 100644 --- a/modules/ROOT/pages/add-another-output-transform-studio-task.adoc +++ b/modules/ROOT/pages/add-another-output-transform-studio-task.adoc @@ -3,8 +3,6 @@ ifndef::env-site,env-github[] include::_attributes.adoc[] endif::[] -:page-aliases: 6.5.x@studio::add-another-output-transform-studio-task.adoc - A single Transform Message component can shape different output parts, such as the payload, a flow variable, or a property. You must define each output part in a separate DataWeave code, written out in a separate tab of the Transform pane. For example: if one tab defines the payload, and another an outbound property, both are parts of the same output Mule message. To add a new output: diff --git a/modules/ROOT/pages/change-target-output-transformation-studio-task.adoc b/modules/ROOT/pages/change-target-output-transformation-studio-task.adoc index f296c6c6..5f52fb21 100644 --- a/modules/ROOT/pages/change-target-output-transformation-studio-task.adoc +++ b/modules/ROOT/pages/change-target-output-transformation-studio-task.adoc @@ -3,9 +3,6 @@ ifndef::env-site,env-github[] include::_attributes.adoc[] endif::[] -:page-aliases: 6.5.x@studio::change-target-output-transformation-studio-task.adoc - - By default, the Transform Message component outputs to the message payload. You can change this target, so that the result of your transformation populates another part of the output such as a property or variable. . Click the *Edit Current Target* button image:using-dataweave-in-studio-47984.png["Edit icon"]. diff --git a/modules/ROOT/pages/graphically-construct-mapping-studio-task.adoc b/modules/ROOT/pages/graphically-construct-mapping-studio-task.adoc index cb80ae40..458a7658 100644 --- a/modules/ROOT/pages/graphically-construct-mapping-studio-task.adoc +++ b/modules/ROOT/pages/graphically-construct-mapping-studio-task.adoc @@ -3,9 +3,6 @@ ifndef::env-site,env-github[] include::_attributes.adoc[] endif::[] -:page-aliases: 6.5.x@studio::graphically-construct-mapping-studio-task.adoc - - Through the graphical UI of the Transform Message component you can do the tasks below. When doing each, the necessary lines are added to the DataWeave code to describe the action. == Map a Field diff --git a/modules/ROOT/pages/index.adoc b/modules/ROOT/pages/index.adoc index e5929d42..ac13e33e 100644 --- a/modules/ROOT/pages/index.adoc +++ b/modules/ROOT/pages/index.adoc @@ -2,7 +2,6 @@ ifndef::env-site,env-github[] include::_attributes.adoc[] endif::[] -:page-aliases: add-view-to-perspective.adoc :keywords: studio, IDE, development, eclipse, anypoint, visual editor, XML editor Anypoint Studio is MuleSoft's Eclipse-based integration development environment for designing and testing Mule applications. diff --git a/modules/ROOT/pages/move-transformations-separate-file-studio-task.adoc b/modules/ROOT/pages/move-transformations-separate-file-studio-task.adoc index 3ac637bb..b32794bb 100644 --- a/modules/ROOT/pages/move-transformations-separate-file-studio-task.adoc +++ b/modules/ROOT/pages/move-transformations-separate-file-studio-task.adoc @@ -3,8 +3,6 @@ ifndef::env-site,env-github[] include::_attributes.adoc[] endif::[] -:page-aliases: 6.5.x@studio::move-transformations-separate-file-studio-task.adoc - By default, the DataWeave code from a Transform Message component is expressed inline within your Mule XML file. You can instead keep each in a separate file ( `.dwl` ) and have your XML reference them. These files are packaged with your Mule application when built. To export the DataWeave code to a `.dwl` file: diff --git a/modules/ROOT/pages/preview-transformation-output-studio-task.adoc b/modules/ROOT/pages/preview-transformation-output-studio-task.adoc index a7f8c467..f56e836e 100644 --- a/modules/ROOT/pages/preview-transformation-output-studio-task.adoc +++ b/modules/ROOT/pages/preview-transformation-output-studio-task.adoc @@ -3,8 +3,6 @@ ifndef::env-site,env-github[] include::_attributes.adoc[] endif::[] -:page-aliases: 6.5.x@studio::preview-transformation-output-studio-task.adoc - You can provide sample input data to your Transform Message component to see how the transformation affects it. You don't need to deploy your project to use this feature. A sample output is updated in real time as you make changes both to the sample input and the transformation. . Click on the root of the input pane and select *Edit Sample Data*. diff --git a/modules/ROOT/pages/proxy-settings-task.adoc b/modules/ROOT/pages/proxy-settings-task.adoc index 6975c07c..3ab06d45 100644 --- a/modules/ROOT/pages/proxy-settings-task.adoc +++ b/modules/ROOT/pages/proxy-settings-task.adoc @@ -2,7 +2,6 @@ ifndef::env-site,env-github[] include::_attributes.adoc[] endif::[] -:page-aliases: proxy-settings-reference.adoc Anypoint Studio allows you to configure proxy configurations for when your computer is behind a proxy server and needs to connect to the internet to download plugins and install updates. diff --git a/modules/ROOT/pages/studio-update-sites.adoc b/modules/ROOT/pages/studio-update-sites.adoc index c1606fcd..43b38be0 100644 --- a/modules/ROOT/pages/studio-update-sites.adoc +++ b/modules/ROOT/pages/studio-update-sites.adoc @@ -3,8 +3,6 @@ ifndef::env-site,env-github[] include::_attributes.adoc[] endif::[] -:page-aliases: 6.5.x@studio::studio-update-sites.adoc - :keywords: mule, esb, studio, anypoint studio, update sites, updates, extensions, plug-ins, plugins, download Anypoint Studio uses update sites to update both itself and embedded versions of Mule runtime engine and MUnit. diff --git a/modules/ROOT/pages/to-download-and-install-studio-lx.adoc b/modules/ROOT/pages/to-download-and-install-studio-lx.adoc index 4e043fee..5d9dde3b 100644 --- a/modules/ROOT/pages/to-download-and-install-studio-lx.adoc +++ b/modules/ROOT/pages/to-download-and-install-studio-lx.adoc @@ -3,8 +3,6 @@ ifndef::env-site,env-github[] include::_attributes.adoc[] endif::[] -:page-aliases: 6.5.x@studio::to-download-and-install-studio-lx.adoc - == Prerequisites * To support the Studio Theme in Linux, have GTK version 3 installed. diff --git a/modules/ROOT/pages/to-download-and-install-studio-wx.adoc b/modules/ROOT/pages/to-download-and-install-studio-wx.adoc index dc605fac..c2906ab7 100644 --- a/modules/ROOT/pages/to-download-and-install-studio-wx.adoc +++ b/modules/ROOT/pages/to-download-and-install-studio-wx.adoc @@ -2,7 +2,6 @@ ifndef::env-site,env-github[] include::_attributes.adoc[] endif::[] -:page-aliases: jdk-requirement-lnx-workflow.adoc, jdk-requirement-wx-workflow.adoc, jdk-requirement-xos-workflow.adoc, studio-configure-vm-task-lnx.adoc, studio-configure-vm-task-unx.adoc, studio-configure-vm-task-wx.adoc, faq-jdk-requirement.adoc . Download the Anypoint Studio installation file from the https://www.mulesoft.com/lp/dl/studio[Download Site]. . Extract the Windows installation file into the `C:\` root folder.