Project:
View Issue Details[ Jump to Notes ] | [ Issue History ] [ Print ] | |||||||
ID | ||||||||
0054280 | ||||||||
Type | Category | Severity | Reproducibility | Date Submitted | Last Update | |||
defect | [Retail Modules] Events for Client | major | always | 2024-01-09 18:50 | 2025-03-27 14:50 | |||
Reporter | charlotte_vasseur | View Status | public | |||||
Assigned To | Triage Platform Conn | |||||||
Priority | normal | Resolution | open | Fixed in Version | ||||
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 | |||||||
Merge Request Status | ||||||||
Review Assigned To | ||||||||
OBNetwork customer | No | |||||||
Support ticket | ||||||||
Regression level | ||||||||
Regression date | ||||||||
Regression introduced in release | ||||||||
Regression introduced by commit | ||||||||
Triggers an Emergency Pack | No | |||||||
Summary | 0054280: inputsAndApprovals: user Name is send in approvedBy in the external system | |||||||
Description | With an external system and event subscription configured, when doing an action on POS that requires an approval: the name of the user that approves is sent in the JSON in the external system This is not compliant regarding GDPR, maybe we should send Username instead of the Name of the user | |||||||
Steps To Reproduce | In BO: - Configure an external system (see "BO Config External System.png") - Configure an event subscription with the previous external system (see "BO Config Event Subscription.png") - Configure an EDL Configuration (see "BO EDL Configuration.png") - Configure a role that requires approval for a user action (ex: 'Return Line' for role 'VallBlancaUser' - see "Role ApprovalRequired.png") - Configure another role that can approve the previous user action (ex: 'Return Line' for role 'The White Valley Group Admin' - see "Role CanApprove.png") - Configure a different Name and Username for the user that can approve (see "User Name.png") In POS, login with the user that has the role that cannot approve (ex: vallblanca/openbravo) Do the action that requires approval (ex: add the product and select 'Return Line' on it) Enter the credentials of the user that can approve previously configured (ex: Openbravo/openbravo) See "POS Approval.png" Finalize the ticket Go to the external system and check the JSON sent => The Name of the user is present in the fields 'approvedBy' See "JSON external system.png" | |||||||
Tags | No tags attached. | |||||||
Attached Files | ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() | |||||||
![]() |
|
![]() |
|
(0177639) shuehner (administrator) 2025-03-27 14:50 |
Issue exported to Jira: https://openbravo.atlassian.net/browse/RM-9228 [^] |
![]() |
|||
Date Modified | Username | Field | Change |
2024-01-09 18:50 | charlotte_vasseur | New Issue | |
2024-01-09 18:50 | charlotte_vasseur | Assigned To | => Triage Platform Conn |
2024-01-09 18:50 | charlotte_vasseur | File Added: BO Config External System.png | |
2024-01-09 18:50 | charlotte_vasseur | Triggers an Emergency Pack | => No |
2024-01-09 18:51 | charlotte_vasseur | File Added: BO Config Event Subscription.png | |
2024-01-09 18:51 | charlotte_vasseur | File Added: BO EDL Configuration.png | |
2024-01-09 18:51 | charlotte_vasseur | File Added: Role ApprovalRequired.png | |
2024-01-09 18:51 | charlotte_vasseur | File Added: Role CanApprove.png | |
2024-01-09 18:51 | charlotte_vasseur | File Added: User Name.png | |
2024-01-09 18:51 | charlotte_vasseur | File Added: POS Approval.png | |
2024-01-09 18:51 | charlotte_vasseur | File Added: JSON external system.png | |
2025-03-27 14:50 | shuehner | Note Added: 0177639 | |
2025-03-27 14:50 | shuehner | Status | new => closed |
Copyright © 2000 - 2009 MantisBT Group |