Genpact Cora Knowledge Center

Support

Cumulative List of Breaking Changes

V9.x

Following is a list of all the breaking changes introduced with V9.x releases.

V9.1

  • Workflow lock duration: with this release, the default workflow execution lock duration is 10 minutes. If an application executes a workflow instance, another application cannot execute that instance until the first execution completes. 
    For example, a workflow that includes a Web Service Consumer that consumes a Web Service Listener in the same workflow will fail because the instance is locked for the consumer's execution first. In such a scenario, the recommendation is to add a Goto activity to connect between the two activities. 
    For more details, see this article .
  • New status update procedure for instance activities: If you use data from tblInstanceActivitiesClosed, note that the status values have been updated.
    For more details, see the description in the Enhancements section in this release notes.
  • Flowtime menu and submenu changes: In case you have customized your portal, note that the menu structure and Hot Operations configuration have been changed. Following these changes, you need to reapply any customized configuration to the Default.config and HotOperations.config files.

NOTE
TheSubmenuIdandSelectedSubMenuItemIdpage properties have been changed on all Hot Operations pages.

  • Team Leaders and Hot Operations Managers now need to have permissions on the solution's relevant workflows to perform actions in the Tasks List/Cases List pages.

V9.0

As a result of structural changes in Cora SeQuence, there is a list of changes that you need to consider when migrating from previous versions to V9.0.

  • There are no upgrade procedures. Existing implementations need to follow a migration path.
    For more details, see this article.  
  • USL and UWF tables have been consolidated.
    For more details, see the General enhancements section in the V9.0 release notes.
  • The fldID column is no longer incremental intblInstanceActivities. For sorting purposes, usefldCreationDate.
  • During workflow execution, activity execution data is stored in the application memory. Consider this if your implementation uses data directly from tblInstanceActivities during execution.
    For more details, see this article.
  • The Runtime.aspx page markup structure has been changed. 
  • The following items have been removed from the product:
    • Cora SeQuence 6 forms 
    • ProcessTOGO application
    • SharePoint Listener activity 
    • Sequence CRM Edition (SCE)
  • The Description field has been remove from Workflow Stage Set screen.

V8.x

Following is a list of all the breaking changes introduced with V8.x releases.

V8.8

  • Sharepoint: Cora SeQuence V8.8 does not support Flowtime hosted on Sharepoint. If your solution uses Sharepoint to host Flowtime, when upgrading, you need to set up a new server.
  • Microsoft SQL Server: If your system uses an earlier version than Microsoft SQL Server 2014 Enterprise Edition or Microsoft SQL Server 2016 SP1/Enterprise Edition, you will need to install a later version.
    For more details, see the Platform Support Matrix
  • Workflow persistence configuration:  If your solution uses tblInstanceActivities table through the database while workflow execution takes place, or it uses built-in commands, sampled data may not be accurate during execution. This event can break the implementation and data credibility. In such a case, you can override the workflow persistence configuration.
    For more details, see  this article.

V8.7

  • Cora SeQuence V8.7 does not support ASP.NET session state: If your code uses data from the ASP.NET session, you need to explicitly enable the ASP.NET session in the web.config file.
  • Flowtime theme
    • Previous built-in themes will be overwritten on upgrade. 
    • Themes "Default" and "SharePoint2010" were removed.
    • New designs and UX elements will not be updated in custom themes.
      To avoid breaking custom themes during upgrade the following actions are required: 
      1. Before the upgrade, back up all the Images folders under the custom theme folder. 
      2. After the upgrade, copy  all the Images folders under the default theme, Sequence8, into the custom theme.  
        • Make sure that you do not replace existing files. 
        • Alternatively, you can create your own images with the same names. 
      3. Apply new CSS styles and changes to the equivalent custom theme files.
        After upgrade the following CSS files, which contain the changes you need to apply, are located under <server name>\Program Files\PNMsoft\Shared Resources\Themes\Upgrade:
        • Flowtime.delta.css
        • Portal.delta.css
        • ProcessPortal.delta.css

          NOTE: Delta CSS files will not be supplied with the next versions.

  • Flowtime layout 
    • After upgrade, in sites that use the Sequence8 theme or a custom theme after upgrade, the name of the logged in user appears on the upper-right corner of the window, instead of the left panel, and the menu does not work properly.
      For details on how to fix this issue, see the Post-upgrade Flowtime configuration section below.

    • The Portal.Master layout, used in earlier versions is not supported by the Cora theme. Systems using this layout need to continue using the Sequence8 theme or a custom theme.
  • Sequence 6 forms
    • To run Sequence 6 forms in Flowtime V8.7, after upgrade: In the Flowtime Web.config file, remove, or comment out the line: <sessionState mode="Off" />, and configure it as follows: <sessionState mode="InProc" cookieless="false" timeout="601" />

V8.6

  • Some system default configs (Flowtime services configuration files) will be overwritten on upgrade. Any change to system configuration must take place on a copy of the file.
  • Flowtime – Default built-in themes will be overwritten on upgrade. New designs and UX elements will not get updated for customers who are using custom themes. In order not to break the customer themes during upgrade the following actions will be required:
    • Copy all new images from the default theme (called Sequence8) into the custom theme (or create your own images with the same names).
    • Apply new CSS styles and changes on the equivalent custom theme files.
      After the upgrade the following CSS files (which contain the changes you need to apply) will be located under c:\Program Files\PNMsoft\Shared Resources\Themes\Upgrade:
      • flowtime.delta.css
      • portal.delta.css
      • processportal.delta.css

To apply the changes open the correspondent files and add the content of the delta files to the end of each file

  • Email listener for attached files - We are now capturing attachment.DisplayName instead of attachment.FileName. If attachment.FileName is empty or not a file name FileName will be used.
  • Authorization Policy has been added to dashboard filter, when importing dashboards from a version prior 8.5, the dashboard must be opened in the designer and re-saved.
  • New Message or Task activities will only work with the new template option for sending emails. To create an activity with a template similar to the XSLT copy an old activity or add this to your template list.

V8.5

  • Email Templates: When you upgrade from Cora SeQuence v8.4, you need to change the token markup for the templates imported during the upgrade. Replace the colon ":" with an equal sign "=", to render the expression in HTML format.
    Before
    After
  • HotOperations: The GroupId and SolutionId properties were added to the architecture of all HotOperations components.
  • HotOperations Dashboards: We changed the HotOperations dashboard names and container names. In SharePoint you need to configure the Data Stream name and Layout Name for Ops Manager and Team Leader.

    ComponentData Stream NameLayout Name
    Operations Manager DashboardOpsManagerCasesDashboardOpsManagerCasesDashboard
    Operations Manager BoardOpsManagerCasesDashboardBoard
    Team Leader DashboardTeamLeaderDashboardTeamLeaderDashboard
    Team Leader BoardTeamLeaderDashboardBoard

NOTE: If you have a SharePoint deployment, before implementing these changes contact the Cora SeQuence Support Team

V8.4

V8.3

  • Message Editor: To prevent JavaScript injection from expressions used in a message body, the message body now goes through HTML encoding. This is the result for expressions that were created in versions earlier than 8.3, which return HTML to change their behavior when editing the message. To bypass this restriction, you can use one of the string expression directives detailed in String Expression Directives.
  • Cora SeQuence Instance Objects id was updated from int to big-int (long): This enables higher transaction volume in the Cora SeQuence engine. Cora SeQuence installation now supports up to 264 instances. The Workflow Instance, Activity Instance, and Action Items ID properties were modified in the database and the API to reflect the update. For more about issues and limitations, see Int to Long Issues.

Important: If you wrote custom code against the API, you need to update the code. If you wrote database code that uses the id field with direct assignment to int, you must update the database code.

  • Flowtime display language after upgrade: In previous versions, you could only select a display language for the entire Flowtime portal. In this version, when you select a display language, it applies to all Cora SeQuence components (Administration, Flowtime, ProcessTOGO). When you upgrade from a previous version, the language reverts back to the user's language.
  • Fixed message body: We removed the <br> tag from the message body.
  • Request/response persists for failed activity: When an Integration Activity fails to execute, the request or response persists (if generated).
  • SSRS analytics: Cora SeQuence no longer supports SSRS-based analytics.
  • Obfuscation method in SAP connection: We changed the obfuscation method in the SAP connection. You need to recreate existing SAP connections.
  • New mode for Attachment field: We added the Internal mode for Attachments. Use this mode when you need to access an attachment from a different workflow instance. The AttachmentInfo class has changed as a result.

V8.2

  • Runtime controls globalization key can be set in the web.config file. This will overwrite culture defined in the control itself. 
  • Sequence Administration, ProcessTO GO and BRS have been upgraded to .NET 4.6.2. 
  • Workflow Instance object has been synchronized from the Start workflow activity. 
  • Forms Authentication is set to False by default. 5. Methods were added to all Flowtime view interfaces. 6. The Request is persisted on failure in integration activity execution

V8.1

  • Sequence Flowtime portal has new layouts and Flowtime control has a new look and feel. To control the site and controls display use the Flowtime web.config. 
  • Sequence App studio has gone through major visual changes. Please note that there might be differences in the way your workflow diagram is displayed. 
  • The following services now run in .NET 4.5: BRS, ADSS and JES.