cdean's account

Thank you for your quick reply.

Yes, I waited for the expiry date to hit which we have set for one hour.  After the one hour +5 to 10 min, I send the request to OneSpan to get all of the EXPIRED packages. The packages, that should have been expired after one hour, are NOT present in the OneSpan response.  The packages still have a status of SENT.  When we look at the packages from our OneSpan account the same packages' statuses are either still SENT or SENT (Trashed).  

Any ideas?

Here's how we are pulling requests from OneSpan, where packageModel is List<IdentifiPackageModel>:

const int PageCount = 50;
const int FromPackageNumber = 0;
const int PackageDaysRange = -7;

Page<DocumentPackage> Packages = OneSpanClientObj.PackageService.GetUpdatedPackagesWithinDateRange(status, new PageRequest(FromPackageNumber,                                                                                                                                                 PageCount), DateTime.Today.AddDays(PackageDaysRange), DateTime.Now);

foreach (DocumentPackage Package in Packages) {
    packageModel.Add(new IdentifiPackageModel { id = Package.Id.ToString(), status = packageStatus });
}

Secondary signed only: srgrxf1LpUXTHr-XjBmyAdKTGcY=
Primary signed only :     seVvaTKO685acTjKKypeYWmehJU=

I just checked by polling OneSpan again and they are correctly set to EXPIRED now.
Is there a time difference between the OneSpan server and our east coast OLE Service that calls OneSpan?

Thank you for the explanations.
These are very helpful.

Thank you very much Duo_Liang.

It sounds like my sequence is correct in my mind...thanks for validating the process.
I have a couple of incorrect Api calls as well as jsonString replacements that need to be done. I will fix these.
I am very close.  I am getting a 404 when I try to apply the layout.
I will continue to work on getting the layout to match/find the document in the package.

Thanks again for your help and I look forward to hearing from you next week.
Enjoy the rest of your time off!

~Clayton

Never mind.

I have found the error and corrected it.
eSign now applies the layout correctly and sends it to the signer correctly.
Once I used the supplied DocID when the draftPackage was created INSTEAD of the actual DocumentPackage documents id, everything worked as expected. DOH!!!!

Thanks for you help!

This forum request is closed by customer :)