Openbravo Issue Tracking System - POS2 |
View Issue Details |
|
ID | Project | Category | View Status | Date Submitted | Last Update |
0052242 | POS2 | POS | public | 2023-04-25 16:23 | 2023-05-24 16:11 |
|
Reporter | jayala | |
Assigned To | jayala | |
Priority | normal | Severity | trivial | Reproducibility | have not tried |
Status | closed | Resolution | fixed | |
Platform | | OS | 5 | OS Version | |
Product Version | | |
Target Version | 23Q2.1 | Fixed in Version | 23Q2.1 | |
Merge Request Status | approved |
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 | 0052242: Open order in the most adecuated schema |
Description | When an order which has a schemaId information is loaded, POS should be able to load it automatically opening the linked schema. |
Steps To Reproduce | 1. Search for a ticket which has the field "obpos2OrgSchema" filled.
2. Open the order.
3. See that order is opened but not in the schema indicated for the order. |
Proposed Solution | We will decide which schema will be selected in the POS based on the following conditions:
1. Use the schema provided by the order in case it's available in the POS and compatible with the loaded order.
2. Use the schema which currently is being used in POS in case it's available in the POS and compatible with the loaded order.
3. Use the default schema defined for the POS in case it's available in the POS and compatible with the loaded order.
*. If none of the schemas installed on the POS are compatible with the current order then a warning will be shown and the order will be opened using the default schema. |
Additional Information | |
Tags | No tags attached. |
Relationships | blocks | feature request | 0052231 | | closed | jayala | Open order in the most adecuated schema |
|
Attached Files | |
|
Issue History |
Date Modified | Username | Field | Change |
2023-04-26 10:55 | jayala | Type | feature request => backport |
2023-04-26 10:55 | jayala | Target Version | => 23Q2 |
2023-04-26 10:55 | jayala | Assigned To | Retail => jayala |
2023-05-02 14:50 | guilleaer | Target Version | 23Q2 => 23Q2.1 |
2023-05-09 10:57 | hgbot | Merge Request Status | => open |
2023-05-09 10:57 | hgbot | Note Added: 0149481 | |
2023-05-10 09:33 | hgbot | Note Added: 0149540 | |
2023-05-11 10:37 | hgbot | Note Added: 0149600 | |
2023-05-11 11:11 | hgbot | Merge Request Status | open => approved |
2023-05-11 11:11 | hgbot | Resolution | open => fixed |
2023-05-11 11:11 | hgbot | Status | scheduled => closed |
2023-05-11 11:11 | hgbot | Note Added: 0149610 | |
2023-05-11 11:11 | hgbot | Fixed in Version | => 23Q2.1 |
2023-05-11 11:11 | hgbot | Note Added: 0149611 | |
2023-05-24 16:11 | hgbot | Note Added: 0150234 | |
Notes |
|
(0149481)
|
hgbot
|
2023-05-09 10:57
|
|
|
|
(0149540)
|
hgbot
|
2023-05-10 09:33
|
|
|
|
(0149600)
|
hgbot
|
2023-05-11 10:37
|
|
|
|
(0149610)
|
hgbot
|
2023-05-11 11:11
|
|
|
|
(0149611)
|
hgbot
|
2023-05-11 11:11
|
|
|
|
(0150234)
|
hgbot
|
2023-05-24 16:11
|
|
|