Difference between revisions of "Required fields validation on Inline Detail Form"
(→Problem Description) |
(→Problem Description) |
||
| Line 1: | Line 1: | ||
[[Category:FAQ]] | [[Category:FAQ]] | ||
===Problem Description=== | ===Problem Description=== | ||
| − | Mandatory fields are not validated on inline forms which are not visible. For example fields on First Task tab on WO details are not validated | + | Mandatory fields are not validated on inline forms which are not visible. For example fields on First Task tab on WO details are not validated when other than First Task tab is active. This behaviour is related to '''Mandatory''' switch on form design and '''Is Required Expression'''. Validation embeded in code is validated always regardless of visibility on form. |
Decision if particular element is required or not is evaluated in code. It is evaluated in same code responsible for rendering form. Inline Detail form is rendered only when it is visible. In current rendering mechanism it is very difficult to safety separate code responsible for validation fields. Enabling rendering hidden inline forms (always regardless of visibility) can affect performance. | Decision if particular element is required or not is evaluated in code. It is evaluated in same code responsible for rendering form. Inline Detail form is rendered only when it is visible. In current rendering mechanism it is very difficult to safety separate code responsible for validation fields. Enabling rendering hidden inline forms (always regardless of visibility) can affect performance. | ||
Revision as of 14:12, 20 December 2016
Problem Description
Mandatory fields are not validated on inline forms which are not visible. For example fields on First Task tab on WO details are not validated when other than First Task tab is active. This behaviour is related to Mandatory switch on form design and Is Required Expression. Validation embeded in code is validated always regardless of visibility on form. Decision if particular element is required or not is evaluated in code. It is evaluated in same code responsible for rendering form. Inline Detail form is rendered only when it is visible. In current rendering mechanism it is very difficult to safety separate code responsible for validation fields. Enabling rendering hidden inline forms (always regardless of visibility) can affect performance.
Workaround
Possible workaround (without code change) is to use generic validation (defined in business rules).
Example
Fields ItemID & Quantity are mandatory in planned materials (Work Order -> First Task -> Planned Materials).
Business rules validation definition (System Configuration->System Data->Business Rules->DataBO.ProcessMngt.JobBO->Validation Rules)
