0017068: Validation pattern - Openbravo Issue Tracking System

Openbravo Issue Tracking System - Openbravo ERP

View Issue Details

Project

Category

View Status

Date Submitted

Last Update

0017068

Openbravo ERP

A. Platform

public

2011-05-09 12:55

2022-02-01 08:08

Reporter

alostale

Assigned To

Triage Platform Base

Priority

normal

Severity

minor

Reproducibility

N/A

Status

new

Resolution

open

Platform

OS Version

Product Version

Target Version

Fixed in Version

Merge Request Status

Review Assigned To

OBNetwork customer

Web browser

Modules

Core

Support ticket

Regression level

Regression date

Regression introduced in release

Regression introduced by commit

Triggers an Emergency Pack

Summary

0017068: Validation pattern

Description

Complex configurations cannot be validated on the fly because while configuring the status is not valid.

For example:
-AD. In 2.50 this is solved when compiling by WAD Validation. In 3.0 this doesn't make sense as it shouldn't be needed to compile after AD modifications.
-Account configuration

Steps To Reproduce

Proposed Solution

There should be a generic validation pattern visible somewhere in the application (top navigation bar?).

Modules could define validations. A validation is defined by:
-Entities to validate. When any of these entities is modified, the validation status is "to be validated".
-Validation process. Is the process that does the verifications and changes the status to "Successfully Validated" or "Validated with errors"

Additional Information