DOM – How is section order defined for new instance?

Solved751 viewsDOM low code app
4
0 Comments

Hi,

I’ve created a DOM Definition, and linked it with a Behaviour Definition.

The initial state is defined as ‘Pending’.

For that state, the included section definitions are placed in a particular order.

I can see that the order is respected in the Low-Code App UI after the DOM instance is saved and enters the ‘Pending’ state.

However, when launching the form to create a new instance – meaning it is not saved and doesn’t have a state yet – the section order is not respected.

The order also doesn’t correspond with the one defined on the Definintion itself.

So my question is: where does the app derive the section order from when displaying a ‘new DOM instance’ form?

Marieke Goethals [SLC] [DevOps Catalyst] Selected answer as best 12th July 2023

1 Answer

1
4.84K 0 Comments

Hi Ruben,

Currently, the order for a new DOM instance is defined by the order of how the SectionDefinitions are defined on the DomBehaviorDefinition disregarding the statuses themselves.

Example:

  • DomBehaviorDefinition
    • StatusSectionDefinitionLinks
      • [0] StatusId: “second_status”, SecDefId: “85e3dc08…”
      • [1] StatusId: “first_status”, SecDefId: “763fdc2c…”
      • [2] StatusId: “first_status”, SecDefId: “85e3dc08…”
      • ….

I assume you would currently expect the order for a new DomInstance with an initial status of “first_status” would be:

  • “763fdc2c…”
  • “85e3dc08…”

But since “85e3dc08…” was first in the list (for another status), the order will be:

  • “85e3dc08…”
  • “763fdc2c…”

As a workaround, you could define all links for the initial status in the expected order at the start of the links collection.

A change will be required so that status is also used to order the sections.

Marieke Goethals [SLC] [DevOps Catalyst] Selected answer as best 12th July 2023