Important Notice: Our web hosting provider recently started charging us for additional visits, which was unexpected. In response, we're seeking donations. Depending on the situation, we may explore different monetization options for our Community and Expert Contributors. It's crucial to provide more returns for their expertise and offer more Expert Validated Answers or AI Validated Answers. Learn more about our hosting issue here.

What doesn work when deployed K2.net 2003 processes are migrated to a K2 blackpearl server?

April 26, 2017blackpearl deployed k2 k2.net migrated Processes server

0

Posted

What doesn work when deployed K2.net 2003 processes are migrated to a K2 blackpearl server?

1 Answer

0

Posted

• The goal of the backward compatibility features of K2 blackpearl is100% cross-version compatibility. This means that everything, including custom code, should work in K2 blackpearl the same way it did in K2.net 2003. However, destination queues are converted to roles and you may have to add custom assemblies to the GAC on the server running K2 blackpearl. You should always test and confirm that processes run 100% as expected in a test environment before migrating your production environment. • OOF features in K2.net 2003 will work in K2 blackpearl • If you are using the SQL user manager (SQLUM) in K2.net 2003 you cannot migrate to K2 blackpearl at this time.