Openbravo Issue Tracking System - Retail Modules |
| View Issue Details |
|
| ID | Project | Category | View Status | Date Submitted | Last Update |
| 0051996 | Retail Modules | Events for Client | public | 2023-03-28 13:03 | 2023-05-09 13:06 |
|
| Reporter | ander_flores | |
| Assigned To | Triage Platform Conn | |
| Priority | normal | Severity | minor | Reproducibility | always |
| Status | closed | Resolution | fixed | |
| Platform | | OS | 5 | OS Version | |
| Product Version | | |
| Target Version | | Fixed in Version | | |
| 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 | 0051996: Messages field only show 1st item of the array |
| Description | Messages of type DISPLAY, MENU, KEY, STRING and APPROVAL have a messages field that is used to enter the messages to be displayed. This field is an array, with each of these messages. The problem is that only the first one is shown.
|
| Steps To Reproduce | There is no current example of a Message that has more than one element on the messages field.
To reproduce it just change the code of a message adding an extra element on the messages field
Example:
this.sendMessage({
messageType: 'DISPLAY',
messages: ['New Message', 'Original Message']
});
Only the New Message should show up |
| Proposed Solution | |
| Additional Information | |
| Tags | No tags attached. |
| Relationships | |
| Attached Files | |
|
| Issue History |
| Date Modified | Username | Field | Change |
| 2023-03-28 13:03 | ander_flores | New Issue | |
| 2023-03-28 13:03 | ander_flores | Assigned To | => Triage Platform Conn |
| 2023-03-28 13:03 | ander_flores | OBNetwork customer | => No |
| 2023-03-28 13:03 | ander_flores | Triggers an Emergency Pack | => No |
| 2023-04-25 13:36 | hgbot | Merge Request Status | => open |
| 2023-04-25 13:36 | hgbot | Note Added: 0148848 | |
| 2023-04-25 14:04 | hgbot | Note Added: 0148857 | |
| 2023-05-05 09:30 | hgbot | Merge Request Status | open => merged |
| 2023-05-05 09:30 | hgbot | Note Added: 0149328 | |
| 2023-05-05 09:30 | hgbot | Resolution | open => fixed |
| 2023-05-05 09:30 | hgbot | Status | new => resolved |
| 2023-05-05 09:30 | hgbot | Note Added: 0149329 | |
| 2023-05-05 09:57 | hgbot | Merge Request Status | merged => approved |
| 2023-05-05 09:58 | hgbot | Status | resolved => closed |
| 2023-05-05 09:58 | hgbot | Fixed in Version | => 23Q3 |
| 2023-05-05 09:58 | hgbot | Note Added: 0149332 | |
| 2023-05-05 09:58 | hgbot | Note Added: 0149333 | |
| 2023-05-05 12:07 | hgbot | Note Added: 0149354 | |
| 2023-05-09 13:06 | hgbot | Note Added: 0149489 | |
|
Notes |
|
|
(0148848)
|
|
hgbot
|
|
2023-04-25 13:36
|
|
|
|
|
(0148857)
|
|
hgbot
|
|
2023-04-25 14:04
|
|
|
|
|
(0149328)
|
|
hgbot
|
|
2023-05-05 09:30
|
|
|
|
|
(0149329)
|
|
hgbot
|
|
2023-05-05 09:30
|
|
|
|
|
(0149332)
|
|
hgbot
|
|
2023-05-05 09:58
|
|
|
|
|
(0149333)
|
|
hgbot
|
|
2023-05-05 09:58
|
|
|
|
|
(0149354)
|
|
hgbot
|
|
2023-05-05 12:07
|
|
|
|
|
(0149489)
|
|
hgbot
|
|
2023-05-09 13:06
|
|
|