Timeline for Upgrading to Tridion 2013 with active items in workflow
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 18, 2014 at 1:08 | history | tweeted | twitter.com/#!/StackTridion/status/467834011671199744 | ||
| May 15, 2014 at 20:43 | vote | accept | BryanD | ||
| May 15, 2014 at 20:43 | answer | added | BryanD | timeline score: 1 | |
| May 9, 2014 at 14:22 | comment | added | BryanD | We have not met a problem yet. Hoping to avoid problems by figuring out the best method to handle workflow after upgrading from 2011 to 2013. Vbscript has been deprecated and if I am not mistaken will be removed in Tridion 2015. We don't want to have to support vbscript and with the legacy pack installed, wont that give users the ability to continue creating templates with vbscript? When we upgrade from 2011 to 2013, there will still be many jobs in workflow. I guess we could install the legacy packs, wait for all legacy workflow items to finish and then uninstall the legacy pack. | |
| May 8, 2014 at 20:57 | comment | added | Syav4eg | And what problem have you met? Probably you need Legacy pack. In 2011 there was only VB ScriptType (default) and legacy workflow service for executing activities. In 2013 new Workflow Service was created. He can execute old VB-script activities, but for this VBScriptExecutor component must be installed (if I am not mistaken - it is part of the legacy pack). So if you had automated activities, you need Legacy pack. Also if you don't want to change your processDefinitions (scriptType ->csharp and rewrite all code) you need legacy pack. So why you don't want to install legacy pack ? | |
| May 8, 2014 at 20:46 | history | asked | BryanD | CC BY-SA 3.0 |