Is there any option to remove anchor string after signature on document in DocuSign.
Please suggest if anything here
Just make the string with a white text on white background, so it's not visible.
You cannot modify the document after signing in any way. This is a legal requirement.
Related
Image 1 - Pdf opened in browser, it locates mouse pointer location. Signer tab should have been placed next to "Hello" (x-142, y-111 pixels)
Image 2 - Docusign placed tab here instead
x/y positioning via absolute specification is off in v2 of the API. V2.1 is much better at this.
Or even better, use anchor text positioning when you can.
I don't see any way to emphasize an individual word or phrase using Bixby's text styling and font features. Is this correct?
https://bixbydevelopers.com/dev/docs/reference/type/layout-macro-def.content.single-line.text.style
I've double checked with our Bixby View Team, unfortunately, specific syntax such as bold or italics are not supported at the moment.
All the available style are listed in Fonts Reference of design guide. And please note that the style applies to the entire string of a template or the entire string of a slot from a card component.
If this feature is critical to your capsule development, I would recommend that you raise a Feature Request in our community. This forum is open to other Bixby developers who can upvote it, leading to more visibility within the community and with the Product Management team.
When users open the document to sign, on the left of the document, there is a yellow tab 'next'. How to disable that? Or at least change the color. We are using embedded signing.
You can't disable the "Next" button, it's a part of the UX. You can probably change its color, see the Branding Guide.
I want to replace some keywords in template document with some text and as per the solution found by the API is that the text gets imposed over the keyword and the keyword is also visible.
I just want to know that is there any way through API, to replace keywords fully from the document with the text we want and hides the keyword.
Re "as per the solution found by the API is that the text gets imposed over the keyword and the keyword is also visible" -- this describes how anchor text works in DocuSign. DocuSign will never actually modify the contents of the underlying (original) document; it will simply overlay tabs (text, input fields, etc.) on top of your original document in the places that you specify.
To achieve your goal, I'd suggest that you "hide" the keywords in your document by setting the text color of each keyword to match the background color of your document. For example, if the background color of the document is white, set the text color of each keyword to white. This will make it so that the keyword text is invisible in the document (but still detectable by Docusign) -- when DocuSign overlays text in those locations, only that text will be visible.
In the rich text field I choose Full alignment, but when previewed the text has left alignment. When I close and reopen the document, the text is brought back to left alignment.
How can this be resolved?
If I understand you correctly, you have a Notes Form with a Rich Text field, in which you align the text "justified", as in the screenshot below:
But if you view that in a Xpage, the text is no longer justified, neither in the read-only rendering, nor in the edit-rendering with the CKEditor:
Alas, if you align the text justified via the CKEditor, it renders properly in the browser
with an "interesting" rendering in the Notes Client:
This is a "known" problem and in my demo case, the Xpages runtime engine even warns me about that:
"Saving this document will change its format from native Notes rich text to HTML. This may cause a change or loss of formatting if opened again in the regular Notes client."
The conversion of rich text to HTML and vice versa is not the whole problem, even though the message says that. There are also issues with repeated conversions back and forth changeing font sizes, loss of certain colors and styles, etc.
This is a long standing issue with Ben Langhinrichs, who documents that rather thoroughly and even sells an extension to handle that conversions better.
Hope this helps a little bit.
I am using v8.5.3 and in the All Properties of the CKeditor they have a property called 'htmlConversion Warning' that you can set to 'noWarning' which seems to prevent the Saving this document message mentioned above. Seems someone from IBM has taken a note from Microsoft on providing a solution. Now if only they would take a note from them on how to market the product.