K2Mng and K2ROM

TM01, this is just a guess, but i think you can just use the value of the K2Mng.WorklistItem.ID as if it were the same exact thing as the K2ROM.WorklistItem.SerialNumber

So, take the value from you call K2Manager.RedirectWorklistItem(worklistItem.ID, strDestUser)

and just use that same value in the K2ROM.Connection.OpenWorklistItem(worklistItem.ID, etc. etc.)

i'm mixing my syntax here because you'd need to create a connection object first in K2ROM, it's not a static method, but you probably get the point since you using the API already.

here's what i'm basing my guess on:

if you take a look at the K2 database (and this is on K2.net 2003 sp2a, by the way) you'll find a couple of stored procedures that pretty much mimc the API interface.

CREATE PROCEDURE kWorklistItemRedirect @ProcInstID INT, @EventInstID INT, @User NVARCHAR(128) 

CREATE PROCEDURE kWorklistItemOpen @ProcInstID INT, @EventInstID INT, @Platform NVARCHAR(128), @Alloc BIT, @IgnoreStatus BIT

the parameters of these sprocs are so close to the API that i can only assume they match up and that the SerialNumber in K2 is just a ProcInstID and an EventInstID concatenated and split up by the API before making the db call.

that would lead me to believe you can just use the worklistitem.ID as a worklistItem.SerialNumber and get that connection you're looking for.

hope that helps.

TM01 -- you're right, it was my bad guess. 

the following code is tested and confirms your last post.  it seems the only way to get at this ID would be to loop through all worklist items though.

k2rom_conn = new SourceCode.K2ROM.Connection();
k2rom_conn.Open("k2megasrv");
   
foreach (K2ROM.WorklistItem wli in k2rom_conn.OpenWorklist("ASP"))
{
    int id = wli.ID;
}
   
k2mng_conn = new SourceCode.K2Mng.K2Manager();
k2mng_conn.Login("k2megasrv",5252);

foreach (K2MNG.WorkListItem wli in k2mng_conn.GetWorkListItems("k2megaadministrator","","","","",null,null))
{
    long id2 = wli.ID;
}

K2ROM has a method called OpenWorklist() which can take in a WorklistCriteria filter. This makes it so you don't have to retrieve all items and then iterate. Folio is one of the options to filter on, but in the event folio isn't unique you can use a bunch of other things (like process id). It is also quite powerful because you can filter on multiple values, etc.

An example of this would be:

K2ROM.Connection conn = <open the connection, etc> 
int processId = 418;

K2ROM.WorklistCriteria criteria = 
        new K2ROM.WorklistCriteria();
criteria.Platform = "ASP";
criteria.NoData = true;

criteria.AddFilterField(K2ROM.WCField.ProcessID, 
        K2ROM.WCCompare.Equal, processId);

K2ROM.Worklist list = conn.OpenWorklist(criteria);

foreach( WorklistItem item in list )
{
//Do whatever you need to do to the items that matched your filter
}

Correct.

 In the case where you are just doing redirects (such as in this post) or something that doesn't require access to datafields/xmlfields then setting NoData = true is more performant, but when you actually need to do something to the process/activity data then you should set this to false (or not set it at all since false is the default).