Loading Documents From Custom Overviews With BAP

Client
1

For a custom view, which serves the role of an overview (a gantt chart), we want to have the ability to open a FormEngine with document data.

Our custom view does have a different model set in the appmodel.ts/the Redux store, than the model we want to load in the FormEngine. (Otherwise, BAP would always show the standard overview when clicking on the navigation item intended to show our custom overview).

Previously, with [BAP 2.x, we achieved this by dispatching a CRUD/SELECT_ROW action.]<INTERNAL_LINK>
This action could carry, among other things, a model in the payload, and worked for our use case.

Now, with [BAP 3.0, the CRUD/SELECT_ROW action does not carry this information anymore]<INTERNAL_LINK>, and the model for the FormEngine activity is now taken from the creating activity.
When dispatching such a CRUD/SELECT_ROW action, it will result in an error state, and the FormEngine will not be displayed. In the listing below you see the store values (and the error) for the FormEngine activity that are created after the action has been dispatched:

{
  '3331': {
    id: '3331',
    activationTimestamp: 1551948202090,
    descriptor: {
      model: 'Gantt',
      instance: 'DomainRelease/60'
    },
    initiatingActivityId: '1803',
    data: {},
    loadingState: 'error',
    savingState: 'not_saved',
    slices: {},
    dirty: false,
    busy: false,
    error: {
      errorCode: 'INTERNAL_CLIENT_ERROR',
      message: 'No scene reference found for activity 3331.'
    }
  }
}

To me, it seems that the problem is that the model field for the FormEngine activity in the store does not correspond to the actual model we want to load.

Is there some recommended way to implement our requirement of loading documents in FormEngines from custom “overviews” for BAP 3.0?

2

The CRUD components are only provided as a replacement for the Form App “zero coding” feature where you have a simple combination of overview and form engine with homogeneous documents. In prior releases, this was not stated clearly in the documentation. Please see <INTERNAL_LINK>

For your use case, please use the regular Engine components: <INTERNAL_LINK>