hmboonstra's account

Hi Duo Liang, we have the same problem with a package where the sender is also the signer (and the only signer): https://sandbox.esignlive.com/api/packages/LfOPVM92RVTYBSAulY62iyL5qWo= In this case the roleId doesn't work (i.e. result in a 404), but the signerId works. In a different package where there are two signers, one of which is also the sender it is possible to retrieve the status for all signers with their roleId and the signerId: https://sandbox.esignlive.com/api/packages/W9z9k0Huzd6PQE-lxuY8D9GuOmg= My question is, is this a bug? And if it is, when will it be fixed? Your solution using the packageService.getRoles() works, but that returns Api Signers instead of SDK Signers. Using the SignerConverter to convert the Api Signer to a SDK Signer introduces the problem again, because the signerId is overwritten with the roleId. Thanks in advance, regards, H.

Hi Duo Liang, thank you for your explanation. I was confused by why the getSigningStatus mostly works with the roleId, but sometimes returns a 404. Its not a problem, we'll use the real signer id instead. It would be nice if the (Java) SDK version of the Signer class exposed this value, but its not a problem since the API version does have it :-) Thanks again, regards, H.