3.5 Some of our workflows have been developed under the framework. We use that tracking only to work just fine. We are trying to change the framework of building our code to 4.0 and we had no problem with it. The workflow was converted into a form.
After going to 4.0 and tracking it, after creating a new workflow, it works fine. But when attempting to continue a workflow frequency, which was previously built 3.5 with the creation of the application, the workflow runs as expected, but SqlTrackingService does not write tracking data.
I tried debugging Assenbug and I saw runtime does not see whether a tracking service is connected or not getting a tracking profile.
I saw that a new type of type was added to the [type] table with version 4.0.0.0.
Was anybody walking in this situation, where you should go to the 4.0 framework, even then the old workflow will continue?
You can document workflow tracking migration.
And the migraine process.
Comments
Post a Comment