[ENHANCEMENT]: Add Packaging Support for Custom Validation Rules in JCB #1273

New Issue

Closed

opened 2025-12-03 15:07:41 +00:00 by Lemuel · 0 comments

Lemuel commented

2025-12-03 15:07:41 +00:00

Owner

Enhancement Details

In JCB, developers can define custom validation rules in the Validation Area and assign these rules to fields to control how input data is validated.

At present, custom validation rules are not included by the JCB packaging engine when a component is built and pushed out to a repository.

This causes the following issue:

Fields may reference validation rules that do not ship with JCB by default.
If these rules were created by the developer (custom rules), they are not packaged or deployed.
When the component is initialized on a different system, those rules do not exist.
As a result, the associated fields break or silently stop validating input correctly.

Currently, the packaging engine does not package developer-defined validation rules.

This enhancement proposes that the packaging engine should:

Detect custom validation rules used by fields.
Register them as dependencies.
Ship them with the package.
Restore them when the component is initialized on another system.

This would ensure complete portability of components and guarantee that field validation behaves identically across systems.

Which part of the extension will be affected by this enhancement?

Validation Rule(admin_view), Validation Rules(admin_views)

Additional Context

Work on this feature is already in progress.

Support for shipping custom validation rules will be included in an upcoming JCB release, ensuring validation integrity and component portability across systems.

### Enhancement Details In JCB, developers can define **custom validation rules** in the Validation Area and assign these rules to fields to control how input data is validated. At present, **custom validation rules are not included by the JCB packaging engine** when a component is built and pushed out to a repository. This causes the following issue: - Fields may reference validation rules that do not ship with JCB by default. - If these rules were created by the developer (custom rules), they are **not packaged or deployed**. - When the component is initialized on a different system, those rules do not exist. - As a result, the associated fields break or silently stop validating input correctly. Currently, the packaging engine does not package **developer-defined validation rules**. This enhancement proposes that the packaging engine should: - Detect custom validation rules used by fields. - Register them as dependencies. - Ship them with the package. - Restore them when the component is initialized on another system. This would ensure complete portability of components and guarantee that field validation behaves identically across systems. ### Which part of the extension will be affected by this enhancement? Validation Rule(admin_view), Validation Rules(admin_views) ### Additional Context Work on this feature is already in progress. Support for shipping custom validation rules will be included in an **upcoming JCB release**, ensuring validation integrity and component portability across systems.