Compatibility Issues with Workflow
There are some specific compatibility issues that have been encountered in Workflow. These compatibility issues are necessary due to certain functionality changes that were made to improve the product.
- Compatibility Issues with Workflow 2.6
- The same compatibility issues for Workflow 2.5 apply to Workflow 2.6.
- Compatibility Issues with Workflow 2.5
- Compatibility Issues with Workflow 2.2
Compatibility Issues with Workflow 2.5
Customer Service Providers
Obsolete | Replacement |
---|---|
ModelObject.TableName | FullyQualifiedTableName |
Obsolete | Replacement |
---|---|
GetTableName() | GetFullyQualifiedTableName() |
GetTableNames() | GetFullyQualifiedTableNames() |
TableName | FullyQualifiedTableName |
HistoryTableName | HistoryFullyQualifiedTableName |
Legacy Certificates
Starting with Workflow 2.5, legacy certificates are no longer supported.
Compatibility Issues with Workflow 2.2
Silverlight 5
You must upgrade from Silverlight Runtime v4.0 to Silverlight Runtime v5.0, as well as from Silverlight SDK v4.1 to Silverlight SDK v5.0. All forms will automatically be updated.
Custom Application Logging
Custom applications that directly reference Log4Net for logging purposes may stop working with Workflow version 2.2, which installs an updated version of Log4Net. To prevent such compatibility problems going forward, we recommend that custom applications instead be designed to log messages through the ILog interface in Proficy.Platform.Core.Diagnostics. If this is not feasible, you must ensure that custom applications reference version 1.2.11 of Log4Net, and be prepared to update the version of Log4Net referenced by custom applications upon upgrade to future releases of Workflow.