This topic contains 10 replies, has 2 voices, and was last updated by  ChrisBrown 2 months, 1 week ago.

  • Author
    Posts
  • Participant
    ChrisBrown
    Member
    Member since: 26.09.2018
    Number of posts: 19

    Good Afternoon,

    i am currently in the process of updating one of our Applications to include ADA functionality. This application is pointed at the cloud implementation. my test is going against https://sandbox.e-signlive.com

    The application in question has a two signer process where we get the signature of the first signer before making another call into the system to create a token from the second signer. The first signer has the “Enable accessibility mode” link in the top right which seems to flip to the screen that put the pdf as text. However, after the signing is complete and our application then triggers the creation of a token for the second signer and a link to the documents needed to be signed by the second signer is generated, the documents no longer have that “Enable accessibility mode” option.

    is there some line of code that i am missing where i need to re turn on the ada flag for a package every time i generate a token?

    Here is the important bits of the code that is being used:

    var closingPackage = PackageBuilder.NewPackageNamed(_configSection.ApplicationDescription)
    .WithSettings(DocumentPackageSettingsBuilder.NewDocumentPackageSettings()
    .WithoutCaptureText()
    .WithoutDecline()
    .WithDocumentToolbarDownloadButton()
    .WithoutInPerson()
    .WithoutOptOut()
    .WithoutWatermark()
    .WithAda()
    .WithCeremonyLayoutSettings(CeremonyLayoutSettingsBuilder.NewCeremonyLayoutSettings()
    .WithoutGlobalSaveAsLayoutButton()
    .WithoutGlobalConfirmButton()
    .WithGlobalDownloadButton()

    )
    )
    .WithSigner(SignerBuilder.NewSignerWithEmail(singerEmail)
    .WithFirstName(package.FirstName)
    .WithLastName(package.LastName)
    .WithCustomId(employeeId)
    .SigningOrder(1)
    )
    .WithSigner(SignerBuilder.NewSignerWithEmail(_setupConfiguration.Value.SharedEmail)
    .WithFirstName(“redacted”)
    .WithLastName(“redacted”)
    .WithCustomId(Signer2)
    .SigningOrder(2)
    );

    //Loop through docs
    foreach (var doc in package.Documents)
    {
    using (var stream = new MemoryStream(doc.Data, false))
    {
    var docBuilder = DocumentBuilder.NewDocumentNamed(doc.Title)
    .WithId(_documentConfiguration.Value.GetDocumentId(PackageType.Closing, doc.DocumentType))
    .FromStream(stream, DocumentType.PDF);

    foreach (var signature in doc.Signatures)
    {
    docBuilder.WithSignature(signature.CreateSignatureBuilder(_setupConfiguration.Value.SharedEmail, singerEmail));
    }

    closingPackage.WithDocument(docBuilder);
    }
    }

    packageId = client.CreateAndSendPackage(closingPackage.Build());

    // create the signing session for employee
    token = client.CreateSignerSessionToken(packageId, employeeId);
    return new ESignatureResponse()
    {
    ServicePackageId = packageId.Id,
    SessionUrl = string.Format(_configSection.ApplicationIFrameUrl, token.Token)
    };

    and then for the subsequent signer:

    var packageId = new PackageId(servicePackageId);

    SessionToken token = null;

    PerformTransaction(client =>
    {
    token = client.CreateSignerSessionToken(packageId, Signer2);
    });

    return new ESignatureResponse()
    {
    ServicePackageId = servicePackageId,
    SessionUrl = string.Format(_configSection.ApplicationIFrameUrl, token.Token)
    };

    • This topic was modified 2 months, 2 weeks ago by  ChrisBrown.
    Keymaster
    Duo_Liang
    Guru
    Member since: 14.06.2018
    Number of posts: 691

    Score

    0

    Good afternoon Chris,

    I’ve tested your workflow and it works at my side, and there’s no need for extra change in URL every time you generate the link as long as you’ve set ADA enable at your package level.

    My first suggestion is that, can you print out two generated links and directly input them into your browser to see whether it yields the same problem? (Signer1 can see “Enable Accessibility Mode” while Signer2 can’t)

    Duo


    Duo Liang
    OneSpan Junior Technical Evangelist
    • This reply was modified 2 months, 2 weeks ago by  Duo_Liang.
    Participant
    ChrisBrown
    Member
    Member since: 26.09.2018
    Number of posts: 19

    Score

    0

    I have attempted this again by putting the links directly into the browser and it does have the same result. Signer one does have the ability while signer 2 does not.

    the package id of the test i just made is 9l986UOWaUgeJgEYrgbx9dFoMqg= in case you can look it up on your side.

    Keymaster
    Duo_Liang
    Guru
    Member since: 14.06.2018
    Number of posts: 691

    Score

    0

    Can you send your links for two signers to developer@esignlive.com so that I can have a closer look at that?

    Duo


    Duo Liang
    OneSpan Junior Technical Evangelist
    Participant
    ChrisBrown
    Member
    Member since: 26.09.2018
    Number of posts: 19

    Score

    0

    I have sent the email with the two links. My apoligies for taking so long to do so, but i had to rearrange the application to generate them both without having to complete the first

    Keymaster
    Duo_Liang
    Guru
    Member since: 14.06.2018
    Number of posts: 691

    Score

    0

    Hi Chris,

    Good morning!
    I think I found out the reason for this issue. Were you using sender email as the second signer? (_setupConfiguration.Value.SharedEmail) If I did so, the same result happened at my side.
    I will create a support ticket on your behalf and we will confirm with the Project Management team whether it’s expected behavior. Can you also describe more on your scenario why you want the second signer to have Accessibility Support since he/she has a fixed email and seems not visibility impaired? I will also add this to our ticket.

    And at the same time, I’ve tested that as long as the second signer is not the sender of the package, he/she can see Ada enable button. You might want to take it as a workaround that #1. use another fixed email for signer 2 or #2. change another sender for this package.

    I will update this thread as long as I got any updates.
    Duo


    Duo Liang
    OneSpan Junior Technical Evangelist
    • This reply was modified 2 months, 2 weeks ago by  Duo_Liang.
    Participant
    ChrisBrown
    Member
    Member since: 26.09.2018
    Number of posts: 19

    Score

    0

    I do believe that is correct where the account is set up with the same email address as is used for the signer. i assume that is what you mean by sender in this context.

    unfortunately, i am unable to change the signer email address. this is an existing process that will not change easily.

    what do you mean change another sender for this package? from what i understand, once the account is made in esignlive with an email address, it cannot be changed. Do you mean that this can be changed? or am i missing something?

    Keymaster
    Duo_Liang
    Guru
    Member since: 14.06.2018
    Number of posts: 691

    Score

    0

    Hi Chris,

    Yes, you can’t change your owner’s email once your account has been created. And the following is what I mean by “change another sender”:

    #1. As you know, one account can have multiple senders, in this workaround, we’d need another sender who are under your account.
    If you don’t have any other senders under your main account, you can invite one through Web UI or REST/SDK code, guide here.

    #2. in your code, you can add extra one line to set sender, this is also called “Create a Package on Behalf of Another User”, documentation here

                DocumentPackage package = PackageBuilder.NewPackageNamed("package_name")
                                            .WithSigner(...)
                                            .WithDocument(...)
                                            .WithSenderInfo(SenderInfoBuilder.NewSenderInfo("sender_email"))
                                            .Build();

    As a result, this package is sent by your sender instead of the owner, and once your owner is not the sender of the package, your owner can see the Ada button.

    Duo


    Duo Liang
    OneSpan Junior Technical Evangelist
    Participant
    ChrisBrown
    Member
    Member since: 26.09.2018
    Number of posts: 19

    Score

    0

    I will have to take a closer look and see what kind of impact this has, but i do not think this will be a viable option either. I do not believe that the owners of this app will accept adding a new email address and processes to check it as acceptable. After i investigate the impact, i will ask them what they think.

    Please let me know when you get an answer as to if this is deliberate behavior. If not, when could we expect a fix for this?

    Keymaster
    Duo_Liang
    Guru
    Member since: 14.06.2018
    Number of posts: 691

    Score

    0

    Hi Chris,

    I just get confirmed from Jira ticket that “there’s no ‘Enable accessibility mode’ for package sender/owner is by our current design”.

    However, “make the sender UI ADA compliant” is actually under the plan but there’s no confirmed ETA for this feature.

    Duo


    Duo Liang
    OneSpan Junior Technical Evangelist
    Participant
    ChrisBrown
    Member
    Member since: 26.09.2018
    Number of posts: 19

    Score

    0

    I will pass this on to the application owners and see what they want to do.

    Thank you for this information.

You must be logged in to reply to this topic.