{"id":3669,"date":"2020-04-29T18:25:22","date_gmt":"2020-04-29T18:25:22","guid":{"rendered":"https:\/\/swiftcloud.ai\/support\/?p=3669"},"modified":"2020-07-02T15:38:16","modified_gmt":"2020-07-02T15:38:16","slug":"guest-user","status":"publish","type":"post","link":"https:\/\/swiftcloud.ai\/supportwebadmin\/guest-user","title":{"rendered":"Guest User (Name Missing)"},"content":{"rendered":"
Problem: We need _1_ contact to be the “master namer” at any given time. This occurs because there can be multiple people in a doc (i.e. child + parent, seller(s) + buyer(s), etc.).<\/p>\n
TL;DR Summary:<\/strong><\/p>\n Replace<\/span> the most important role’s field that starts with additional contact<\/span>, i.e. one that looks like this:<\/strong><\/p>\n With something like this: (Required 1 time per doc to auto-name)<\/strong><\/p>\n NOTE: Multiple people can fill a single role<\/strong> – example: Husband and wife selling a house may both legally be the “seller”, and legally, both may be required to sign. The additional_contact_swift_name_X (number at the end) must be different if you want them saved as separate contacts.<\/p>\n This gets a bit complex, because reality gets complex, but we can handle it all, once properly configured.<\/p>\n If you add multiple “Name both” into a doc, AND the role is the same, it will convert it to something like<\/p>\n TIP: Revise that big string of numbers to something useful, like<\/p>\n The “extra_” prefix in front of any shortcode tells SwiftCloud to basically ignore the contents, to not treat as a reserved field. These names will show in the PDF, but do not affect the contacts that get generated.<\/strong><\/p><\/blockquote>\n Example:<\/p>\n TIP: You can split this into first name, last name if you prefer; if you use swift_name_both, our system will automatically split this into first and last name (most common).<\/p><\/blockquote>\n …and both will get added to your address book separately. This is also key for multi-party e-Sign or forms.<\/p>\n NOTE: For multi-party eSign, SwiftCloud will replace shortcodes, and the dominant-role on-the-fly based on who is signing.<\/p><\/blockquote>\n This only affects multi-party (3 or more) eSign.<\/p>\n <\/p>\n","protected":false},"excerpt":{"rendered":" GOAL: Show Jane Doe instead of Guest User 8349 Problem: We need _1_ contact to be the “master namer” at any given time. This occurs because there can be multiple people in a doc (i.e. child + parent, seller(s) + …<\/p>\n[swift_additional_contact_name name=\"additional_contact_swift_name_1\" role=\"Seller\"]<\/pre>\n
[swift_name_both name=\"swift_name_both\" role=\"Seller\" required]<\/pre>\n
[swift_name_both name=\"extra_swift_name_both_1588184473527\" role=\"Client\" required]<\/pre>\n
[swift_name_both name=\"extra_swift_name_both_bottom role=\"Client\" required]<\/pre>\n
\n