April 2008 - Posts
When creating a programmatic connection to K2 (typically via either the SourceCode.Workflow.Client or SourceCode.Workflow.Management APIs) there are a number of connection options that can be used. I wanted to highlight a couple of common scenarios here.
Read More...
I found the attached document that I worked up to show how to use K2.net 2003 XML fields in an ASP.NET app as well as within a Server Event within the process. I still get asked this question a bit in regards to K2.net 2003 so I thought it worth posting.
Read More...
Attachment(s): Example - How to Work with K2 XML Fields.doc
*** Updated Slightly with version 0807 *** K2 blackpearl now supports non-AD users to interact with their workflow tasks. This is performed via the integrated SQL User Manager (SQLUM) that is installed by default with K2 blackpearl. Previously, in K2.net
Read More...
It is often desirable to enforce in your application that upon user submission of a task (e.g. the user clicks the submit button after making a decision that finishes he/her workflow client event), that the application does not proceed until the K2 process
Read More...
Below is an example of how to use the SourceCode.Workflow.Management.dll to retrieve the current StringTable for a specific Process and then modify the value of a specific entry in the stringtable: private void EditStringTableForProcess(string strProcName,
Read More...
I was asked today how to add code into a Default escalation. At first glance it doesn’t appear that there is anywhere to insert your code, because when you view the code you are shown an empty XOML. However, it is entirely possible if you drag out a WF
Read More...
There have been a couple of questions recently about how best to programmatically interact with environment settings within blackpearl process code (e.g. server events). There is an environment library server containing the fields, values and Environments
Read More...