K2 Process Management Visual Studio Add-in Vs Live Instance Management (LIM) API

  • 8 July 2017
  • 1 reply
  • 9 views
N
Badge +4

OK so i'm using version 4.7 and I'm trying to plan for fixing workflow errors should they occur in a production scenario and I've seen the following video that uses the Process Management Tool in Visual Studio to retry workflows with new fixed versions of a workflow:

 

Video: https://help.k2.com/displaycontent.aspx?id=6239

Article: https://help.k2.com/onlinehelp/k2blackpearl/userguide/4.7/default.htm#2.Create/K2_for_VisualStudio_K2_Studio/1.Elements.K2VS/Process_Management.htm

 

I've also read the following article on the Live Instance Management (LIM) API :

https://help.k2.com/onlinehelp/k2blackpearl/devref/4.7/default.htm#Live_Instance_Management.html%3FTocPath%3DRuntime%2520APIs%2520and%2520Services%7CWorkflow%7CWorkflow%2520Management%2520API%7CLive%2520Instance%2520Management%2520(LIM)%7C_____0

 

I'm wondering why you would go down the LIM route when the Process Management Add-in seems like the quicker option of fixing a problem. Does the Process Management tool use the LIM API behind the scenes? Would I only use LIM if I wanted to automate error fixing or write my own application to do more than what the Process Management tool does? If so - does anyone know what additional stuff you can do with LIM that the Process Manageement tool can't?

 

Thanks for any suggestions here!

1 reply

M

Hi, Yes, K2 management uses the LIM API's behind the scenes. I would go down the LIM route if I'm trying to execute the same action across multiple instances and don't want to avoid causing any issues in prod as well as expedite the process or execution. 

 

for example if you want to perform the same action across 1000 instance, for example you might want to query an external data sources based on a value that was captured in your process and based on that value you'd query another system pick up a value from there then set it in the process. You can do that using the K2 management interface, but it involves a lot of manual labour and it's not error prone. 

I hope this answers your question. 

Reply


View our Community Site Map

Nintex Community Sitemap
Terms & ConditionsCookie settings