Documentation - describe changes in AIS_InteractiveConnect and AIS_MultipleConnected introduced within 6.8.0

(Tracker per the respective post on the forum https://dev.opencascade.org/index.php?q=node/1019)


Version 6.8.0 apparently introduced some signficant change about how the IO's can be connected.
The former use case as explained in my blog post (http://opencascade.blogspot.ru/2013/11/ais-connecting-objects.html) has been broken.
In particular an exception is currently thrown in ConnectedInteractive:

void AIS_ConnectedInteractive::Connect (const Handle(AIS_InteractiveObject)& theAnotherObj)
{...
  else
  {
    Standard_ProgramError::Raise ("AIS_ConnectedInteractive::Connect() - object without own presentation can not be connected");
  }
}

The change seems to be introduced in #25371 ([archived tracker link removed]), to which access is denied for
community members to get further details.

The use case as explained in the above blog post is to create a hierarchy of AIS_IO's via connection of CI and MC. Here is
an excerpt as pseudo-code:

Handle_AIS_InteractiveObject CreateIO (const SceneGraphElement& e)
{
    Handle_AIS_InteractiveObject r;
    if (e is a Part (i.e. leaf of scene graph)) {
        r = create_concrete_interativeobject();
    } else if (e is Instance) {
        Handle_AIS_InteractiveObject ref_r = CreateIO (e->reference); //recursion
        Handle_AIS_ConnectedInteractive i = new AIS_ConnectedInteractive;
        i->Connect (ref_r, location);
        r = i;
    } else if (e is assembly) {
        Handle_AIS_MultipleConnected m = new AIS_MultipleConnected;
        for (all childs in assembly) {
            Handle_AIS_InteractiveObject c = CreateIO (child_i); //recursion
            m->Connect (c);
        }
        r = m;
    }
    return r;
}

Thus, there never exists a presentation for any IO which gets connected and any interim IO will ever be displayed itself.

Neither the Release Notes nor the Visualization User's Guide invalidate the formerly valid and working use case. So please do
restore the possibility existed before and meanwhile please advise on a proper work-around.