Some standard components of the catalog are no longer available on this version, and others are now deprecated. This version also provides new components, which can cause conflicts when migrating old code.
You have to adapt your code if your project depends on components which have been removed on this version of ALBPM. Refer to Removed and Deprecated Components to see which components have been removed or deprecated on each version of ALBPM.
Standard components which are new to this version can cause naming conflicts with existing custom components in your project.
For example, a new component named MailSender has been added to the Fuego.Net module. If your project defines a BPM Object type also named MailSender, existing code referring to MailSender now becomes ambiguous.
To resolve this conflict, you should use the fully qualified names of those components:
sender = MailSender() // ambiguous sender = YourModule.MailSender() // explicitly refer to custom BPM Object sender = Fuego.Net.MailSender() // explicitly refer to standard component