What is the impact if pyMigrateIntraction cases takes long time to execute post upgrade to 8.7.2
We are upgrading to 8.7.2 from 8.4 and understand a new DB table pc_work_triage has been introduced as part of the release ro map instances of class Work-Channel-Triage.There is also a new JS pyMigrateInteractionCases to help with the migration post release.
Considering we have many instances in the pc_work tabler for Interaction cases whihc would be In Progress,what is the impact on this to the end users and do we need to cater for any thing else except running the JS post upgrade and aldo adding additional columns for exposing
Pegasystems Inc.
IN
Hi,
As per the release notes (ref : https://docs-previous.pega.com/platform/release-notes-archive?f%5B0%5D=releases_version%3A32691&page=7),
email BOTs will be using this new table. and JS "pyMigrateInteractionCases" triggers automatically during the update process. Additionally The job scheduler migrates unresolved triage cases first, and once complete, the system migrates the resolved triage cases.
If there are exposed columns there is a pre activity step to be performed, so that migration is successful during update activity.
Please refer : https://docs-previous.pega.com/conversational-channels/87/migrating-triage-cases-new-tables.
Thanks
Suhas