Actions
Bug #9995
open
Task #11611: Issues identified in Product-UEM 6.2.0 testing process
Caching when sending messages/ device lock in Device Operations
Status:
New
Priority:
High
Assignee:
-
Start date:
13/03/2023
Due date:
% Done:
0%
Estimated time:
CallRef:
Description
Environment details
513 server
Prerequisites
enroll a device
Steps
go to device.
send a normal message.
then send a prioritized message.
again send a normal message.
Description
after sending a prioritized message and after that, sending a normal message the payload is still sending the isPrioritizedMessage:true. so when sending a normal message it automatically transform to prioritized message.
Note: This also happens in device lock(and hard lock enabled)
Result
sending a normal message before sending a prioritized message [1].
sending a prioritized message [2].
sending a normal message after prioritized message [3].
[1] ![[1]](/attachments/download/3068/unnamed%20(1).png "[1]")
[2]![[2]](/attachments/download/3069/unnamed%202.png "[2]")
[3]![[3]](/attachments/download/3070/unnamed%203.png "[3]")
Files
| unnamed (1).png (86.6 KB) unnamed (1).png | [1] | ||
| unnamed 2.png (100 KB) unnamed 2.png | [2] | ||
| unnamed 3.png (104 KB) unnamed 3.png | [3] |
Updated by Viranga Gunarathna over 2 years ago
- Project changed from product-uem 5.3.0 GA to 32
Updated by Viranga Gunarathna over 1 year ago
- Project changed from 33 to Backlog
Updated by Arshana Atapattu over 1 year ago
- Subject changed from Caching when sending messages in Device Operations to Caching when sending messages/ device lock in Device Operations
- Description updated (diff)
- Priority changed from Medium to High
Updated by
Updated by Lasantha Dharmakeerthi over 1 year ago
- Project changed from Backlog to product-uem 6.2.0 GA
Updated by Lasantha Dharmakeerthi over 1 year ago
- Project changed from product-uem 6.2.0 GA to product-uem 6.3.0 GA
Actions