UiPath Documentation
action-center
latest
false
Action Center user guide

Expanding and collapsing field groups in the Validation Station

Field group collapse in the compact Validation Station view: closing a whole group or a single instance, and what the dot on a closed group reports.

A field group holds a set of related fields. The same group can be extracted more than once from one document, and each of those instances brings its own copy of every field in the group. So the field list ends up with more fields than the taxonomy defines.

Closing a group hides everything inside it. Closing a single instance hides just the fields of that instance and leaves the rest of the group in place. Either way the list gets shorter, and the values still waiting on a decision are easier to find.

Only field groups can be closed this way. Tables and simple fields have no collapse control, and collapsing works in the compact view only. Collapsing only changes what the field list shows: it never touches the action, the document, the taxonomy, or the extraction result, and it never confirms or clears a value.

Two levels of collapse

Every extracted field group has two chevrons:

  • The group chevron sits to the left of the field group name. It closes the whole group, hiding every instance at once.
  • The instance chevron sits at the start of each instance summary. It closes only that instance and leaves the others open.

Both point down when open and right when closed, and both report their state to assistive technology.

A field group nested inside another one has the same two chevrons, so a branch can be closed at whatever level is useful. Closing an instance also hides the nested groups inside it.

The field group header

A field group with at least one instance reports the number of instances in its header, as 1 instance or as a count followed by instances. The number stays in the header while the group is closed, so the size of a closed group is visible without opening it.

Flagged issues behind a closed group

A colored dot appears on any closed group or instance that hides a value still needing attention. On a group the dot sits in the header, before the instance count. On an instance it sits at the end of the instance summary, before its checkbox.

The dot appears only while the group or instance is closed. Opening it again removes the dot, because each value inside shows its own indicator once it is visible.

What the dot reports

A field has a flagged issue when any of these is true:

  • A business rule on the field is broken, at any criticality.
  • One of its values fails validation: a required value left empty, or a value that does not match the format its type expects.
  • One of its values is not confirmed and its confidence sits below the threshold set for it in the taxonomy.

An instance is flagged when any field inside it is flagged, nested groups included. A field group is flagged when a rule on the group itself is broken, or when any one of its instances is flagged.

How severe the dot is

The dot comes in two severities:

  • Warning, when everything behind the dot is an optional broken rule, meaning one defined at SHOULD criticality.
  • Error, for anything else: a broken MUST rule, a failed validation, or a value that is neither confirmed nor confident.

Where a closed group or instance hides issues of both severities, the dot shows the error.

Selections from outside the field list

A value can be selected without going through the field list at all:

  • From the Business checks panel.
  • From the fields listed for a token selected in the document.
  • By keyboard.

Any of those selections opens every field group and instance the value sits inside, so a selection never lands somewhere out of sight.

A field group with nothing extracted

A field group with no instances has nothing to hide, and its header shows no count. The chevron is still there and still changes state, but nothing below it moves: the missing-value placeholder stays visible either way.

Confirming and submitting with groups collapsed

Collapsing changes which values are shown, not which values are processed.

Important:

Confirming all values and submitting the action both cover every field, including the fields inside closed groups and instances. The counts shown before submitting are calculated over the whole document type, not over what the list happens to show.

Where the collapse state is kept

The field list opens with every field group and every instance expanded.

After that, the choices last only as long as the same document type stays selected:

  • Switching to another document type expands everything again, and switching back does not restore the earlier choices.
  • Reloading the page expands everything again.
  • Nothing is stored in the browser, so the choices do not carry to another session, another device, or another reviewer working on the same action.

Field filters behave differently: they are kept in the browser per document type and survive a reload. See field filters.

Availability

Collapsing is available in Automation Cloud, in the compact view of the Validation Station. The view an action opens in comes from the DisplayMode property of the Create Document Validation Action activity.

Field groups themselves are supported in the compact view only, so the classic view is unaffected.

Was this page helpful?

Connect

Need help? Support

Want to learn? UiPath Academy

Have questions? UiPath Forum

Stay updated