Form Modelling: CDM, several relationships and abstract models

Hey, I am setting up a new model and I have quite a complicated model structure, such that I am not sure how to model it in the Form model.
Here is my model structure:

The modelling part, I am struggling with, is the right hand side → TenderRequest => Tender => Product.
The relationship is as following: one TenderRequest can hold 1 or many Tenders. Each Tender has a 1-1 relationship with a specific product. In my picture, I only modeled one product so far. “HppdoProduct”. The Product_DM is abstract.

My starting point is a TenderRequest, I have a TenderRequest_CFM, where I can select several products. Based on this user selection, I want to automatically create tender documents (via camunda), and then the user should see the riskquestions from the tender-related product on the next screen.
Is that modelling possible with a12 or do I need implementation?

I have a click-dummy to display the user flow, as I imagine it, here is the ownCloud link to it: <INTERNAL_LINK>
Here are screenshots from the click-dummy:

  1. I start with a tenderRequest Overview:

  1. Adding a new TenderRequest

  1. Start Tender

(Risk questions from the products, that were selected before are displayed)

Here, another screenshot of the user flow as draw.io- diagram. Right now, I am interested in modelling the first two steps of this diagram:

I am off on Friday, but I am gladly to talk on Monday to explain more details.

here is a screenshot from my models,and I uploaded the zip to OwnCloud: <INTERNAL_LINK>

TenderModelConcept.diagram (6.3 KB)

More linked topics will be added to sufficiently answer this question.

Hi @maria-wintry-ice

A quick question to

What are we seeing here? I assume that this is a single Tender Document with it’s linked Products. Is this correct as the discussion from CDM with multi level relationship and conditional visibility in CFM - #5 by moganian seems to suggest otherwise.

Ah, I understand the confusion.

This would actually be the fields of two “Product_subtypes” each belonging to one tender document of the tender request. So basically, the screen should combine fields belonging to 1, 2 or more product subtypes (therefore indirectly tender documents), depending on user selection.

Here I will show you a reduced example of your request. Please be aware that you should use at least the 2024.06-ext4 release for CDM support. I modeled the attached workspace using the 2024.06-ext6 release. Feel free to explore the workspace and the workflow.

Workspace download via ownCloud: [TenderRequest_2024.06-ext6]<INTERNAL_LINK>

  1. At first you start the request.

  1. The request is created and enters the first process in Camunda

  1. After entering the respective Data the processes start

  1. You recieve correctly linked documents

I did not model the following product choice