Conversation
…move Fields shown only when a parent FieldValue is selected could not be reordered in the form preview - drag-and-drop and the move buttons were disabled for any field with a parentFieldValue. Fields can now be moved like any other field. Moving a field (via drag-and-drop or the move buttons) past a step boundary now reassigns the field's step to match its new position, so it actually becomes part of that step instead of only changing its visual position while keeping the old step reference. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Empty steps were skipped entirely in the preview. Every configured DynamicFormStep is now always rendered with its heading; steps with no visible fields show an empty-state placeholder row, which also accepts drag-and-drop to assign a field into that step. Move Up/Down at a step boundary now first only reassigns the field to the neighboring step while keeping its relative order; a further click then reorders it within that step. Regular drag-and-drop onto an existing field keeps its previous immediate reposition-and-reassign behavior. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Document DynamicFormStep (missing from the data model tables), the interactive Backoffice form preview renderer with its drag-and-drop and step-boundary behavior, and the recent wizard refinements. Also fixes a stale relation/typecode row that no longer matches items.xml. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
- DynamicFormField editor: new "Visibility" tab grouping hidden and
parentFieldValue (with an explanatory description), separate from
the Step tab.
- DynamicForm creation wizard: drop the Steps/Fields wizard pages -
their part-of collections cannot be created before the form itself
is persisted, so they only ever failed there; both remain fully
editable from the form editor afterwards.
- Fix the DynamicFormField wizard's step reference restriction: the
editor-parameter belongs in the wz: namespace (not editorArea:)
when nested in a wz:property, and the templating placeholder is
always {parentObject.<attr>} regardless of the wizard's own
property-list root name.
- Hide id (UUID-prefilled) in the DynamicFormStep and
DynamicFormFieldValue wizards too.
- FormFieldType/FormType wizards: add the icon field inherited from
EnumerationValue.
- Rename the Form/Field reference list columns and reorder the
DynamicFormStep list view.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
The preview's inline styles used fixed hex colors, so the rendered form preview would not adapt to a non-default Backoffice theme. Every color now references the semantically closest --bo-*/--sap* theming variable (container background/border, list row divider, required marker, secondary label text, step heading) instead. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
- Derive the explorer tree's level-shading colors from the active Backoffice theme (--bo-container-background mixed with --bo-highlight-color per level via color-mix()) instead of fixed hex values, so they adapt to non-default/dark themes. - Also register the tree node icon for the side navigation rail (.yw-treeCellInner), a separate widget from the expanded explorer tree (div.yw-explorerTree) that was missing the icon when the navigation panel is collapsed. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Introduces a new custom extension providing configurable, multi-step form definitions with Backoffice administration, a service/facade layer, and an OCC API.
Data model
Backoffice administration
OCC API
Form submissions
Other