-
Notifications
You must be signed in to change notification settings - Fork 284
Feature/10350 ticketvalidation consent/10542 consent screen #3847
Feature/10350 ticketvalidation consent/10542 consent screen #3847
Conversation
…r' into feature/10350-ticketvalidation-consent/10542-consentScreen
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
UA approved
|
Hi @CV113 and @mlenkeit |
@vaubaehn the legal relationships between all involved parties for the Ticket Validation feature have carefully been reviewed by legal experts and were taken into consideration by them when the legal texts were created. 😉 |
Thank you for having a look - then I don't want to be more papal than the pope 😁 |
…r' into feature/10350-ticketvalidation-consent/10542-consentScreen # Conflicts: # src/xcode/ENA/ENA/Resources/Localization/de.lproj/Localizable.strings
…r' into feature/10350-ticketvalidation-consent/10542-consentScreen
…r' into feature/10350-ticketvalidation-consent/10542-consentScreen
…r' into feature/10350-ticketvalidation-consent/10542-consentScreen # Conflicts: # src/xcode/ENA/ENA/Resources/Localization/de.lproj/Localizable.strings
74570c5
into
feature/10350-ticketvalidation-consent/10405-coordinator
Just realized that my question was a valid one, and that there is additional information regarding the validation service, when getting a seperate consent II to submit data to the validation service. |
Description
First consent screen for ticket validation.
Link to Jira
Mainstory: https://jira-ibs.wbs.net.sap/browse/EXPOSUREAPP-10350
Subtask: https://jira-ibs.wbs.net.sap/browse/EXPOSUREAPP-10542
Screenshots