No decline option in the mobile viewer?

Hey nserror, I see the same. I will look into why this is and let you know what I find. :)

The opt-out and decline essentially do the same thing, so because of real estate on the mobile view, the opt-out was the one that was placed there. Do you need the decline option from mobile? If so, you could have support turn off your mobile viewer and simply zoom to use the desktop view on mobile which does have the decline option. I believe in the next release of the mobile viewer experience, there will be a different handling of this to allow better usage of both options. Not sure when the new mobile signing ceremony will be released. I'll have to see if it's on the road map for this year or not. I'll let you know.

So answer me this, reading through the REST API documentation its not immediately clear but, can I decline an approval for a specific signer through the REST API so I could implement my own decline button on our end?

Sorry for the delay. I was offline, all day. I will do a test, tomorrow on changing the status to DECLINED by doing a package update call and let you know. If you get a chance to test it out before me, let me know.

We tested just updating the package status to null but unlike updating it to other statuses, when we do DECLINED we get the following error. Seems like it should work but its missing some information? Could you provide any more info on if we can make this work. Thanks Michael. Silanis.ESL.SDK.EslServerException: Unable to update package settings. Exception: The remote server returned an error: (400) Bad Request. HTTP PUT on URI https://sandbox.e-signlive.com/api/packages/67c3f149-b506-41bd-b136-d81d9a8b737c. Optional details: {"messageKey":"error.validation.optOut.invalidComment","entity":null,"technical":null,"packageId":null,"message":"Invalid comment provided. Please provide a valid comment.","code":400,"name":"Validation Error"} ---> Silanis.ESL.SDK.EslServerException: The remote server returned an error: (400) Bad Request. HTTP PUT on URI https://sandbox.e-signlive.com/api/packages/67c3f149-b506-41bd-b136-d81d9a8b737c. Optional details: {"messageKey":"error.validation.optOut.invalidComment","entity":null,"technical":null,"packageId":null,"message":"Invalid comment provided. Please provide a valid comment.","code":400,"name":"Validation Error"} ---> System.Net.WebException: The remote server returned an error: (400) Bad Request. at System.Net.HttpWebRequest.GetResponse() at Silanis.ESL.SDK.Internal.HttpMethods.PutHttp(String apiToken, String path, Byte[] content) --- End of inner exception stack trace --- at Silanis.ESL.SDK.Internal.HttpMethods.PutHttp(String apiToken, String path, Byte[] content) at Silanis.ESL.SDK.RestClient.Put(String path, String jsonPayload) at Silanis.ESL.SDK.Services.PackageService.UpdatePackage(PackageId packageId, Package package) --- End of inner exception stack trace --- at Silanis.ESL.SDK.Services.PackageService.UpdatePackage(PackageId packageId, Package package) at BoardBookitWebService.Repositories.SignatureRepository.putPackageStatus(Int32 companyId, String packageId, String status)

My apologies again. I was travelling at the end of last week and the beginning of this week, both, and didn't get to it just yet. I will try it out, right now.

Okay. Same thing happens for me when attempting to push a DECLINED status. I guess this makes sense as it would be acting on behalf of the user. One workaround I can think of off the top of my head would be to create your own decline option by setting the status to DRAFT and adding an attribute to the package that will specify that would explain that the package was declined. You'd be able to check any DRAFT package for this "declined" attribute. If you have interest in this, let me know, I can create some code to send to you on it. I will try a couple more things to see if I can get update a package to declined, but I don't know that it'll work in any way.