K2 Core

• Legacy databases: In order to upgrade to K2 4.7 you require a single database. If you have not yet consolidated your databases, you need to consolidate the databases prior to upgrading to 4.7. For more information, see KB001628 (http://help.k2.com/KB001628).
• K2 Management Site: For the new K2 Management Site to run you must have the K2 smartforms runtime site installed. Run the SmartForms installer after the blackpearl installation if you require the runtime site.
• License Audit Report: When Upgrading and opening the License Audit Report for the first time, all users will by default display with the last log in date as the date of the upgrade as this is the starting point after which it will update as users log in.
• API: If you currently have made use of custom OAuthExtensions with logic in the Init method on the IHostableType interface in any K2 solutions, from K2 4.6.11 these solutions will no longer function as expected as the IHostableType has been removed. To fix the solutions you will need to change the related code and then recompile.
• Unattended Installer: In order to implement new features, merge installers and resolve bugs new variables have been added to the installer. Any unattended files must be regenerated in this release to ensure that the full set of features and functionality gets installed.
• .NET Framework: .NET Framework 4.6.1 is required from K2 4.7. If you have upgraded to .NET Framework 4.6 ensure that you read KB001712 (http://help.k2.com/kb001712) and downloaded the available update.
• K2 for SharePoint 2013 requires as a minimum the SharePoint 2013 July 2016 Cumulative Update (CU).
• When deploying a package that contained a large number of artifacts it would take a long time for the analysis to finish after each change if the Automatically re-analyze after each change checkbox was selected. By default this checkbox was selected when deploying a package. The default behavior has been changed and the Automatically re-analyze after each change checkbox is not selected when deploying a package. A blue Analysis Required icon will appear after changes are made in the deploy package, after which the Analyze button can be clicked. This allows you to make multiple changes in the package and then run the Analysis on the pakage once rather than after each change.
• Workflow “Admin” rights have changed. You no longer need K2 Workflow Server “Admin” rights on the K2 environment to be able to manage workflow definitions and process instances. Users with Workflow Admin rights can now manage processes that they have “Admin” rights to, without needing K2 Workflow Server “Admin” rights as well.
• The Workflow Management API behavior has changed. Methods that return lists were updated to return only the data that the currently-connected user has rights for. If the user does not have any rights, an exception is no longer thrown, but instead an empty list is returned. If you have code that relies on an exception to be thrown on these management methods, you will need to change your code accordingly to cater for the change in behavior.
• The SmartBox data column length for encrypted data has changed from NVARCHAR(200) to NVARCHAR(MAX).
• If you have built solutions or UI components for the SQLUM database take note of the following change that might impact your environment after upgrading to 4.7. When using a secure security key (AES_256), the resulting cipher data is bigger than the previous key and will required the password column in the CustomUM (SQL UM Provider) to be extended to store the new encrypted data.

K2 for SharePoint

• K2 for SharePoint App: The K2 for SharePoint App no longer supports individual subsite control, from K2 4.7 the app is deployed per site collection and will be available on all subsites in the collection. For more information see KB001738.
• K2 for SharePoint App: All users that use K2 in SharePoint (including list integration, creating, editing and deleting list items), require Read rights on the App Catalog.
• K2 for SharePoint App: If you had integrated K2 with a SharePoint on-prem environment, and then integrated with SharePoint Online, you might not have an app catalog on your tenancy because the K2 app was available from the SharePoint Store. In K2 4.7 there are changes to the way in which the K2 app is registered and activated. You must create an app catalog site on the tenant (if one does not already exist) and add K2 for SharePoint to the app catalog site, where you then use the Registration Wizard to register the app with a K2 server. From that point forward, you must deploy and activate the app to site collections serviced by the app catalog using links on the Administration page.
• Installer: The K2 for SharePoint installer has been merged into the blackpearl installer. Run the blackpearl, SmartForms installers and the Appdeployment.exe to install K2 in a SharePoint 2013 environment.
• Microsoft is renaming "apps for SharePoint" to "SharePoint Add-ins” (for more information on this change implemented by Microsoft, please refer to  https://msdn.microsoft.com/en-us/library/office/fp161507.aspx and http://www.jeremythake.com/2015/06/office-365-app-model-rename-cheat-sheet/ ). K2 product documentation and some UI components of K2 may still use the term "App" as opposed to “Add-in”. Over time, K2 may be updating products, documentation, samples, and other resources to reflect the SharePoint platform name change from “App” to “Add-In”, but you can assume that the terms “App” and “Add-In” are synonymous.

• Installer: The K2 smartforms server component install has been combined with the K2 blackpearl server component in the blackpearl installer. The SmartForms Setup Manager will install the Runtime and Design time sites as well as the SmartForms process wizards.
• Unattended Installer: In order to implement new features, merged installers and resolve bugs new variables have been added to the installer. Any unattended files must be regenerated in this release to ensure that the full set of features and functionality gets installed.
• Control Pack: The K2 smartforms Control Pack has been merged into SmartForms, this means that there is nolonger a separate Control Packer installer.
• List View: Previously, you could select text in the List View with your mouse and copy the selected text. A change has been made to the copy and paste functionality that allows you to select a row or multiselect rows in a List View and then use CTRL+C to copy the rows, CTRL+V to paste. See keyboard shortcuts in the List View product documentation for more details.
• Additional file types have been added by default to the Global Blacklist setting in the web.config file. This could result in certain files that your solutions previously allowed to be uploaded to be blocked. For more details on the Global blacklist see the File Attachment Control topic.
• Custom Themes: K2 recommends that you actively maintain your custom themes by checking that they still render as expected after an upgrade. In order to implement new features, resolve bugs and improve performance, changes are made to the rendered HTML and accompanying CSS. As a result, custom themes will need to be adjusted to retain their existing appearance and behavior. In most cases, custom themes are copies of the core themes provided with SmartForms, with alterations to match the user’s requirements. It is recommended that the custom theme be compared with the theme on which it has been based using a tool such as Beyond Compare. From the comparison, structural changes will be evident and the required changes can then be made to the custom theme.
  The following changes were made in SmartForms 4.6.9 and up that need to be considered in order to ‘upgrade’ a purpose built custom theme:
              o Icons are no longer globally available, instead it is required that one specify the icons within the custom theme itself. This improves performance when a theme uses custom icons. Use the Platinum theme as an example.
              o The application of borders has changed on the following controls:
                      - Lookup Control
                      - Picker Control
                      - Date & Time Picker
                      - Dropdown List
              o The following controls have new stacked rendering implementations which can affect a custom theme:
                      - Radio button List
                      - Checkbox List
                      - Choice Control
• Reporting Controls: Currently the On Change event in the rules would not execute when any of the reporting controls changed, but would rather execute when the controls were populated. The On Change event has been fixed in K2 4.6.11 to only execute when a selection is made. This would change the expected behavior that users are accustomed to and might require the Form rules to be adjusted accordingly.
• System Objects: With the release of the new K2 Management Site the OAuth and Claims System Forms and Views in the K2 Designer are now hidden, this means that if you want to add or update an OAuth resource, for example, you will no longer find the Form in the System node in SmartForms. Browse to Start> All Programs>K2 blackpearl> K2 Management to open the site which contains the functions previously visible in the system Folder.
• Changes applied to the Category naming structure – The category naming structure has been changed and will not allow a category name to include a backslash, for example, DepartmentHR. After upgrading to 4.7 all existing names containing backslashes will be updated and the backslash will be replaced with an underscore, making our example’s new name Department_HR. If for any reason after the upgrade the underscore results in a duplicate name the new category name will be incremented with an integer at the end, for example, Department_HR1. Note that a forward slash is still allowed in the category name.

• The Language Pack only applies to K2 smartforms and K2 View Flow.
• Runtime exception messages originating from the K2 blackpearl Server will still be displayed in English.
• Localization support for the Design time is limited and areas of the Design time experience will still display in English after the K2 Language Pack has been installed.
• If a multi-language Form is required, the Form and the Form Views must be designed in one language then copied and modified for each of the other languages you wish to support. Direct the user to the Form in the user’s language choice. During installation of the K2 Language Pack, select all the required languages to ensure that the required resource files are installed for the languages you wish to support.