Skip to content

W-11585544: Update Studio version #178

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

Merged
fermujica merged 1 commit into from
Aug 16, 2022
Merged

W-11585544: Update Studio version #178

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: 1 addition & 1 deletion modules/ROOT/pages/dataweave-migrator.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -7,7 +7,7 @@ endif::[]

include::partial$eol-warning.adoc[]

If you have projects that are built with the deprecated xref:5@studio::datamapper-user-guide-and-reference.adoc[DataMapper], a migration tool is now included in Studio, which assists in converting a DataMapper map to DataWeave. This tool doesn't replace the original DataMapper in your flow, it creates a new equivalent DataWeave component next to it. The old DataMapper component is left in its place so that you can compare both as they sit next to each other on your flow, but you must then delete it for the flow to be executable.
If you have projects that are built with the deprecated xref:5.x@studio::datamapper-user-guide-and-reference.adoc[DataMapper], a migration tool is now included in Studio, which assists in converting a DataMapper map to DataWeave. This tool doesn't replace the original DataMapper in your flow, it creates a new equivalent DataWeave component next to it. The old DataMapper component is left in its place so that you can compare both as they sit next to each other on your flow, but you must then delete it for the flow to be executable.

== Using the Migrator Tool

Expand Down
8 changes: 4 additions & 4 deletions modules/ROOT/pages/dataweave-reference-documentation.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -305,7 +305,7 @@ Valid types are:

When defining an input of type CSV, there are a few optional parameters you can add to the input directive to customize how the data is parsed. These are not defined in the DataWeave script but on the Mule XML code, in the Transform Message XML element.

In Anypoint Studio there are two ways to achieve this. You can either manually add the attributes to the project's XML, or do it through the graphical interface, by selecting the element from the tree view in the input section and clicking the gear icon. See xref:5@studio::using-dataweave-in-studio.adoc#parsing-csv-inputs[Using DataWeave in Studio] for more details.
In Anypoint Studio there are two ways to achieve this. You can either manually add the attributes to the project's XML, or do it through the graphical interface, by selecting the element from the tree view in the input section and clicking the gear icon. See xref:5.x@studio::using-dataweave-in-studio.adoc#parsing-csv-inputs[Using DataWeave in Studio] for more details.

==== Output Directive

Expand Down Expand Up @@ -3477,7 +3477,7 @@ c: |2003-10-01T23:57:59Z| + |P1Y|

Your DataWeave code can call any function you define as a global xref:3.7@mule-runtime::mule-expression-language-mel.adoc[Mule Expression Language (MEL)] function, as long as it is correctly defined in the Mule Project where your Transform Message element sits.

Refer to xref:5@studio::using-dataweave-in-studio.adoc#calling-global-mel-functions-from-dataweave-code[Using DataWeave in Studio].
Refer to xref:5.x@studio::using-dataweave-in-studio.adoc#calling-global-mel-functions-from-dataweave-code[Using DataWeave in Studio].

== Object

Expand Down Expand Up @@ -4060,7 +4060,7 @@ books: payload.items.*item map
}
----

In Anypoint Studio, you can define several more values, like separators, quote characters and escape characters. See xref:5@studio::using-dataweave-in-studio.adoc#configuring-the-csv-reader[Using DataWeave in Studio].
In Anypoint Studio, you can define several more values, like separators, quote characters and escape characters. See xref:5.x@studio::using-dataweave-in-studio.adoc#configuring-the-csv-reader[Using DataWeave in Studio].

== Functions and Lambdas

Expand Down Expand Up @@ -4221,7 +4221,7 @@ You can reference any *Property* (System or Spring) that exists in the server wh

== See Also

* xref:5@studio::using-dataweave-in-studio.adoc[Using DataWeave in Studio]
* xref:5.x@studio::using-dataweave-in-studio.adoc[Using DataWeave in Studio]
* xref:dataweave-examples.adoc[DataWeave Examples]
* xref:dataweave-tutorial.adoc[DataWeave Tutorial]
* https://www.mulesoft.com/platform/studio[Anypoint Studio]
8 changes: 4 additions & 4 deletions modules/ROOT/pages/index.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -8,12 +8,12 @@ include::partial$eol-warning.adoc[]

[TIP]
====
DataWeave is a new feature of the 3.7 runtime that replaces the xref:5@studio::datamapper-user-guide-and-reference.adoc[DataMapper], which is a major component in previous versions. We recommend you use DataWeave to avoid the future obsolescence of Datamapper.
DataWeave is a new feature of the 3.7 runtime that replaces the xref:5.x@studio::datamapper-user-guide-and-reference.adoc[DataMapper], which is a major component in previous versions. We recommend you use DataWeave to avoid the future obsolescence of Datamapper.
====

The xref:dataweave-reference-documentation.adoc[DataWeave language] is a simple, powerful tool to query and transform data inside of Mule. It can be used in two different ways:

* you can graphically map fields by dragging and dropping them, as could be done with the deprecated xref:5@studio::datamapper-user-guide-and-reference.adoc[DataMapper]
* you can graphically map fields by dragging and dropping them, as could be done with the deprecated xref:5.x@studio::datamapper-user-guide-and-reference.adoc[DataMapper]
* or you can leverage its powerful JSON-like language that's purposely built to make writing transformations as fast as possible and highly maintainable over the long term.
It supports a variety of transformations, from simple one-to-one mappings, to more elaborate mappings including normalization, grouping, joins, partitioning, pivoting and filtering.

Expand All @@ -24,13 +24,13 @@ The DataWeave language (which is similar to JSON) is used to describe the cannon

[TIP]
====
If you have projects that are built with the deprecated xref:5@studio::datamapper-user-guide-and-reference.adoc[DataMapper], a migration tool is now included in Studio, which assists in converting a DataMapper map to DataWeave: Right click on a DataMapper, select *Migrate to DataWeave*, and follow the instructions.
If you have projects that are built with the deprecated xref:5.x@studio::datamapper-user-guide-and-reference.adoc[DataMapper], a migration tool is now included in Studio, which assists in converting a DataMapper map to DataWeave: Right click on a DataMapper, select *Migrate to DataWeave*, and follow the instructions.

image::dw-migrator-script.png[dw migrator]
====


* xref:5@studio::using-dataweave-in-studio.adoc[Using DataWeave in Studio]
* xref:5.x@studio::using-dataweave-in-studio.adoc[Using DataWeave in Studio]
* xref:dataweave-reference-documentation.adoc[DataWeave Reference Documentation]
* xref:dataweave-tutorial.adoc[DataWeave Tutorial]
* xref:dataweave-examples.adoc[DataWeave Examples]
Expand Down
⚡