Anonymous | Login

Project:

News | My View | View Issues | Roadmap | Summary

View Issue Details[ Jump to Notes ]

[ Issue History ] [ Print ]

ID

0057838

Type

Category

Severity

Reproducibility

Date Submitted

Last Update

defect

[POS2] POS

minor

always

2025-02-03 11:08

2025-02-13 13:08

Reporter

jinigo

View Status

public

Assigned To

NaroaIriarte

Priority

normal

Resolution

fixed

Fixed in Version

25Q2

Status

closed

Fix in branch

Fixed in SCM revision

Projection

none

ETA

none

Target Version

OS

Any

Database

Any

Java version

OS Version

Database version

Ant version

Product Version

SCM revision

Review Assigned To

Regression level

Regression date

Regression introduced in release

Regression introduced by commit

Triggers an Emergency Pack

No

Summary

0057838: [25Q1] Postal Code Validation Not Applied

Description

When postcode validation is configured in CRM Connector Configuration, the system allows saving and assigning a customer without a postcode, without displaying any error message.

Steps To Reproduce

In the Backoffice:
1. Go to 'CRM Connector Configuration' window
2. Proceed to 'API Property for Address' tab
3. Open 'postalCode' property (required field in POS)
4. Proceed to 'Validations and Notifications' section
5. Set Validation = Informative and Validation type = Empty
6. Remove postal code ('Location/Address' tab → 'Location address' field of 'Business Partner' window) for the selected Customer

7. Login to POS2
8. Push 'VBS Customer' button
9. Search for Customer
10. A dialog is shown, click 'Yes, Fix Data' button
11. Go to Manage Address(es)
12. Select the address
13. Push 'Save' button

Expected results: 'Postal code' is a highlighted field and it is not possible to save until 'Postal code' field is completed

Actual results: 'Postal code' is not highlighted and it is possible to save.

Tags

No tags attached.

Relationships [ Relation Graph ] [ Dependency Graph ]

related to

design defect

resolved

The code that validates the CRM configuration properties, should be refectored

Notes
(0175472) hgbot (developer) 2025-02-11 11:46	Merge Request created: https://gitlab.com/orisha-group/bu-commerce/openbravo/product/pmods/org.openbravo.pos2/-/merge_requests/3481 [^]

(0175595) hgbot (developer) 2025-02-13 13:08	Merge request merged: https://gitlab.com/orisha-group/bu-commerce/openbravo/product/pmods/org.openbravo.pos2/-/merge_requests/3481 [^]

(0175596) hgbot (developer) 2025-02-13 13:08	Directly closing issue as related merge request is already approved. Repository: https://gitlab.com/orisha-group/bu-commerce/openbravo/product/pmods/org.openbravo.pos2 [^] Changeset: 3b2262b025981f97f0e6f6b8febd2ea2abf94860 Author: Naroa Iriarte <n.iriarte@orisha.com> Date: 13-02-2025 12:08:45 URL: https://gitlab.com/orisha-group/bu-commerce/openbravo/product/pmods/org.openbravo.pos2/-/commit/3b2262b025981f97f0e6f6b8febd2ea2abf94860 [^] fixed ISSUE-57838: CRM entity validations now works for addresses --- M web-jspack/org.openbravo.pos2/src/components/Customer/CustomerUtils/CustomerFormHandlerUtils.js ---

Issue History
Date Modified	Username	Field	Change
2025-02-03 11:08	jinigo	New Issue
2025-02-03 11:08	jinigo	Assigned To	=> Retail
2025-02-03 11:08	jinigo	Triggers an Emergency Pack	=> No
2025-02-03 11:46	jinigo	Steps to Reproduce Updated	View Revisions
2025-02-03 13:46	guillermogil	Assigned To	Retail => guilleaer
2025-02-09 17:32	guilleaer	Assigned To	guilleaer => NaroaIriarte
2025-02-09 17:32	guilleaer	Status	new => acknowledged
2025-02-11 11:46	hgbot	Note Added: 0175472
2025-02-13 12:44	guilleaer	Status	acknowledged => scheduled
2025-02-13 13:08	hgbot	Note Added: 0175595
2025-02-13 13:08	hgbot	Resolution	open => fixed
2025-02-13 13:08	hgbot	Status	scheduled => closed
2025-02-13 13:08	hgbot	Fixed in Version	=> 25Q2
2025-02-13 13:08	hgbot	Note Added: 0175596
2025-02-14 10:50	NaroaIriarte	Relationship added	related to 0057989

Copyright © 2000 - 2009 MantisBT Group