Signature Document - Registrant Phone Number Attribute Displays JSON Data

[tpcc-myles]

Description

When completing an event registration that contains a phone number registrant attribute, the phone number will print to the signature document as JSON data.

This behavior was discovered in our sandbox environment, running Rock v16.8. It was reproduced in the Rock Demo site that currently runs v16.9.

This issue appears to be directly related to #6067 though it occurs in a different part of the system (signature document creation vs workflow entry)

Actual Behavior

When the signature document for the registration is presented - as well as after it is signed and saved - any phone number registrant attribute printed to the sig doc displays as JSON data.

Expected Behavior

When the signature document for the registration is presented - as well as after it is signed and saved - any phone number registrant attribute printed to the sig doc should display as a properly-formatted phone number.

Steps to Reproduce

1. Create/update an event registration to ask for a phone number on one of the registration forms. Setup the phone number as a Registrant Attribute, using the Field Type of Phone Number.

2. Create/update a signature document to pull in the phone number registrant attribute using the syntax {{ Registrant | Attribute:'PhoneNumberAttributeKey' }}.

3. Update the event registration to require the signature document.
4. Complete a registration for the event, providing a phone number in the registrant attribute created above.
5. Review the Signature Document presented on-screen to see the JSON data in place of the expected phone number.
   

Issue Confirmation

• Perform a search on the Github Issues to see if your bug or enhancement is already reported.
• Reproduced the problem on a fresh install or on the demo site.

Rock Version

16.8 & 16.9

Client Culture Setting

en-US