Migration notes for Silverstone M1

This page summarizes key changes from the previous milestone.

Global Context API updates

Metadata enhancement for extension activities in Assemble flow

More details about this enhancement could be found here

This enhancement provide good backward compatibility. For the most cases, the implementation of extension activities or the existing flow won't be impacted. And you can continue use the old format for the metadata creation.

In the flow definition, if the name of Activity input is missing, that input will be treated as same as the input defined in the first activity. E.g. The following two flow snippets are equality.

    <sendMail name="sendMail_0" 
              address="${inputForm_0.client[0]}" 
              subject="The proposal of your request.">
        <input value="Here's the final proposal." />
    </sendMail>

    <sendMail name="sendMail_0" 
              address="${inputForm_0.client[0]}" 
              subject="The proposal of your request.">
        <input name="body" value="Here's the final proposal." />
    </sendMail>

The following built-in activities will be updated

• <sendMail> : If you want to send the attachment in the email, you need specify the input with name "attachement"
• <XSLT> : If you want to specify the variables used in the XSLT transformation context, you need to specify the input with name "variables "

Deprecated Security Functions

There have been some features of WebSphere sMash's security model that have been superseded by new function. While migration from the deprecated methods is not required for M1, it is strongly suggested to ensure your application is compatible with future versions of the sMash runtime. Complete information on the deprecated functions can be found here