...
Ideally, channel deletion would find and drop all references to the channel in user layouts, to maintain referential integrity in the uPortal data model (no layouts reference non-existing channels). Even more ideally, it would have an ability for a deployer to replace the references with references to a different channel, thereby easing failing over a doomed channel to a replacement message as described above. These enhancements would reduce the incidence of layouts referencing deleted channels.
| Warning | ||
|---|---|---|
| ||
Are you sure you want to delete SplatUpdates?
(x) drop references to this channel from layouts (including end user composed layouts and centrally managed layouts). (Yes, delete the channel) (No, do not delete the channel) |
There are 47 end user composed layout fragments and 3 centrally managed layout fragments referencing this channel. How would you like uPortal to handle references to this channel?...
| Warning | ||
|---|---|---|
| ||
Are you sure you want to delete SplatUpdates? No end user managed layouts and no centrally managed layouts reference this channel. (Yes, delete the channel) (No, do not delete the channel) |
Implementation
Dropping referencs to channels at the time of channel deletion could be implemented by a callback to the LayoutManagers to advise them that a channel has disappeared. Supporting Layout manager implementations would update their layout definitions to no longer use the deleted channel, replacing it with another channel if so advised.