may 26, 20215:24 AM - editado may 26, 20215:34 AM
Miembro
eSign module not working in quote template
resolver
We are currently implementing a quote template into our workflow. The template shows up in the dropdown menu and works well apart from the esign button. This has been added as a module to the template but when selected under the signature options it does not display. We only see the label text saying "Before you sign this quote, an email must be sent to you to verify your identity. Find your profile below to request a verification email."
Looking at Google Chrome's Developer Console I can see an error message stating "Uncaught SyntaxError: Unexpected token } in JSON at position 184 at JSON.parse (<anonymous>) at quote-esignature.js:1". It further states that "DevTools failed to load SourceMap: Could not load content for https://static.hsappstatic.net/quote-esignature-js/ex/quote-esignature.js.map: HTTP error: status code 403, net::ERR_HTTP_RESPONSE_CODE_FAILURE".
The esign module has been added to the template in the following way:
I understand that some of the features developed around quotes are still in beta but was wondering if I could get some advice on any mistakes in the setup or whether there is a known bug in the esign module.
This isn't something I've specifically done, so I've just compared your code with the default e-sign section in our template, since we haven't made any changes and it does show up for us without an issue. It's just a guess, but we're using template_data in a few places where you have QUOTE_PROPS:
I tried a test quote where I changed those three calls to use QUOTE_PROPS to match yours, and my e-sign block definitely breaks, although it has different behavior than what you described.
This isn't something I've specifically done, so I've just compared your code with the default e-sign section in our template, since we haven't made any changes and it does show up for us without an issue. It's just a guess, but we're using template_data in a few places where you have QUOTE_PROPS:
I tried a test quote where I changed those three calls to use QUOTE_PROPS to match yours, and my e-sign block definitely breaks, although it has different behavior than what you described.