DocuSign API rules and limit
How To articles are not official guidelines or officially
supporteddocumentation. They are community-contributed content and may
not alwaysreflect the latest updates to Liferay DXP. We welcome your
feedback toimprove How to articles!
While we make every effort to ensure this Knowledge Base is accurate,
itmay not always reflect the most recent updates or official
guidelines.We appreciate your understanding and encourage you to reach
out with anyfeedback or concerns.
Legacy Article
You are viewing an article from our legacy
"FastTrack"publication program, made available for
informational purposes. Articlesin this program were published without a
requirement for independentediting or verification and are provided
"as is" withoutguarantee.
Before using any information from this article, independently verify
itssuitability for your situation and project.
Issue
- APIs are failing, hence Liferay has to provide a feature to restrict the API limit.
Resolution
-
With the current DocuSign integration feature provided by Liferay, the existing customers are not seeing this issue while working with 10k concurrent users.
The implementation of this integration is mainly focused on creating those envelopes and sending them to DocuSign for the users to sign.
The way Liferay implemented was to be fully proxy, which means that none of the data users see there about the envelope is actually on the Liferay side, so, every time Liferay needs some information it makes a call to Docusign, the data is not stored in Liferay at all.
- With that said, adding this limit as consumers are asking would require us to fully change the functionality because all the data on the Liferay side is needed and required to check if it could or could not update at the moment that the user is trying to check the envelope details.
-
In this case, if the last check was less than 15 min ago, it would not be updated, because the latest value of that status couldn't received (and all the other details). This would hurt the feature goal, which is to have live status and details of the envelope.
- If let's say, Liferay would want to achieve what the requirement is, then there is a need to persist the data in Liferay and only update if the limits were not exceeded, again, changing completely how the feature currently works.
-
Whereas, currently, Liferay already has customers using without this API call limit in a solution with 10k concurrent users and hasn't had such issues with it.
Moreover, if there is a feature to trigger an action based on envelope status changing, it's necessary to implement a webhook for that: https://developers.docusign.com/platform/webhooks/
-
Conclusion: the data is not stored in Liferay at all. Also, Liferay doesn't have this webhook implementation on DXP.
Did this article resolve your issue ?
