Hello,
I try to install the version 11.41 of com.silanis.sdk
As I see, there is a dependency on littleproxy 1.1.2 (org\littleshoot\littleproxy\1.1.2)., but it has not been updated since 2017.
Could you please confirm if it is still supported and required?
Thanks and Regards,
Michail
Hello,
I am in the process of testing the migration of API key to API Token. I created a client app in the test account, got the client id and client secret. But I can't retrieve the Token API from the ApiTokenConfig
Here is the error message I get:
Caused by: java.lang.RuntimeException: com.silanis.esl.sdk.EslException: Unable to create access token for ApiTokenConfig{baseUrl='http://localhost:8881/api', clientAppId='.......................', clientAppSecret='................', tokenType=OWNER, senderEmail='null'}
We are seeing this error:
Caused by: java.lang.NoSuchMethodError: com.silanis.esl.sdk.builder.CeremonyLayoutSettingsBuilder.withoutIFrame()Lcom/silanis/esl/sdk/builder/CeremonyLayoutSettingsBuilder;
Just want to confirm that this method is deprecated especially since we are moving to New Signer Experience.
Hi. I've got fields that I've set up like this:
.withField(createFieldBuilder(FIELD_TEXT_BOX_CONSTANT, TEXT_BOX_GRP_ADDRESS_CONSTANT, "tbRetirementDate")
.withFontSize(22))
The font size is not changing. The New Signer Experience is different from the classic experience as far as the way text that is entered into fields looks. It's very light. We're a government agency so we have to comply with ADA accessibility standards.
Screenshot is attached.
Please advise.
Intermittently getting some of our senders set to 'EXTERNAL_SENDER'. What would cause this? Package TmMr3BJ4K8RXuVOKzkfRtFeSsWo= is one example. Thanks
Hello I found this code for to be able to create a signing session :
I am looking for a place to store a signer's role. The idea here is we can store an attribute against a signer that allows us to find the proper signer based on some role in our workflow. I tried to use 'signerType' - but it seems the system wants to store its own values there such as EXTERNAL_SIGNER etc.
For now I plan to store my role property in Signer 'placeHolderName' but I am not sure what this attribute is supposed to hold.So 3 questions:
What is 'placeHolder' supposed to be?
Customer wanted to confirm if the class com.silanis.esl.sdk.EslClient is supposed to be thread safe?
So far, going by the examples they were assuming that it is indeed thread safe and thus creating a single instance of EslClient throughout the application. If it is to be used in such a way, then we found that it is not thread safe.
Their findings below:
Below is the snippet of the code from AccountApiClient within the esign sdk:
public Sender getSender(String senderId) {
Code:
.withValidation(FieldValidatorBuilder.regex("^\\d{2}/\\d{4}$").required().withErrorMessage("Please enter a valid retirement date (MM/YYYY)"))
When we are testing and when we do not enter a value, we are seeing what looks like an overriding validation error message than the one we configure in the code. See attached. When we enter a value that does not adhere to regex, we see correct validation error.
We would like the error we configure in the code to be the one we see whether there is a value entered or not.
Please advise.
We are transitioning to New Signer Experience. When we test documents that are ready to sign, we are receiving e-mail notifications with one notable difference between classic and new signer experience: Given documents that have already expired and we click on "Go To Document" in the e-mail, the new signer experience is taking us to login screen. In the classic experience, the "Go To Document" link in the e-mail was taking us to an "Access denied" screen. Our business unit prefers the "Access denied" screen.