Account


Earned badges

Earned badges

Achievement: Latest Unlocked

Topic Started

Topics

Hello,

We are witnessing an issue with Document upload with large document sizes. I wanted to know what the limitations are of the platform. 

Hello, 
I've had this issue for several weeks now and I'm not sure how to remedy it. 

I have a few questions in regards to text fields on documents in the signing ceremony:

Can we make the text fields on documents Required or Optional?

I am working with authenticating Signers in the ceremony and when we try to set the signers to the default option (email) -- the package creation returns with a 400 error.

Replies Created

Reply to: Authentication Error

0 votes
Hello, Well that did the trick. I went into our Back Office Settings and changed that value to false. Thank you for that May the Force be with you D'Metrius Agurs

Reply to:

0 votes

Hello, 

My apologies, I didn't give you enough context around that line of code. We have a method we wrote that uses the GetSigningURL from the PackageService

Here is that method:
  public Tuple<ESignStatsNotifier, string> GetSigningUrl(
      PackageId packageId,
      string signerId)
    {
      string str = "";
      try
      {
        str = this._client.PackageService.GetSigningUrl(packageId, signerId);
      }
      catch (Exception ex)
      {
        this._logger.Error<Exception>(ex);
        EslNotificationStatus.EslIsDown = true;
      }
      finally
      {
        this.CheckIfEslIsDown();
      }
      return Tuple.Create<ESignStatsNotifier, string>(FailSafeEslClientWrapper.IsDown ? ESignStatsNotifier.Down : ESignStatsNotifier.Up, str);
    }

 

The SessionToken is the SignerId, we just changed the name of the variable but it has the correct value. 
As of right now, at the ceremony creation and the package completion I'm not able to generate the url for the signer I created as such.

                        packageBuilder
                            .WithSigner(SignerBuilder.NewSignerWithEmail(sender.Email)
                                .WithFirstName(sender.FName)
                                .WithLastName(sender.LName));

 

and this is how I set up our PackageBuilder 

 var packageBuilder = PackageBuilder
                    .NewPackageNamed(packageName)
                    .DescribedAs(packageDescription);


Reply to: Broken png file on Complete Signing modal

0 votes

Hello Duo, 
 

If I understand the question correctly, I think it is deployed on our Front End Server. 
Where can I specifically find the account level and the account settings? Is that located on the server or is that something I can find in the back office?

 

Thanks, 

D'Metrius Agurs


Reply to: Broken png file on Complete Signing modal

0 votes

To confirm your question before, I did change the files on the server and not the back office. It was this route specifically:
/opt/eSLFrontEnd/public/stylesheets

 

Will I find the broken png in the css file?


Subscriptions

Topics Replies Freshness Views Users

Hello,

We are witnessing an issue with Document upload with large document sizes. I wanted to know what the limitations are of the platform. 

2 5 days 3 hours ago 14

Hello, 
I've had this issue for several weeks now and I'm not sure how to remedy it. 

7 1 month 1 week ago 34

I have a few questions in regards to text fields on documents in the signing ceremony:

Can we make the text fields on documents Required or Optional?

1 2 months 2 weeks ago 33
4 7 months 2 weeks ago 39
I am working with authenticating Signers in the ceremony and when we try to set the signers to the default option (email) -- the package creation returns with a 400 error.
2 1 year ago 47

Code Share

This user has not submitted any code shares.