Iress ContributorAMA: I'm Laura Capozzi, Xplan Design Consultant and efficiency expert, Ask Me Anything!
Hi Laura,
Do you have advice for businesses looking at migrating from templated threads and tasks to cases? What steps can be done to minimize workflow disruptions and allow for a smooth transition into cases. We are primarily looking at cases for initial advice workflow, review workflow and implementation workflow and client offboarding processes.
Thank you
Michael
Iress ContributorHi Mchael,
Great question. I would suggest that firstly you export the thread templates and re-import them as cases. There is a solution offered by another Iress Community member located here: (https://community.iress.com/t5/Ask-the-Community-Xplan/Threads-converted-to-Case-Threads/m-p/30500). While this currently works, please note that it is not standard functionality and isn't officially supported by Iress. Note, there is a step for you to change the type in the exported file so that Xplan knows to create it as a Case.
Once you have the new cases set up, add a date to the end of the name (or an identifier) so that people know to use the new ones going forward. That way you can gradually phase out the old ones.
I would recommend that your users complete any in-flight threads through to the end as replacing them mid way could potentially cause issues as the new case would start from the first task again.
If this sounds like a bit too much re-work, a workaround could potentially be to add the existing thread to a new case (and not create a new workflow in the case itself). You could still add benchmarks to the case but you would also need to remind users to go back to the case under the client to manually link anything you have automated off the threads task outcomes.
So out of the above 2 options would you put up with a little bit of short term pain for long term gain or implement a work around that you need your users to remember to manually add benchmark item links to client cases when they could have been automated?
