Release Notes1.1 Skelta BPM.NET 2009 March 2010 Release <Version > Date: 20 th May, 2010

Transcription

1 Skelta BPM.NET 2009 March 2010 Release <Version > Date: 20 th May, 2010

2 Document History Date Version No. Description of creation/change 30 th March, Release Notes for March Update th May, Release Notes are modified based on Skelta BPM.NET 2009 March 2010 Release. With this change March Update can be applied both as a upgrade or new build Skelta Software,

3 Table of Contents INTRODUCTION... 5 Purpose of this Document... 5 SCOPE OF THIS DOCUMENT... 5 Release summary... 5 NEW FEATURES AND ENHANCEMENTS... 5 Forms performance has been enhanced and optimized... 5 Memory tuning for workflow engine... 5 Multiple outputs from Invoke Form activity... 5 Allow null values in default text property of drop down control... 9 Facility to add individual BAM report to aspx page or Sharepoint site Sort on subject column in WorkItem inbox Opening work item detail page (Custom ASPX page) on double click on WorkItem list Retain Sort order in Work Item inbox after submitting a work item Option to disable logging of strings System variable to store timeout warning value Skelta BAM tree with one level expanded view HTML Print Mail Channel - Disable reply for invalid s Two New fields added to engine configuration Facility to close the form when submitted through MINOR ENHANCEMENTS Setting default ideal time span for resuming EP workflows to 5 hrs Default storage option of XML variable changed to Variable Date format to be as per Actor Culture in Mail Channel Property Stop Action on Exceptions added for ForEach-Loop Activity New action output for List Navigator Activity Form submission on enter click Opening of form in maximum mode by default Edit Form description through forms designer Hide header for forms Setting the grid column caption for lookup header ISSUES FIXED IN THIS RELEASE Activities Business Activity Monitoring Skelta Forms Skelta Queues Calendar Work Item List Skelta Object Access Mail Channel Farm Configuration Skelta Software,

4 Skelta Upgrade Manager Process Designer SharePoint Forms Engine Security CHANGES IN USER INTERFACE Lookup Control if rendered as drop down API Changes API to Save ResourceSet Activity variables New API to find out whether a list item having child items or not API Changes for Submit of Invoke Form Activity OTHER CHANGES Show Save as Draft button? removed from Form properties KNOWN ISSUES INSTALLATION INSTRUCTIONS Installation Instructions for this Release Types of Support if you still face problems RELATED DOCUMENTATION Skelta Software,

5 Introduction Purpose of this Document The purpose of this document is to list out the changes made as a part of the March 2010 Release for Skelta BPM.NET Scope of this Document This release note covers only Version of Skelta BPM.NET Release summary Product: Skelta BPM.NET 2009 Version: < > New Features and Enhancements This release of Skelta BPM.NET 2009 March 2010 release includes the following enhancements: Forms performance has been enhanced and optimized Forms performance has been enhanced and optimized in this release. You have faster loading forms that allow you to perform your tasks quicker. Memory tuning for workflow engine Overall workflow performance has been enhanced and optimized in this release. Multiple outputs from Invoke Form activity This feature enables you To specify multiple conditions using form button and form control values and in effect set different outputs for the Invoke Form activity. Each output can be marked as completion maker or not. If no output is marked as completion maker, the task remains in the Inbox. To set whether the output instance xml is to be updated with the input data of the form for all the outputs or only for the outputs which are of type completion makers. Example Scenario Purchase Order Requisition Process Skelta Software,

6 A purchase order submitted by a user is sent for manager s approval. During the approval process, the manager has options to Approve, Reject, Apply Corrections or Keep On Hold the request. - When the manager approves the request, the same is added to the Skelta list that stores all the approved purchase order for further processing. - When the manager rejects the request, the information is send back to the requestor with valid comments for rejection. - When the manager opts for Apply Corrections, the same request is send back to the requestor with the comments from manager for applying required corrections before resubmitting. - And when the manager keeps the request on hold, the same request is retained in manager s inbox for later processing with information being sent to the requestor saying the request is kept on hold. How is this possible? A new property has been added to the Invoke Form activity under Decision Influencers. Figure: Property Possible Distinct Outputs added under Decision Influencers Add new rule for distinct output in the Invoke Form Action Outputs. Skelta Software,

7 Figure: Adding new rules for distinct outputs WorkItemSubmissionContext enables you to select form submission related information. It consists of button pressed, FormInstanceXML, RespondngUserName and WorkItemId information. Skelta Software,

8 Figure: Setting condition for the rule Specify whether is output is a completion maker or not. Also we can set whether the output instance xml to be updated with the input data of the form for all the outputs or only for the outputs which are of type completion makers. Skelta Software,

9 Figure: Set Completion maker for outputs and Update output instance xml To generate the conditions automatically for the buttons available in the form, you have the option to either use this button to generate the conditions or create conditions on their own using form fields and button pressed text. Figure: Generate condition for form buttons Please refer topic Using Skelta BPM.NET Activities Human Activities Invoke Form Activity Invoke Form Possible Distinct Outputs in the Skelta BPM.NET 2009 Developer Guide for more details. Allow null values in default text property of drop down control Skelta Software,

10 You can now have a Null (case insensitive) value as the default text of the drop down control. Example Scenario Suppose in a form you have a mandatory drop down box and by default you need to show it as blank. How is this possible? Go to an Advanced property called Default Text and set it as Null (Case Insensitive). Figure: Default Text property of drop down box Skelta Software,

11 Figure: Null value has been added for the drop down box Please refer topic Skelta Forms Forms Designer Toolbox to design forms -> Controls to design forms -> Drop Down in the Skelta BPMNET 2009 Skelta Lists and Forms for more details. Facility to add individual BAM report to aspx page or Sharepoint site This feature enables you to render individual BAM report in an aspx page or Sharepoint site. Characterstics of the report can be controlled by specifying the report properties. Also the rendering of the reports is purely based on security rights. Example Scenario Scenario 1 - Suppose an organization wants to render a particular report on its home page. It can be achieved by using this new feature of Skelta BAM control. Scenario 2 - Suppose an organization wants to render a particular report on its Sharepoint website. How is this possible? 1. Drag and drop the Skelta BAM control to any aspx page. 2. Set the BAM properties Scenario 1 IsAnIndividualReport: If this property is set as true, it enables the individual report rendering. Else default configurations will be considered for rendering the report. ReportName: This is the hierarchy of the report in the BAM Control. Example: In order to render all the executing instances in an aspx page, ReportName property can be set with Analyze/Execution/Executing ReportID: This is a unique Id for any report. This information will be taken from the database where the report information is stored. ID column of SKBAMMenu table, this information will be unique. Width: Width of the Control can be controlled by this. Height: Height of the control can be controlled by this. ReportTitle: Title of the report which will be displayed on the top left corner of the report. Skelta Software,

12 ReportDescription: Description for the report which will be displayed next to the report title. Scenario 2 In SharePoint it is possible to set properties to the BAM control in order to render an individual report. Figure: BAM Control properties in Sharepoint Please refer topic Using Skelta BPM.NET Controls BAM Control To add individual BAM report in an aspx page or Sharepoint site in the Skelta BPMNET 2009 Developer Guide for more details. Skelta Software,

13 Sort on subject column in WorkItem inbox This feature enables you to sort the WorkItem inbox on the subject column. Please refer topic Using Skelta BPM.NET Controls -> Workitem list Control in the Skelta BPMNET 2009 Developer Guide for more details. Opening work item detail page (Custom ASPX page) on double click on WorkItem list Now you can configure the options to view the workitem detail page. It can be set to be viewed on double click or on row select as required. How is this possible? A property exposed on SharePoint workitem list web part ShowDetailsonRowDoubleClick. Please refer topic Using Skelta BPM.NET -> Using Skelta BPM.NET features within Sharepoint -> Working with Skelta SharePoint Web Parts -> Work Items list Web Part in the Skelta BPMNET 2009 User Guide for more details. Retain Sort order in Work Item inbox after submitting a work item This feature retains the sort order in Work Item inbox after submitting a work item. Note: User can create a Global Layout by rearranging columns, specifying width for the column etc. You can retain sort order with saved global layout also. Example Scenario For example take a scenario where you were sorting items in a work item inbox based on the Priority column after loading the workitem list control. Then you selected a row to open the detailed window to act on it. After acting on the task the sort order on Priority column is now retained. Please refer topic Using Skelta BPM.NET Controls -> Workitem list Control in the Skelta BPMNET 2009 Developer Guide for more details. Option to disable logging of strings This feature enables you to control the string messages getting logged into the logger files without making any change to the debug level. Example Scenario Skelta Software,

14 Suppose your debug level is set as 2. And you want to restrict some messages containing text, For Example, Inserting local variables from getting logged into the logger file without changing your current debug level. How is this possible? 1. Create a New Key in BPM.NET Registry named DoNotLogMessages of type Multi-String value. Figure: New Key in BPM.NET Registry 2. Specify the text of the messages which are to be ignored while writing to the log files. Skelta Software,

15 Figure: Message Texts to be ignored 3. Restart services. Please refer topic Using Skelta BPM.NET Advanced Features -> Using Message Logs -> Option to disable logging of strings in the Skelta BPMNET 2009 Developer Guide for more details. System variable to store timeout warning value This feature enables you to store the timeout warning value for any human activity by creating a new system variable. Note: Multiple timeout warnings cannot be tracked using this feature. Example Scenario Suppose if want to store the timeout warning value for an Approval activity in your workflow. The naming convention for the system variable to be declared is ^<ActivityName>ResponseByWarningTimeout The value returned by the variable will be in UTC format. For multiple user scenarios the highest timeout value calculated for a user will be available in the variable. How is this possible? 1. Add a Human activity in the workflow 2. Create a variable in start activity with name as <ActivityName>ResponseByWarningTimeout 3. Set the Timeout warning for Activity property for the human activity. 4. The variable gets populated with value after the human activity is executed. 5. The variable can be accessed in next step to check the value. The value stored will be in UTC format. Please refer topic Using Skelta BPM.NET Activities -> Human Activities -> Approval Activity in the Skelta BPMNET 2009 Developer Guide for more details. Skelta BAM tree with one level expanded view The BAM tree in the Skelta Business Activity Monitoring interface now by default shows a one level expanded view instead of a fully expanded tree view. Skelta Software,

16 Figure: Skelta BAM tree with one level expansion Please refer topic Working with Skelta BPM.NET -> Skelta Enterprise Console -> Business Activity Monitoring and Reports -> About the BAM in the Skelta BPM.NET 2009 User Guide for more details. HTML Print This feature enables you to take a print of a form. Two new controls have been added for this functionality HTML Print and Print Label. How is this possible? 1. Suppose you have a form named Employee with the HTML Print control added to it. Figure: Employee Form Skelta Software,

17 2. Create a copy of this form through export and import, say EmpPrint and replace the controls with Print Label control for a printer friendly form view. 3. Set the Select Printable Form property of the HTML print control. Figure: Select Printable Form property of HTML print 4. Select EmpPrint form as the print template. Skelta Software,

18 Figure: EmpPrint form as Print template 5. Click on the Print button of the Employee form to view the printable form and the Print dialog box. Figure: Printable form Please refer topic Using Skelta Forms and Lists -> Forms Designer -> Working with Forms -> Printing a Form in the Skelta BPM.NET 2009 Skelta Forms and Lists for more details. Skelta Software,

19 Mail Channel - Disable reply for invalid s If any invalid comes to the notification engine, an automated reply System could not process your mail. Some of the keywords not found in your mail to process it. Please reply to the original message again will be send to the from address with the same subject. This action has been made configurable now. User can disable this reply if required. How is this possible? Add a registry string value called SendReplyForInvalidMail under HKEY_LOCAL_MACHINE\SOFTWARE\Skelta\BPM.NET and set its value data as NO. Please refer topic Using Skelta BPM.NET Activities -> Communication Activities -> Configuring Communication Activities -> Disable reply for invalid s in the Skelta BPM.NET 2009 Developer Guide for more details. Two New fields added to engine configuration Two new fields DeleteFinishedWorkFlows and LogMessages have been added to engine configuration. DeleteFinishedWorkFlows It enables you to control the deletion of workflow entries from the SWFeCount table that are successfully resumed. By default, such entries are automatically deleted. LogMessages - It enables you to control the log messages in the logger console whenever the engine tries to resume Execution Pending or Finished with Errors workflows. Example Scenario Suppose if you wish to retain the entries in the SWFeCount table for workflows that are successfully resumed then you can use DeleteFinishedWorkFlows field settings. Also if you wish to control the log messages getting logged into the logger files then LogMessages field settings can be used. How is this possible? DeleteFinishedWorkFlows 1. Go to Farm database. 2. Open the SKServiceMapping table, and add the following tag to the existing XML in the properties field for the record where name is equal to SkeltaWorkflow2. <property key="deletefinishedworkflows">true</property> LogMessages 1. Go to Farm database. 2. Open the SKServiceMapping table, and add the following tag to the existing XML in the properties field for the record where name is equal to SkeltaWorkflow2. <property key="logmessages">true</property> Please refer topic Administering Skelta BPM.NET Skelta BPM.NET Advanced Settings Auto Resume Feature for FE and EP workflows in the Skelta BPMNET 2009 Administrator Guide for more details. Skelta Software,

20 Facility to close the form when submitted through This feature enables you to decide whether form page can be closed or not when user submits the form from the . Example Scenario Suppose an organization wants its user to fill a form through and on submission form window should get closed. How is this possible? A new property Close the form on click of finish? has been added in the Invoke Form activity under Notification Contents. Figure: Close the form on click of Finish? Please refer topic Using Skelta BPM.NET Activities Human Activities Invoke Form Activity in the Skelta BPMNET 2009 Developer Guide for more details. Minor Enhancements Setting default ideal time span for resuming EP workflows to 5 hrs Workflow engine tries to fetch the workflow instances that are in the Execution Pending state if that instance is idle for at least 5 hours. The default idle time for trying to resume of EP workflows is now changed to 5 hours from the earlier set value of 2 hours. This cannot be less than 5 hours. If it is less than 5 hours, then by default, the engine will consider 5 hours as idle time. Skelta Software,

21 Please refer topic Administering Skelta BPM.NET Skelta BPM.NET Advanced Settings Auto Resume Feature for FE and EP workflows in the Skelta BPMNET 2009 Administrator Guide for more details. Default storage option of XML variable changed to Variable The default storage option of XML variable is now changed to Variable. Figure: Default storage option for XML variable XML Document is now Variable Please refer topic Using Skelta BPM.NET Activities Start Activity XML Variables -> Introduction to XML Document XML Variable in the Skelta BPMNET 2009 Developer Guide for more details. Date format to be as per Actor Culture in Mail Channel The date format of the Submitted On field in the Mail Channel will now be based on the actor s culture instead of the culture configured on the notification engine server. For Example, if the culture set for the actor is English (United Kingdom) then the date format will be DDMMYYYY. Skelta Software,

22 Figure: Culture setting for an actor Please refer topic Enabling Human-Workflow Interaction and Outlook Integration -> Date Format in Template in the Skelta BPMNET 2009 Developer Guide for more details. Property Stop Action on Exceptions added for ForEach-Loop Activity A new property Stop Action on Exceptions is added to ForEach-Loop activity which allows the user to specify whether to stop the activity and finish the workflow with errors or to continue the normal workflow execution in the case of an exception. Figure: Stop Action on Exceptions Please refer topic Using Skelta BPM.NET Activities Engine Activities For Each Loop Activity in the Skelta BPMNET 2009 Developer Guide for more details. Skelta Software,

23 New action output for List Navigator Activity New action output List Item Not Found has been added for List Navigator activity. This output will be given for the activity, when the list query specified does not return any items. Figure: New action output for List Navigator property Note: Enable Errors Encountered Output property of List Navigator should be set as No to capture this output. Please refer topic Using Skelta BPM.NET Activities List Activities XML List Navigator Activity in the Skelta BPMNET 2009 Developer Guide for more details. Form submission on enter click A new property has been added to the Advanced tab of forms Can submit form when enter key is pressed. If yes, the form gets submitted on enter click. Skelta Software,

24 Figure: Form submission on enter click Please refer topic Skelta Forms Getting Started with Skelta Forms About Skelta Forms Interface -> Skelta Form Properties in the Skelta Lists and Forms for more details. Opening of form in maximum mode by default Whenever you open a form for preview or fill, it opens in maximum mode. A new property Maximize window when form loads has been added to the Appearance tab of forms. Skelta Software,

25 Figure: Maximize window when Form loads? Note: The same property has been added for the Invoke Form Activity as well. Please refer topic Skelta Forms Getting Started with Skelta Forms About Skelta Forms Interface -> Skelta Form Properties in the Skelta Lists and Forms for more details. Edit Form description through forms designer The description column of form list item can be updated through the Forms designer. Figure: Description column to be updated Skelta Software,

26 Figure: Form description can be updated here Please refer topic Skelta Forms Getting Started with Skelta Forms About Skelta Forms Interface -> Skelta Form Properties in the Skelta Lists and Forms for more details. Hide header for forms This feature enables you to hide the form header if required. A new property Show top level title? has been added under Advanced tab for forms. Skelta Software,

27 Figure: Show top level title? Please refer topic Skelta Forms Getting Started with Skelta Forms About Skelta Forms Interface -> Skelta Form Properties in the Skelta Lists and Forms for more details. Setting the grid column caption for lookup header The Grid Caption property of Skelta List Control has been enhanced to set the grid column caption for the lookup grid when a lookup is created from Skelta List. Example Scenario 1. Create an Employee list; add two Text input controls as "Employee Code" and "Employee Name". Provide the grid caption property value for the Employee Name control as "Name". Skelta Software,

28 Figure: Employee List and Grid caption property 2. Now create a lookup for this list and select the above columns as the display columns for the lookup. 3. Create a new form and add the lookup control. 4. Select the lookup created in the above steps as the data source for the lookup control. 5. Preview this form. 6. When this lookup is selected to add items, lookup header columns will display the Employee Code column & Name column instead of Employee Name. Figure: Employee form with lookup added Note: This feature is supported for Skelta list lookup only. Skelta Software,

29 Issues Fixed in this release The following issues have been resolved in this release. Activities The following activities issues have been fixed. Issue To Customize the format of storing Comments for Human Activities Foreach-Loop activity completed successfully even when there was an exception occurring for the activity The List Navigator Activity gave the output as Action Completed even when the list items were not found. Knowledge Base Article Business Activity Monitoring The following Business Activity Monitoring issues have been fixed. Issue Knowledge Base Article Performance issue fix for KPI/Trend/OverdueChart Drill Downs Showing workitem field information for Work Analysis and Resource Analysis Insert with AND condition (KPI data point) enhancement Error in WorkItem Details report drill down Error while accessing workitem details of BAM Reports on the Production Server Skelta Forms The following Skelta Form issues have been fixed. Issue Knowledge Base Article Day and Month swapping for Date control inside a grid in a form In the case tab and tabs control, buttons (add, edit, delete, drag and drop) not visible on first load. In Firefox browser, the attachment control will truncate the file name if the file name consists of a space in between. Script written for a button inside the tab control not getting fired. User lookup control's filter expression fails to fetch Sharepoint users Skelta Software,

30 Issue while opening attachments from SharePoint Date Time issue in Skelta Forms Attachment form field s issue Skelta Queues The following Skelta queue issues have been fixed. Issue Knowledge Base Article Taking ownership allowed for a workitem even it is removed from the inbox Queue participants grid resize issue Calendar The following calendar related issues have been fixed. Issue Knowledge Base Article Error while deleting a work slot from a calendar Work Item List The following Work Item List issues have been fixed. Issue Knowledge Base Article Manage work items error when security is disabled Work item list loads with the default view before switching to global layout view Performance reports in BAM showing error ''Column already added to the table'' Workitem detail pops up while doing a sort on the workitem list with a row selected. Inbox takes full screen height if ShowInboxViewOnly property is set as true Subject changes when the task is picked from the Queue. Skelta Object Access The following Skelta Object Access (SOA) issues have been fixed. Issue Knowledge Base Article Assembly name resolving problem Skelta Software,

31 Mail Channel The following Mail Channel issues have been fixed. Issue Knowledge Base Article Link to the work item page through the mail breaking down in rare scenarios "Response Rejected" mail received on replying to a human activity Mail templates with XML variables as placeholders failed to display the XML variables values Mail Channel (Wait-for- Activity) Issue Farm Configuration The following Farm Configuration issues have been fixed. Issue Knowledge Base Article DMS Product name was not getting listed in Farm configuration. Data not being fetched by ListTable control of a List form App_Code folder not getting created in the EnterpriseConsole sites Exception occurred while loading Hidden Repository Skelta Upgrade Manager The following Skelta Upgrade Manager issues have been fixed. Issue Knowledge Base Article Current machine name does not exist in the farm error message while running Skelta Upgrade manager Process Designer The following Process Designer issues have been fixed. Issue Knowledge Base Article When the child workflow variable is null there is an error while getting the data from the Context object. Activity with numeric workitem field set is failing to execute Skelta Software,

32 SharePoint The following SharePoint issues have been fixed. Issue Knowledge Base Article ID, Display text and value node for SharePoint content types XML variable Issue of multiple logging of error messages when SharePoint dll s were found in application s BIN folder but SharePoint is not installed on that machine. Authentication issue when the work item was viewed from different zones. Access denied error in SharePoint document view SharePoint central admin - mapping repository to a web application issue Forms Engine The following forms engine issues have been fixed. Issue Knowledge Base Article XML variables get unexpected or repeating node values during the workflow execution Incorrect handling of multi paragraph data by rich text box control Notification Engine Performance Issue Incorrect behavior for XML variable (XML document) with local scope workflow step getting executed twice Security The following security related issues have been fixed. Issue Description In the security group screen in all the places, an exception was getting thrown which said: "ID column does not belong to table". Skelta Software,

33 Changes in User Interface Lookup Control if rendered as drop down Css style has been changed for the lookup control header if the lookup control is rendered as drop down. Figure: Change in Lookup control header API Changes The following changes have been made to the APIs. API to Save ResourceSet Activity variables Reason: While submitting the ResourceSet Activity using workitem submit method, there is no need to save the variables now to store the resource information as this will be done internally. Old: //user has to write the logic to store the variables before saving workitem.submit("webworklist", Proceed, "", "", ""); New: //no need to save the variables and pass the ResourceIDs while calling the workitem submit method Skelta Software,

34 workitem.submit("webworklist", Proceed, ResourceIds, "", ""); Note: Pass resource information while calling Submit method. New API to find out whether a list item having child items or not Reason: Earlier we had one API (HasChidItems) which will accept list definition and list item objects as parameters and return type as Boolean. This API was very expensive if you want find out whether child items are there or not for different list items recursively. By considering this scenario, we introduced one more overload of this API (static), this over load accepts application name, list table name & list item id as parameters and return type as Boolean. New: //No need to create listitem object as it was static API. //Returns true if the list item has child items otherwise it returns false. ListItem.HasChildItems(<string:ApplicaitonName>,<string:ListTableName>,<GuId:ListItemId>) API Changes for Submit of Invoke Form Activity Reason: While submitting the Invoke form activity, we need to pass the instance XML of the form to the work item submit method. To achieve this, new overload is added for the Submit method of work item class. This change is to make use of the submitted form instance XML in work item submission context for the new Possible Distinct Output property. Moreover, the earlier procedure of saving of the form instance XML before work item submit should not be removed, since this is handled internally. Old: //saving of form instance xml to the output xml variable workitem.currentcontext.xmlvariables[outputvalue].rawxml = FormRenderer1.FormDefinition.FormInstanceXml; workitem.currentcontext.xmlvariables[outputvalue].save(); //submit the work item adapter.currentworkitem.submit(adapter.channelname, "Action Completed", "Action is Completed", "Action is Completed", syncdata); New: //getting the clicked button text string clickedbuttontext = e.buttontext; //getting the submitted form instance xml string instancexmldata = FormRenderer1.FormDefinition.FormInstanceXml; //building comments to the work item string outputcomments = "Acted on + clickedbuttontext + " button."; //get the synchronus action data Workflow.NET.Engine.SynchronousActionData syncdata = new Workflow.NET.Engine.SynchronousActionData(false, this.context, true); //if adapter is not created in the page use the below code //Skelta.HWS.WorkListChannel.Web.WebWorkItemAdapter adapter = new Skelta.HWS.WorkListChannel.Web.WebWorkItemAdapter(); // adapter.processwebchannelrequest(); //submit the work item.. Check this overload, form xml is passed to submit method Skelta Software,

35 adapter.currentworkitem.submit(adapter.channelname, clickedbuttontext, "", outputcomments, syncdata, ref instancexmldata); //save the state of form instance, inorder to open the changes again when the work item is opened adapter.currentworkitem.setstateforforminstance(channelname, FormName, instancexmldata); NOTE: Pass the form instance xml to the submit method. Depending on the storage provider of the output xml, this XML can get internally changed due to update. So you should set the respective channel form state of the work item only after the submit call. Also note, if you have customized the invoke form activity s document view to submit the form, then replace the above old code with new code. Other Changes Show Save as Draft button? removed from Form properties Show Save as Draft button? property has been removed from the Form properties Advanced tab. Figure: Show Save as Draft button? property has been removed Skelta Software,

36 Known Issues The following are the known issues in this release of Skelta BPM.NET March Release Extra node is added to the XML variable (XML document) when no value is passed to it Lookup control when rendered as a drop down, displays the previously set text value even if the value is set as null. The link to the knowledge base article for this issue is 3. Skelta Farm and Backup Recovery wizard does not provide the SQL Authentication option in Database User Settings. The link to the knowledge base article for this issue is 4. There is a decrease in performance when multiple workitems (300 or more) are submitted together from the workitem list When user clicks on Show All Versions option in the context menu of Manage Form list, the version grid will be rendered. In the version grid the Created On column shows UTC time instead of current culture/local time 6. Not able to set value containing & to the child node of a XML variable or nodes of XML iterator type XML variable BAM Performance Report configured with Queue and Resource calendar throws an error (Error while processing report) in Oracle environment while processing Importing a list having lookup control causes page crash when the list is loaded Multiline text control s Ondatachanged script not getting evaluated in some scenarios Lookup control gets dissociated with its dropdown frame on scrolling Click of Html print button after importing the form causes a page crash. Installation Instructions Installation Instructions for this Release Please see the Upgrade Instructions document for applying March Release. Types of Support if you still face problems If you still face problems with installation, you can take help of the support plan that you have. Skelta provides the following types of support for Skelta BPM.NET. Type of Support Telephone Support Description and details Contact support at through phone for limited support at: Skelta Software,

37 Tel US: +1 (678) , India: +91 (80) Support You may write to for all your issues. Skelta Knowledge Base Skelta Forums You may also search to the Skelta Knowledge Base at: to find articles relevant to your need. Skelta Forum is an interactive platform for discussing all product or technical issues. Please visit for more details. Skelta Software,

38 Related Documentation The link to the complete documentation set for the Skelta BPM.NET 2009: Skelta Software,