To enhance the stability of Marketo’s email assembly infrastructure, we are disabling some Velocity Script functionality on June 14, 2019.
What change is being made?
The following Velocity Tools will permanently be disabled for use in email script, on June 14, 2019.
My Tokens:
- classTool
- contextTool
- resourceTool
Some common use examples of these tools include:
- $class.
- getClass()
- $context.
When are these changes taking effect?
These changes will take effect in the June 2019 Release on June 14, 2019.
How did it work before?
The way Velocity Tools are used in your email scripts is highly dependent on the structure of your code and varies on a case-by-case basis. To identify how you are currently utilizing Velocity Tools in your email design, please consult directly with your developer. Documentation on each tool can be found on Apache’s website at the links below:
classTool : https://velocity.apache.org/tools/devel/apidocs/org/apache/velocity/tools/generic/ClassTool.html
contextTool: https://velocity.apache.org/tools/devel/apidocs/org/apache/velocity/tools/generic/ContextTool.html
resourceTool: https://velocity.apache.org/tools/devel/apidocs/org/apache/velocity/tools/generic/ResourceTool.html
Why is this changing?
We regularly review our infrastructure to ensure it meets the highest standards for stability and security. During a recent review, we identified that a small subset of Velocity Tools could potentially impact the health of our message assembly servers, and as a result, we made the decision to disable these permanently.
What do I need to do?
If you are currently using Velocity Tools in your email scripting, you will need to review and update your script to use alternate methods before June 14, 2019. Documentation on supported Velocity Scripting can be found on our Developers’ site at http://developers.marketo.com/email-scripting/. Any email script tokens still referencing Velocity Tools after the June 14, 2019 deadline could fail to compile, resulting in emails not rendering as expected or complete send failure.
We have identified impacted customers using these Velocity Tools and will alert them individually via Marketo Notifications.
Considering the customized nature of Velocity Scripting, Marketo Support is not able to assist with the authoring or troubleshooting of custom code. Please reach out to your developer for assistance. If you no longer have access to a technical resource, you may also contact your CSM to coordinate a scoping call with our Professional Services team.
.png)