You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
« Previous
Version 6
Next »
Product release notes
Sprints | Teams | Modules | Product features |
---|
S1 | TnG | Mob | |
S1 | TnG | Mob | Secret code to enable/disable screenshot and screen recording protection https://jira.secutix.com/browse/TIX2-772 [FIFASTX-3186] As FIFA organizer, I know a secret code to enable/disable screenshot and screen recording. - In the way to have easier operations & troubleshooting, allow the organizer staff to enable/disable the new feature Screenshot and screen recording protection https://jira.secutix.com/browse/TIX2-2 Screenshot and screen recording protection.
- New application setting keys in AdminTool "Protect screenshot and screen recording", by default is TRUE, as well as "Secret code to change in-app the protect screenshot and screen recording setting", by default is 159874.
- If the value is TRUE, then the feature in https://jira.secutix.com/browse/TIX2-2 is enabled (i.e. use the ScreenShieldKit SDK). If the value is FALSE, the protection is not used at all (i.e. the ScreenShieldKit SDK is not used at all) and screenshot and screen recording can be taken with QR code without any protection (i.e. extra layer displayed). However:
- If the user triple taps on the bottom of the home screen where all the version of the app, model of the phone (i.e. a similar procedure than the manual activation of the ticket, but in a different location on the screen), the user can enter the secret code to change the current screenshot and screenshot protection setting (TRUE/FALSE) for this Mobile AppID.
- Login out/in keep the setting. Reinstalling the app remove the setting.
- These new application setting keys in AdminTool "Protect screenshot and screen recording" and "Secret code to change in-app the protect screenshot and screen recording setting" will impact both iOS and Android, and no build app would be needed.
![](/download/thumbnails/145887462/image2022-8-25_17-49-33.png?version=2&modificationDate=1662041451808&api=v2) ![](/download/thumbnails/145887462/image2022-8-25_17-50-11.png?version=2&modificationDate=1662041485938&api=v2) ![](/download/thumbnails/145887462/image2022-8-25_17-55-11.png?version=2&modificationDate=1662041517217&api=v2) ![](/download/thumbnails/145887462/image2022-8-25_17-53-32.png?version=2&modificationDate=1662041562401&api=v2) ![](/download/thumbnails/145887462/image2022-8-25_17-54-9.png?version=2&modificationDate=1662041594667&api=v2) ![](/download/thumbnails/145887462/image2022-8-25_17-54-38.png?version=2&modificationDate=1662041632116&api=v2) ![](/download/thumbnails/145887462/image2022-8-25_17-55-46.png?version=2&modificationDate=1662041660689&api=v2)
|
S1 | TnG | BO | Transfer a ticket on the AdminTool 2.0 https://jira.secutix.com/browse/TIX2-537 As an organizer, I want to be able to transfer spectators ticket to another email address. - AdminTool user (admin-user - AU and support-user SU, but not basic-user BU) can trigger a transfer of the ticket to another email address
- The ticket can be transferred regardless of transfer rules
- The organizer must provide a reason (mandatory, free text)
- This transfer reason will be displayed in the Additional information of the Ticket history log with format: Admin Tool transfer: <transfer reason free text>
![screenshot-1.png](https://jira.secutix.com/secure/attachment/278229/278229_screenshot-1.png)
- The BE shall log the ticket status as a normal transfer (with a reason of course)
- The ticket cannot be transferred if it is controlled or the event is expired
- Deleted ticket shouldn't be transferred => Hide send button
![](/download/thumbnails/145887462/image2022-8-25_18-10-41.png?version=2&modificationDate=1662041896801&api=v2) ![](/download/thumbnails/145887462/image2022-8-25_18-11-15.png?version=2&modificationDate=1662041943681&api=v2)
|
|
|
|
|
|
|
|
|