Creating and editing

Create and edit workflows let users add new records or update existing ones when the record type and permissions allow it. Forms show the fields that matter for the current workflow, including required values and read-only values.

Dependent reference fields

Some reference fields depend on values selected earlier in the form. For example, a work item’s Type can determine which records are valid choices for Parent.

• Choose the driver value first. The dependent list or picker remains disabled until every required driver has a value.
• When the dependent control becomes available, it shows only candidates that satisfy the configured Reference Eligibility rule. A Lookup can still show hierarchy ancestors for navigation, but navigation-only rows cannot be selected.
• Changing a driver clears the dependent value and any values that depend on it, even if the previous choice might still be valid. Select those values again from the newly filtered candidates.
• The same rule is checked when the record is saved through the WebApp or API. If another change made the selection invalid after it was chosen, Moltaro rejects the field value. Reload the current data, review the driver, and select an eligible value.

If saving fails, Moltaro should point to the value or rule that needs attention. After saving, the record appears with its updated display values, history, and related context according to the screen that opened the form.

Some edit forms also contain a child-record table. Its child operations commit independently and are not undone by Cancel on the parent form. Read Related tables in forms before using Add, Archive, or Delete there.

Choosing a value through a hierarchy

Some Reference fields open a Hierarchy Selector instead of one flat list. The dialog can show a fixed path, such as Country, Region, and City, or append levels as you follow a recursive structure such as Work Item Parent.

• Choose one value at each level. Changing an earlier level removes all later choices because they no longer belong to the same branch.
• Navigation-only or ineligible rows can remain available for opening an accessible child level, but they cannot be confirmed as the final value.
• Confirm stores only the final record. Clear removes that one value, and Cancel keeps the value that was present when the dialog opened.
• Opening an existing value reconstructs its readable breadcrumb chain. If a saved value is now ineligible, you can still clear or replace it when you are allowed to read it.

The selector does not add hidden helper values to the record. Read more about the two source modes and their limits in Hierarchy Selector configuration.