Explore apps for invoice automationIntegrate CRM with CLM solutions
Help & Support
Elevate Your Agents with AgentExchange Solutions
Easily enhance Agentforce with pre-built AI solutions from AgentExchange. Browse, install, and deploy agents, actions, and apps directly into your environment. Tell Me More
Have Questions?
BrightSIGN
Capture signatures from the browser and save as attachments or files
- Business Need
- Productivity
- Requires
- Platform Cloud
- Compatible With
- Sales CloudService CloudPlatform Cloud
Signature Capture is now BrightSIGN BrightSIGN is a Lightning Component that allows signing via a browser or mobile device and stores the captured signature as a Salesforce attachment or Salesforce file (Salesforce files added in July 2017 update).
Rating
Reputation
MVP
Recognized by Salesforce for their leadership, expertise, and generosity
Top Reviewer
Contribute reviews that encourage conversation and help others make informed decisions
Ranger
Lifelong learners who have earned the Ranger rank or higher on Trailhead
Showing 10 of 25 Reviews
Worked perfectly
Easy to use, works perfectly for me. Quick question - How can a validate the signature is populated and saved in a screen flow?
I created a Get Records component after the signature screen, to find an Attachment with the name I assigned, related to the Account. Then I had a Decision element to assess whether the Get Records element found anything. If it did not, it returns to the signature screen which now has an error message displayed thanks to Component Visibility settings.
Great tool!
I use your signature tool inside Screen Flow, is there a way to oblige the user to sign? Make the signature a mandatory field?
I created a Get Records component after the signature screen, to find an Attachment with the name I assigned, related to the Account. Then I had a Decision element to assess whether the Get Records element found anything. If it did not, it returns to the signature screen which now has an error message displayed thanks to Component Visibility settings.
Great component
Exactly what I expected : easy to setup and to use on lightning pages or as a screen flow element, this component totally filled my needs.
Exceptional component
Thank you for developing such an exceptional component. It's incredibly intuitive, highly useful, and the extensive content you've generously provided supports various additional use cases wonderfully. A couple of questions: 1. Any guidance on what this error that appears on mobile when saving a signature is? Uncaught Error in $A.getCallback() [self.toggleClass is not a function] Callback failed: apex://BGSIGCAP.SignatureCaptureCont roller/ACTION$SaveSignatureFile 2. The saved files have thier sharing default to Customer Access - Enabled / Set by Record. Is there a way to disable that? Thanks a lot!
1. This sounds like you are on an old version of the component. Salesforce made a change to how the lightning container functions which caused me some callback issues. I'd recommend upgrading to the latest version. 2. The sharing on the File is inherited from the linked record - if you can tell me what you'd like it to do I can take a look.
Simple yet amazing
The setup is super simple, the function is excellent. The only issue I found is when using it in a community with guest users. I have a flow running on sys context to allow users to update a public record but the user must sign. Unfortunately, I haven't been able to get it to work. If someone know how to, it would be amazing
Perfect
Works perfectly, intuitive.
Makes Signature Capture Easy
This elegant solution can be easily added as a button or within the record page of choice. With just a few clicks it was setup and tested. Pleasantly surprised it was so easy!
Works like a Charm!
The solution is built on using native HTML and it is an ideal solution to showcase how easily one can build a native app exchange app using standard HTML and Salesforce native technologies. I love it.
Awesome Product!
This is great for a simple sign on a lightning record page! only wish I could have two different signatures named separate names! Great easy solution!
Well done
Easy to set-up.
Nice solution@Kristen. If you are sticking with standard flow functionality that's pretty much the only approach - check afterwards to see if what you are expecting to be present is indeed present. If you have Lightning component developer skills to hand, you can go a slightly different route and not let the user move off the page until they have provided a signature. I wrote a blog on this a while back with some sample code - essentially the user is stuck on the page until they save a signature, and when that happens they are automatically navigated to the next page. You can find more details at : https://bobbuzzard.blogspot.com/2019/10/auto-completing-signature-capture-flow.html