Is SUM number supported for CDM overview/Is computed field set by external service supported by CDM models?

Modeling
, ,
1

Hi team,
I have 2 CDM modeling related questions:

  1. Is the SUM number feature supported (or planned to be supported) for a CDM overview? In 2023.02 ext 1 I do not see this checkbox showing in CDM overview when modeling the column; however, I can model this for a normal overview model with same field and same SME version.

I have this field “Contract Status” as read only on the UI, the value of this field is set via a Camunda task. The field is set correctly and show correctly in a normal form model and overview model. In a CDM form model and CDM overview model, the field show empty in the UI, even though in the payload again the value is there and correct.

image
image1298×414 15 KB

example of the value showing in table binding in a form UI linked a normal document model
image
image1664×494 25.2 KB

example of the same contract in CDM overview and CDM form the field show empty

Is this a known limitation of CDM in general, or do I need to do something more specific to make this work, such as a transient field?

Thank you,

2

Hey ttnche,

  1. sounds like it should already be a feature as it is in regular Overviews. I would support you to write a Requirement Ticket for this.

  2. The CDM itself should not hold data, but the individual DMs it is comprised of. So the data should be written into the regular DM - and should be there when you open up the wrapping CDM. (Or is that already what you tried? It is not fully clear to me yet.)

3

Hi fproehl,
Yes it’s what I already tried. I open the wrapping CDM (form and overview) but the value of that field does not show up. But the value is saved and show correct in the regular DM..

image
image1536×383 67.3 KB

4

Hi Felix, for the SUM requirement, I found this ticket A12-14417 that could match my case
Regarding the calculated fields… our developers has a deeper look inside the issue and found out that the model computation that always override the value set by Camunda task. This cause inconsistency in display the expected value