Hi Mike,
Thanks for posting back. Good to see your success there although as we both know it is a slightly different case (it seems) because the extension point is positioned within the <table>..</table> construct and not within the nested <ColumnListItem>..</ColumnListItem> construct. If it were I suspect you would have a similar problem in having the fragment code interpreted.
I know that I can over-ride the entire the S2 view with a view replacement, copy the standard S2 code in full and make my changes to it, but that defeats the purpose of having the standard insertion point and view extension available. To allow me to use the same view extension approach anywhere, I would rather find out how to make the S2 PO Approval extensionpoint fragment work. Cloning parts of the code just leads to maintenance problems down the track when the standard code changes and the cloned version breaks down.
I did have better success with a controller enhancement to the S3 detail view, to remove some of the action buttons that my company did not want available. To do that I used the onInit function in the S3CustomController to copy and adapt just the HeaderFooterOptions definition from the standard S3 controller, leaving out the button we didn't want and suppressing the BookmarkButton. Again I would have preferred to use object methods to set the buttons invisible but I tried several ways to do that and could not - the best I could do was to set the button disabled but it was still visible on the S3 view. This is the workflow "Forward" button that my company does not want to expose to the user community.
I still invite anyone who has succeeded in enabling a view extension fragment where the extensionpoint is within a nested object definition (as per Mike's example at the top and my follow-up example) to show us how it is achieved.
- Mark