Using SPARK containers as Template content boxes

Neil Kolban

June 14, 2016 at 12:26 pm #2132

I was doing some study on the BPM concept of Coach “Templates”.  A Coach Template is basically a Coach View that can be used as the basis for a consistent “base” for a new Coach page.  For example, if I wish all my Coaches to have a similar look and feel (for example a corporate logo), then I can create a template and from then on, when I create a Coach, I can base it on the template.  One of the rules of a Template is that is should have a Content Box within it to act as the container for the content that will be specific to a Coach instance.  I figured that if I added a SPARK container such as a “Well” that would be satisfied.  Unfortunately, when I tried it, it didn’t seem to work.  I found that if I created my Template and in the template added a “Well” and in the “Well” I added a Content Box, all worked … but I think this may be a work-around rather than desired semantics.

So … would this be an issue to pursue against SPARK or against the IBM BPM Coach View architecture?  Do we think that a Coach View that contains a Content Box should satisfy “We have a content box”?

Elliot

June 14, 2016 at 12:45 pm #2133

Hey Neil,

This is a great question and point. Adding a Content Box inside of the Well seems redundant and unnecessary considering that the Well Coach View already has a Content Box within it. Due to the Coach View Architecture being unable to recognize a nested Content Box within a Coach View, I believe that this is an issue with the IBM BPM Coach View architecture. Unfortunately, there is not much we can do to enable this functionality through SPARK.

Thanks,

Elliot P.

 

Mikael Eriksson

June 16, 2016 at 6:20 am #2189

In fact the “standard” coach views have the same behaviour. When using a section in a Coach View Template one have to add a Content Box inside the section to be able to add elements when using the template.