Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

W-17453211-Remove-page-aliases-from-v7-20-CP #587

Draft
wants to merge 1 commit into
base: v7.20
Choose a base branch
from
Draft

W-17453211-Remove-page-aliases-from-v7-20-CP #587

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 0 additions & 2 deletions modules/ROOT/pages/add-another-output-transform-studio-task.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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:
Expand Down
3 changes: 0 additions & 3 deletions modules/ROOT/pages/change-target-output-transformation-studio-task.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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"].
Expand Down
3 changes: 0 additions & 3 deletions modules/ROOT/pages/graphically-construct-mapping-studio-task.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down
1 change: 0 additions & 1 deletion modules/ROOT/pages/index.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.
Expand Down
2 changes: 0 additions & 2 deletions modules/ROOT/pages/move-transformations-separate-file-studio-task.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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:
Expand Down
2 changes: 0 additions & 2 deletions modules/ROOT/pages/preview-transformation-output-studio-task.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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*.
Expand Down
1 change: 0 additions & 1 deletion modules/ROOT/pages/proxy-settings-task.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.

Expand Down
2 changes: 0 additions & 2 deletions modules/ROOT/pages/studio-update-sites.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.
Expand Down
2 changes: 0 additions & 2 deletions modules/ROOT/pages/to-download-and-install-studio-lx.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.
Expand Down
1 change: 0 additions & 1 deletion modules/ROOT/pages/to-download-and-install-studio-wx.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.
Expand Down