---
schema_version: "1"
id: 57b30e08ffefa7dc98dc867f9a3cf2a7548e0a2d24f766adf12476524fc6b720
title: Migrating the Scripting Component
collection: mulesoft
version: current
locale: en-us
portal_url: https://docs.salesforce.com/mulesoft/current/en-us/mule-runtime/4.3/migration-module-scripting.md
canonical_url: https://docs.mulesoft.com/mule-runtime/4.3/migration-module-scripting
source_site: docs.mulesoft.com
content_type: documentation
content_hash: 580d76d45ee493f24adee18069e46acb2c06974a00cba4cf0dcabbb081d26519
description: MuleSoft Documentation Site
release: "4.3"
latest: false
---
---
product: Mule Runtime
version: 4.3
---

# Migrating the Scripting Component

> For the full documentation index, see: https://docs.mulesoft.com/llms.txt

The `<scripting>` component in Mule 3 is replaced with a new `<scripting>` module. This new module
is pretty similar in functionality, with just some syntax changes:

Mule 3 Example: Scripting

```xml
 <flow name="greedy">
    <choice>
        <when expression="#[flowVars['currency'] == 'USD']">
            <scripting:component>
                <scripting:script file="greedy.groovy">
                    <property key="currency" value="USD"/>
                </scripting:script>
            </scripting:component>
            </when>
        <when expression="#[flowVars['currency'] == 'GBP']">
            <scripting:component>
                <scripting:script file="greedy.py">
                    <property key="currency" value="GBP"/>
                </scripting:script>
            </scripting:component>
            </when>
    </choice>
</flow>
```

-

Mule 4 Example: Scripting

```xml
 <flow name="greedy">
    <scripting:execute engine="groovy">
        <scripting:code>${file::greedy.groovy}</scripting:code>
        <scripting:parameters>
            #[{currency: vars.currency}]
        </scripting:parameters>
    </scripting:execute>
</flow>
```

As you can see, the main difference here is that now you can use DataWeave to generate the input
parameters.

## Accessing Variables from the Script

The previous example uses a variable to show how to pass parameters into the script, it’s best to
keep the script decoupled from the rest of the flow, so that changes to the Mule applications don’t
require changes to the script.

However, you can still access the variables from the script using the `vars` keyword. For example:

Mule 4 Example: Accessing variables directly

```xml
<flow name="greedy">
    <scripting:execute engine="groovy">
        <scripting:code>return "currency is " + vars.currency</scripting:code>
    </scripting:execute>
</flow>
```

To use the Scripting Module, simply add it to your application using the Studio palette or add the
following dependency in your `pom.xml` file:

```xml
<dependency>
  <groupId>org.mule.modules</groupId>
  <artifactId>mule-scripting-module</artifactId>
  <version>1.1.0</version> <!-- or newer -->
  <classifier>mule-plugin</classifier>
</dependency>
```

## See Also

- [Scripting Module Documentation](https://docs.mulesoft.com/scripting-module/latest/)