Account
I am a
Developer
Product(s)
Earned badges
Achievement: Latest Unlocked
Preferences
Replies
Topics Started
Topic Started
Topics |
---|
Hi,
I was wondering if it's possible to change the "Clear All" message.
|
Hi,
I'm having issues setting the expiration date to null.
These are the functions I'm calling:
EslClient eslClient = getEslClient(companyId);
PackageId pkgId = new PackageId(packageId);
DocumentPac
|
Replies Created
Reply to: Package Expiration Dates
Friday, July 8, 2016 at 05:45amOk thank you for checking on that.
Meanwhile, I have another question: Is there a callback method for when a package changes state from Expired to Draft? Would it be the PACKAGE_RESTORE event?
Fernando
Reply to: Package Expiration Dates
Friday, July 8, 2016 at 06:38amWhat do you mean when a package expires it should go to draft? For me, the status changed to Expired and stayed that way until I changed the due date to a future one. Which is the behavior that I would expect. If it changed automatically to draft mode that could cause some confusion.
I was just wondering if there's a callback for when the due date is changed to a future one, thus changing the status from Expired to Draft.
I could just automatically change the status on our end, and assume that the status has been changed on yours, but I would prefer getting the callback in order to have consistency between data.
Fernando
Reply to: Package Expiration Dates
Friday, July 8, 2016 at 07:26amOk, let's see if I can convey my message better to you, I apologize if I wasn't clear enough.
After a package expires, the status of the package in eSignLive is changed to "EXPIRED", and it sends a notification about the event. I'm verifying this by doing a GET Request on the package and looking at the status attribute. Whenever we get that notification, we change the status of the package in our database as well.
After extending the date on the expired package, the eSignLive status changes from "EXPIRED" to "DRAFT". But since we are not getting any notifications, in our database it stays EXPIRED.
My question was if there was any notification for this particular case: When a user extends the date of an expired package, thus changing the status to DRAFT.
Thanks,
Fernando
Reply to: Setting ExpiryDate to null
Wednesday, July 20, 2016 at 05:45amThat's exactly it. A package that previously had an expiration date and now trying to set it to null.
We give our users the option to edit and change the deadline of a package, so if they want to remove the deadline they can. That's the scenario.
Fernando
Reply to: Long-term storage update
Wednesday, December 7, 2016 at 09:51amHi Michael,
Can you expand on how putting a request would work? Will there be an api we can call for this new server to retrieve the document? Or every new request will be analyzed by eSignLive and emailed to the user?
Right now we do all of our storage of signed documents within eSignLive, so this will be a big issue for us.
Fernando
Subscriptions
Topics | Replies | Freshness | Views | Users |
---|---|---|---|---|
Hi,
I got an email from eSignLive today saying that, effective January 9 of 2017, all transactions older than 90 days will be moved from the cloud to another database.
I'm trying to figure out what
|
5 | 7 years 4 months ago | 14 | |
Hi,
I was wondering if it's possible to change the "Clear All" message.
|
5 | 7 years 8 months ago | 3 | |
Hi,
I'm having issues setting the expiration date to null.
These are the functions I'm calling:
EslClient eslClient = getEslClient(companyId);
PackageId pkgId = new PackageId(packageId);
DocumentPac
|
5 | 3 years 7 months ago | 35 | |
I'm looking for more information on the expiration date. Can you tell me how the date and time is stored on your end?
|
24 | 7 years 9 months ago | 193 |
Subscriptions Release Notes
This user is not subscribed to any release notes.