K2 blackpoint Release Notes

Transcription

1 K2 blackpoint Release Notes VERSION February 26 PAGE 1

2 INTRODUCTION This document provides information on the installation and known issues for K2 blackpoint 0902 ( ). CONTENTS INTRODUCTION... 2 CONTENTS... 2 INSTALLATION... 3 > Installation Steps... 3 > Confirm K2 blackpoint 0902 ( ) Installation... 4 > Post installation configuration... 5 > Beta 2 Migration... 5 IMPORTANT CONSIDERATION... 5 KNOWN ISSUES... 6 PAGE 2

3 INSTALLATION K2 blackpoint 0902 ( ) is available as an independent self extracting installation package. For new clients K2 blackpoint is installed on clean machines. For Beta 2 clients it is recommended to remove any previous versions of K2 blackpoint before installing K2 blackpoint 0902 ( ). K2 blackpoint Beta 2 clients can migrate the K2 databases and K2 processes from K2 blackpoint Beta 2 to K2 blackpoint 0902 ( ) if required. Please review the Beta 2 Migration section to understand the steps for uninstalling Beta 2 and recommendations for migration. Note: There is no upgrade of K2 blackpoint to K2 blackpearl available in this release. The upgrade options will be available in a future release. INSTALLATION STEPS Save the compressed archive to all machines where K2 blackpoint 0902 ( ) is to be installed. Click on the WinRAR self - extracting archive and select a destination folder to extract the installation files to and click Install. Click on the K2 Setup link in the K2 blackpoint splash screen to initiate the installation process. Alternatively, when installing from a network (UNC) share (\\server\...\), or even a mapped network drive, the K2 blackpoint installer will copy all necessary files and folders to a temp folder on the local drive and then restart itself from the local temp folder. This ensures that the installer executes correctly. The screen below shows when the files are being copied: [FIGURE 1. PREPARING FILES FOR K2 BLACKPOINT INSTALLATION] If installing K2 blackpoint from a network location set the permissions to execute a.net application over a network manually by running the following command using the CasPol utility: %WINDIR%\Microsoft.NET\Framework\v \CasPol.exe" -q -machine -addgroup 1. - zone Intranet FullTrust The K2 blackpoint Setup Manager will step through the installation process. There is also a video available to watch to help you install K2 blackpoint, available from the splash screen by clicking on the link in Step 2. Full PAGE 3

4 installation details are provided in the product documentation available by clicking on the link in Step 2. Please contact support if any errors are detected during installation or configuration. [FIGURE 2. K2 BLACKPOINT SETUP MANAGER WELCOME SCREEN] Note: Please refer to the K2 blackpoint Getting Started Guide for detailed installation information. CONFIRM K2 BLACKPOINT 0902 ( ) INSTALLATION To ensure that K2 blackpoint 0902 ( ) has installed correctly, follow these steps: 1. Open Add/Remove Programs 2. The installed K2 components and the relevant version number will be displayed: PAGE 4

5 [FIGURE 2. ADD OR REMOVE PROGRAMS WITH THE UPDATE DISPLAYED] POST INSTALLATION CONFIGURATION Follow the steps outlined in the Getting Started Steps after installation or click on the K2 Studio link on the K2 blackpoint splash screen for step by step instructions. BETA 2 MIGRATION Existing K2 blackpoint Beta 2 clients have the option to migrate from Beta 2 to K2 blackpoint 0902 ( ) when installing K2 blackpoint 0902 ( ). The various installation options are discussed in the K2 blackpoint 0902 Migration document. IMPORTANT CONSIDERATION 1. The default behavior of the Destination Rule in the K2 designers differs as follows: In the Process Helper the default behavior of the destination rule is All at once. When manually dragging events and activities onto the K2 Studio design canvas the default behavior of the destination rule is Plan just once. The K2 Web Designer for SharePoint s default behavior of the destination rule is All at once. 2. In a distributed install the MOSS AppPool account must be assigned db_owner rights on the K2 Web Designer database. PAGE 5

6 KNOWN ISSUES 1. The K2 Report Web Part cannot be configured on any site except on K2 Process Portals. 2. Solution deployment and feature activation inconsistently fails on various installs. 3. K2 Workflows do not continue if a user task is assigned to a SharePoint group. 4. SharePoint SmartObjects do not support multiple lookup fields. 5. A WFI runtime error occurs when K2 Server is not a site collection administrator. Error message states "Value does not fall within the expected range." 6. When deploying a process that has been exported from the K2 Web Designer an error occurs. Save the process and then deploy it. 7. There is a potential issue when working with a K2 Web Designer process that has a merge rule. If you delete an activity depending on the merge rule, the dependency is lost and your process will no longer be able to compile. The only available workaround at this time is to recreate the desired process in K2 Web Designer or to not delete Activities that depend on merge rules. 8. Working Hours in Management Console does not cater for daylight saving. 9. When a K2 Worklist web part is added to a site that is required to be checked out before it can be edited, such as a Collaboration Site and the user sets his/her Out of Office from the worklist an error will be displayed as shown below: Click on Site Actions >Site Settings> Modify Pages Library Settings> Versioning Settings. Select the No option under Require Check Out and click OK as shown below: Note: In SharePoint Contribute rights are required to change the check out requirements on a site. PAGE 6

7 10. Occasionally when K2 blackpoint creates the workflow task in SharePoint a noticeable delay occurs before the tasks appear on the SharePoint Workflow Status page and can take up to a few minutes to create all the task items. The only available workaround at this time is to regularly refresh the page. 11. When a K2 workflow is terminated in the K2 Management Console the workflow is not terminated in SharePoint. The workaround at this time is to open SharePoint and manually terminate the workflow in SharePoint. 12. It is not recommended and is unsupported to open a K2 blackpearl project in the K2 blackpoint K2 Studio Designer. 13. If a K2 project making use of a reference event containing references to an absolute path is moved to a different location on the same machine or to a different machine the process will not deploy as it cannot locate the reference and the following error will be displayed: PAGE 7

8 > Open the Project in K2 Studio. > Click on the References icon on the Home tab. > The reference in question will display in the Reference list. > Select the reference in the list and click the Remove button. Click Yes to the warning message. > Now re-add the reference by clicking the Add button, browsing to the location of the reference and click OK. > Deploy the K2 process. 14. Certain special characters are not supported when used in a SharePoint List or Column name and will cause problems when trying to create SmartObjects. The unsupported characters are: >, ; ~ $ cannot be used in a List or Column name > The apostrophe cannot be used in a list name 15. It has occurred that the K2 Server has stopped and the following error message displayed: Unable to connect to SHAREPOINT on port No connection could be made because the target machine actively refused it. PAGE 8

9 The following steps will resolve this error as well as the issue with web part timeouts in the K2 Process Portal. The error is caused by the Max Pool Size configuration setting being too small. Increase the Max Pool Size by following these steps: > Browse to the installation directory of the K2 blackpoint Server (e.g. C:\Program Files\K2 blackpoint\host Server\Bin) > Locate the following file: SourceCode.Workflow.Runtime.Management.config > Open the file with a text editor (e.g. Notepad) > Locate the configuration section that begins with <add name="k2"... > Alter the connectionstring attribute to contain this additional information: Max Pool Size= ; The configuration section should look similar to this: <add name="k2" connectionstring="data Source=localhost;Initial Catalog=K2Server;Integrated Security=SSPI;Max Pool Size= "/> > Restart the K2 Server. 16. In the Managing Users and Roles topic in the concepts section of the documentation an indication is given that SQLUM is supported in K2 blackpoint. This is incorrectly stated, SQLUM is currently not supported in K2 blackpoint 0902 ( ). 17. Currently in K2 Studio it is not possible to copy a process and paste it in a new process. It is possible to copy and paste in the same process. 18. A SharePoint List can have lookup values to multiple SharePoint Lists. When creating the K2 SmartObjects only the first list is associated on the lookup. 19. InfoPath Integration and SharePoint Event Integration cannot be used in the same process in K2 Studio. 20. In K2 Studio the Succeeding Rule icon does not appear on the activity strip if there is no client event in the process. > Right-click on the activity and select Properties. > Select the Succeeding Rule icon in the right hand panel of the Activity General Properties wizard. 21. When using the Sum mathematical operator for an XML or Data field in a succeeding rule and the shared checkbox is not selected for that field a error message is displayed at runtime. The error message states ActivityInstanceDestination property not available on given context. 22. When using Management Worklist in K2 Process Portals and an item is set to Sleep as soon as a second user s work item is set to Sleep the first item changes to display as Available. 23. If a group is added to a role, K2 will not resolve the group. 24. If the K2 Worklist Web Part is modified the Configuration icon is not visible until the page is refreshed 25. In Out of Office the Forwarded users do not receive their work items if the Original Destination is part of a group which does not resolve. 26. When using the XML repeating nodes in the Mail Event in K2 Studio the ';' is not added between the addresses. Manually add the ; between the addresses in the XML. 27. In K2 Web Designer if the Action name is changed from the activity properties section and the automatically generate outcomes checkbox is selected, the outcome names and line labels do not get updated, however, if select ADD and then type the Action and select automatically generate outcomes the new outcome is added. Manually Add the outcome in the Configure the possible Outcome(s) for this step: screen. PAGE 9

10 28. When adding an action between two existing actions in the activity properties the existing outcomes will be duplicated and the new outcome will not be created. Remove the duplicates by selecting them and clicking on the Remove button. Add the outcome manually by clicking on Add. 29. If an invalid address is entered in the From field in the Mail event and the user clicks Next on the wizard screen the wizard will not continue to the next wizard screen and no error message is displayed. However, if the user clicks on Finish on the screen the validation message is displayed. 30. If a data event is used to insert a value into an Integer field on an InfoPath form, InfoPath schema validation errors occur at runtime. Set the field on the InfoPath form to a text field. Copyright SourceCode Technology Holdings, Inc. All rights reserved. Patents pending. SourceCode, K2, K2 blackpearl, K2 blackpoint, the four squares logo and K2 logotype are registered trademarks or trademarks of SourceCode Technology Holdings, Inc. in the United States and/or other countries. The names of actual companies and products mentioned herein may be the trademarks of their respective owners. PAGE 10