Idea ID 2783857
Use REST tokenDestinations again
Status:
Waiting for Votes
Submitted by
martin_mortense n
on
2018-12-11
09:57


Make SSPR use the REST tokenDestinations data even if the user does not have phone/email attributes.
Background: (SR #101204053351)
in SSPR 4.3 The REST Client tokenDestinations can ask for new email and phone for a user, but it will only ask if the user already has an existing phone attribute or email attribute, so if these attributes does not exist it will not use the new data from the REST client.
This was not the case in SSPR 4.2 with the combined sms/email method.
Background: (SR #101204053351)
in SSPR 4.3 The REST Client tokenDestinations can ask for new email and phone for a user, but it will only ask if the user already has an existing phone attribute or email attribute, so if these attributes does not exist it will not use the new data from the REST client.
This was not the case in SSPR 4.2 with the combined sms/email method.
Labels
- Labels:
-
Integrations
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.