Ops & Safety (formerly AM)

Problem: Some fields overflow compact layouts. Actionables: Add width presets (S/M/L/Full) and custom width (%) per field. Allow max-height for dropdown/pickers with scroll. Provide grid guidelines in builder. Success criteria: Fields resp...

Problem: Deleting a mistaken field redirects to root; changing type not possible. Actionable: Remove redirect; stay on same form and scroll position after delete. Add “Change Field Type” with compatibility checks and warnings. Add “Undo” sna...

Problem: Recreating similar structures is time-consuming. Actionables: Add “Duplicate Field” and “Duplicate Group” actions. Auto-generate unique IDs and detach data bindings safely. Include/option to duplicate rules, validations, visibility ...

Problem: Can’t render a full row of 10 options. Actionables: Update max column setting to allow 7–10. Ensure responsive wrapping rules for small screens. Add visual preview in builder for 1–10 columns. Validate accessibility: minimum touch...

Change default behaviour for new Composite items Request: When a new composite item is added to a Composite group, it should be Disabled/Unselected by default. Reason: Currently, new composite items are enabled by default and propagate into al...

We’re hitting structural limits in Composite Work Practices that force workarounds and prevent accurate modelling of real operations. Current constraints Only two Composite Work Practice Groups. Each group supports a maximum of three sub-items...

Introduce a self-customization feature (using simple AND/OR/IF logic) that lets admins build pairing rules such as: A Co-pilot with fewer than 500 total flight hours must not be paired with a Captain who has both fewer than 2,000 total flight hour...

Consider adding a self-customization rules feature (using simple AND/OR/IF logic) so admins can create pairing rules such as: Pairing restriction: Do not pair a Captain (PIC) who has both fewer than 50 PIC hours on type and fewer than 500 total ho...

Introduce a no‑code self‑customisation feature (using simple AND/OR and IF logic) so admins can define pairing rules. One required rule: Pairing constraint: A PIC and Co‑pilot may only be paired if at least one crew member is familiar with the are...

Introduce a self-customization rules feature (using simple AND/OR and IF logic) so admins can configure operational policies directly. For this policy: Policy: In commercial air transport, a pilot (PIC or Co‑pilot) may not operate an aircraft ty...