"Upgrade of coach views" in 8.5.7 happens on two levels:
- Toolkit upgrade - when a new snapshot of a toolkit that provides coach views (UI Toolkit / Spark, Coaches, your own) is available, the app's Toolkits panel shows an upgrade icon: Upgrade re-points the dependency; all coaches using those views pick up the new implementation. Process Designer validates afterwards - options that were removed or retyped in the new views show as validation errors on the coaches (re-set them), new options get their defaults.
- Heritage coaches to coach views (the 7.5-style coaches): no automatic converter; rebuild the coach in a client-side human service with UI Toolkit controls, mapping each heritage control to its counterpart (Text → Text, Select → Single Select, Table → Table, Button → Button with boundary event). 8.5.7 offered the Convert to client-side human service action for heritage human services whose coaches already used coach views, which migrates the flow; heritage coaches inside it must still be replaced.
A safe upgrade procedure for the UI Toolkit (the one that bites most): create a new snapshot of the app before, upgrade the dependency in a new track or a branch, run the validation, walk through every coach in playback (label placement, sizing and events changed between Spark 8.5.7 versions and the IBM BPM UI Toolkit), compare a few coaches side by side with the old snapshot, then take the new snapshot. Custom coach views that extend toolkit views (copied code) do not upgrade - keep a list of them.
References