Solved

Legacy workflows Appit vs K2 Cloud?

  • 23 January 2018
  • 5 replies
  • 1 view
M
Badge +3

After the most recent upgrade last night all our existing workflows seem to be forcing us to the legacy Workflow Designer.  Is there a way to prevent this?   If not, does it mean that all existing (pre K2 cloud) workflows have to be replaced in order to use the new WF Designer?   It appears that FireFox is not allowed nor private browser sessions (essential in some cases).   There are many warnings about continuing to use Legacy designer.   Do we have a specific limited timeframe in which to re-write and retest all the existing workflows?  Thanks!

icon

Best answer by Vernon 23 January 2018, 21:44

View original

5 replies

Vernon
Userlevel 4
Badge +14

Hi


 


The behaviour your seeing is correct, old legacy workflows will open in legacy designer. New workflows will give you the choice to use new or legacy designers.


All workflows will need to be redeisgned in the new designer.


 


Legacy designer will be supported until the end of regular support cycles for K2 Five (5.0) - 31 December 2020 (Extended Support 2022)


https://help.k2.com/kb002091


https://help.k2.com/k2releasestrategy


 


Im sure firefox support is in the pipeline but you can also log that to ideas.k2.com this way you can get updates on the feature.


 


Using private browser sessions is not allowed with HTML designer. Not sure what use case there is to use provate when designing but if there is any feel free to log it to ideas.k2.com.


 


HTH


Vernon


 


 

C
Badge +2

So are we supposed to recreate the entire workflow manually in the new designer and then redeploy it?  Is there a way to convert an existing legacy workflow to the new format?

Vernon
Userlevel 4
Badge +14

At the moment there is no way to convert legacy silverlight worklfows to HTML workflows. You can once again log this to Ideas.k2.com for visibility.


 


HTH


Vernon

M
Badge +3

Thanks Vernon.  The use case for private/incognito sessions is the increasing use of multiple O365 subscriptions by users.  This can be a combination of their employer, other projects they collaborate on, and/or their personal subscriptions.   Unless you fully clear the cache each time the standard session cannot be reused between O365 SharePoint sites without 'invalid sign-on' type messages.  So, we have gotten around that be using (and telling others) to use private sessions.

Vernon
Userlevel 4
Badge +14

Yeah credential switching is tough in cases like this. I think your best option is to log that on the Ideas.k2.com site. Our PM team monitors that and if there is an update on the item you'll receive a mail notifying you.


 


 

Reply


View our Community Site Map

Nintex Community Sitemap
Terms & ConditionsCookie settings