You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In a Silverstripe 3.7 --> 4.4 upgraded codebase, the "WorkflowInstance" table leaves legacy values in some columns: ClassName and TargetClass.
The logic may already deal with "ClassName" field values of "WorkflowInstance" (as opposed to its FQCN), but the workflow admin breaks with refs to "SiteTree" vs its FQCN. TO fix it, I just wrote a quick BuildTask that updates the x3 refs, but then all the "rogue" TargetClass values were all the same.
The text was updated successfully, but these errors were encountered:
In a Silverstripe 3.7 --> 4.4 upgraded codebase, the "WorkflowInstance" table leaves legacy values in some columns:
ClassName
andTargetClass
.The logic may already deal with "ClassName" field values of "WorkflowInstance" (as opposed to its FQCN), but the workflow admin breaks with refs to "SiteTree" vs its FQCN. TO fix it, I just wrote a quick BuildTask that updates the x3 refs, but then all the "rogue"
TargetClass
values were all the same.The text was updated successfully, but these errors were encountered: