December 2023

NeSL eStamping Update

Telangana state is now available for eStamping via NeSL.

This enhancement aims to provide an streamlined experience for our users in Telangana.

December 8, 2023
Improvement
New Feature
Bug Fix
NeSL
eStamp

December 2023

Face Match

Face Match is now available on App1 environment.

Face Match compares the signer’s face, captured during the signing journey, against the signer’s approved ID proof uploaded by the sender. This makes sure only the intended recipient signs the document.

Learn more about Face Match here: https://www.leegality.com/features/facematch

December 6, 2023
Improvement
New Feature
Bug Fix
Face capture

December 2023

Invitees Can View Supporting Documents

Invitees (signers and reviewers) can now view the supporting documents uploaded by other invitees - if allowed by the sender. 

Benefits

  • Reviewers will have the option to review supporting documents while accepting or rejecting the document. Ensuring no misses in the supporting documents.
  • Faster reviews and approval cycles.

December 4, 2023
Improvement
New Feature
Bug Fix
Supporting Documents

November 2023

PDF Templates

We're excited to launch PDF Templates on App1. 

With PDF Templates you can easily create reusable templates by simply uploading your PDF documents and adding the required dynamic fields.

Key Features

  • Create dynamic templates using your PDF documents

No need to recreate your entire document in Leegality’s text editor and instead just simply upload your PDF and drop fields on top.

This significantly reduces the time and effort to convert your documents into Leegality templates.

  • Add dynamic fields to your PDF using drag and drop editor

Now you don’t need to configure fields in-line while recreating the document.

PDF templates allow you to simply drag and drop the field wherever required on the PDF.

  • You can choose from a variety of fields to accommodate all of your requirements: Available fields are:

         1. Text field

        2. Dropdown

        3. Radio Button

        4. Checkbox

        5. Date

        6. Image attachment

Knowledge Base Article - How to Create a PDF Template?

November 24, 2023
Improvement
New Feature
Bug Fix
Templates

October 2023

NeSL eBG Phase 2

Non-signers and only stamping journey

We are thrilled to introduce a significant update to our NeSL eBG suite that will allow our clients to skip debtors and beneficiaries from the signing journey in eBG flow.

In addition, clients now have the flexibility to obtain only stamps from NeSL while utilizing other signing options available on Leegality, such as Aadhaar, Virtual, DSC, and more for signing.

For more details on Bank Guarantee: https://www.investopedia.com/terms/b/bankguarantee.asp

1. Sending Journey

1. Toggle on "NeSL’s eBG Flow" on the 'Create' screen.

2. After adding the required signing invitees (with or without NeSL signing type), navigate to Signing Journey Options and toggle on "Number of NeSL parties." You can specify the number of total parties for stamping-only flows or non-signing parties for partial signing via NeSL here.

3. Fill out the NeSL form or upload a NeSL Excel document.

4. New fields in the form include Event type, Is Individual, Signatory Gender, Expiry Date, and Claim Expiry Date.

5. A new Party section is available on this screen with the same number of placeholders as mentioned in the Signing Journey Options on the previous screen.

6. After completing the form, the document can be sent to the participants.

2. Signing Journey

1. Signing invitations will be sent only to the participants added in the invitee section.

2. Parties not added as invitees in step two (Invite) will not receive the signing link but will receive final mail communication for eBG details.

3. The remainder of the signing journey remains the same as before.

Why is this update important?

1. This update aligns with the standard market practice where banks typically do not require debtors and beneficiaries to sign bank guarantees. It's primarily the responsibility of bank employees to sign. With this update, our bank clients can replicate this standard practice digitally.

2. NeSL now offers the option to use its platform solely for stamping for eBG, a choice that many banks are eager to embrace due to the simplicity and efficiency of stamping flow. This feature enables clients to leverage NeSL for stamping and Leegality for signing, offering a versatile solution.

Additional Points

1. NeSL parties can be used for both stamping-only and partial stamping flows.

2. In the case of stamping-only flows, the signing process commences once stamping is completed, which is an automatic process taking only 2-3 seconds on average after sending the document.

3. This module supports all available event types for eBG, including issuance, amendment, invocation, cancellation, and more

October 6, 2023
Improvement
New Feature
Bug Fix
NeSL
eSign

October 2023

Auto-switching ESP Priorities

Signer when using Aadhaar eSigning goes to different ESPs, depending on the number of trial attempts. This happens because we use backup ESPs. For example, by default, the signer lands on the following ESP pages according to the attempts:

1. Attempt 1:  NSDL (Protean)

2. Attempt 2: Verasys

3. Attempt 3: CDSL

This is the default set priority order for ESPs

Previous Working

In the past, determining whether ESP priority order adjustments were needed required manual monitoring by our Support team. This process was time-consuming and relied on Admin Panel actions. The decision to switch priorities was based on various ESP parameters, including success rate, error rate, and pending rate.

New Update

Now, with this update, we have automated the process. Here's what you need to know about this update:

A. Continuous Monitoring: Transactions will now be automatically checked every 10 minutes, allowing us to swiftly respond to changing conditions.

B. Priority Logic: We've implemented a priority logic based on the following considerations:

   i. NSDL (Protean) as super-priority:

This ESP will maintain its position as the top priority, thanks to its quick Turnaround Time (TAT) and commitment to engagement. It will only be deprioritized if its success rate falls below a specified threshold (success rate threshold = 40%).

  ii. Auto-switch for OTPs only: This feature applies exclusively to OTP-based transactions and will not affect Bio, Iris, or Face authentication methods.

  iii. Global Level: Auto-switching will be applied globally, ensuring a consistent experience for most users. However, organizations with custom orders or specific ESP configurations will need to manage priority orders manually.

C. Notification: Whenever an ESP's priority order is switched, an automated email notification will be sent to relevant stakeholders.

D. ESP Activation/Deactivation: Activation and Deactivations of ESPs are not included in the scope of this feature. Only the priority order is impacted.

E. For App1 only: This feature will impact only app1 transactions. Sandbox and Preprod won't get impacted.

Key Advantages

1. Reduced Turnaround Time: Quick adjustments to ESP priorities in case of dropping success rates will lead to faster transaction processing.

2. Less Manual Intervention: Our Support team will no longer need to manually monitor and adjust priority orders, freeing up their time for more strategic tasks.

3. Improved Client Relationships: With fewer escalations and smoother transactions, we expect to strengthen our client relationships.

October 9, 2023
Improvement
New Feature
Bug Fix
eSign
Aadhaar eSign

October 2023

AI-Powered Smart Name Feature On App1!

We're unveiling an advanced AI-driven system that efficiently handles the above challenges, from jumbled names to phonetic similarities. The aim? To offer more accurate, reliable, and traceable similarity scores for name comparisons.

How does it work?

Enable Smart name AI from department level settings to start using it.

The result of Smart name AI will appear on the details page as they currently do.

Existing Smart Name users can effortlessly upgrade to the new Smart Name AI with a simple toggle switch in settings once they have access!

October 2, 2023
Improvement
New Feature
Bug Fix
Aadhaar
verification
eSign

September 2023

Aadhaar First

Introducing a new feature that will enhance your control over the signer experience in our platform: "Aadhaar First."

With "Aadhaar First," clients can now specify if Aadhaar eSign types should be prioritized over other eSigning options for signers. Additionally, senders have the ability to fine-tune the signing sequence and retry count for subtypes within Aadhaar, including OTP, BIO, and IRIS.

Setup and Sending Journey

To start using this feature, simply grant access from the Admin Panel. Once enabled, follow these steps to configure it in the sending journey:

1. When selecting the Aadhaar eSign type for an invitee, a new toggle for "Prioritize Aadhaar for the invitee" will appear in invitee-level options.

2. Turn on the toggle to specify the selected subtype (OTP/BIO/IRIS) to be shown.

3. You can further customize the experience by setting:

 3.1 Order: Define the sequence in which the subtypes should be presented to signers. Subtypes with the same order will be shown together.

3.2 Retry Attempts: Determine the number of additional attempts a signer needs to go through before the next option in the order is shown and made available to the signer.

Impact on the Signing Journey:

Once applied, "Aadhaar First" transforms the signer journey:

1. Signers will initially see only the Aadhaar eSign option.

2. eSign subtypes will be displayed according to the configured order.

3. After reaching the configured retry attempts for a subtype, the next subtype in the order will be shown. An attempt is counted when the user clicks on 'Sign Document' button before going to the ESP screen

4. Other eSign types (e.g., Virtual, Cloud DSC) will only be shown to the user after they have completed the retry attempts for all Aadhaar eSign subtypes.

Example Scenario:

Imagine a sender selects prioritise Aadhaar and configures the invitee with the following details:

- Aadhaar OTP with 0 retry attempts at order 1

- Aadhaar BIO with 0 retry attempts at order 2

- Virtual

- Cloud DSC

- Doc Signer

the signer journey will unfold as follows:

Step 1: Signer sees only Aadhaar with OTP in the first attempt, user goes to ESP screen and clicks on cancel or closes the tab

Step 2: Signer previews the document > Signer sees Aadhaar with both OTP and BIO > user goes to ESP screen and clicks on cancel or closes the tab.

Step 3: Signer previews the document > Signer can choose from other signing options (Virtual, Cloud DSC, and Doc Signer) in addition to Aadhaar with both OTP and BIO.

September 25, 2023
Improvement
New Feature
Bug Fix
Aadhaar
Aadhaar eSign

September 2023

NeSL verification flow

We’re excited to announce another upgrade to our suite of features specific to NeSL! We have launched the NeSL verification flow (v1).

Background-

1. For NeSL eSign verification, even if verification fails, we have to Accept the eSign and respond that a mismatch has occurred (Accept but Respond with Result). 

    [For a normal Aadhaar eSign, we have 2 options upon verification mismatch → ‘Reject if failed’ OR 'Accept but Respond with Result']

2. If an NeSL eSign has verification ON and verification fails, the signer’s eSignature is placed on the document, and the next signer is made active (this was the intended flow). We cannot  reject the signing as the entire process happens in NeSL's environment so we're not in control of rejecting the eSign.

3. In the scenario where an NeSL signer signs and there is a verification mismatch, if the next active signer has an automated eSign configured, then despite verification mismatch, their eSign will be affixed to the document. Due to mismatch, the document may not be useful at all for the client. But the document gets completed and the client's automated eSign credits will be wasted nevertheless.

To avoid completion of such a transaction and save the aforementioned eSign credits, we wanted to provide an additional level of check in NeSL eSign flow with verification, so that, incase of verification mismatch, the sender can have an option whether to proceed with signing or not.

The Solution-

We’ve added an additional config in the Account TAB in -
Account → Department → eSignatures → NeSL eSign → Settings button

In Acceptance Condition dropdown, we’ve added a new config called “Accept but pause signing journey”

If an admin selects this option for verification for any verification type, upon verification failure of NeSL signer, the NeSL eSign will be affixed to the document, but subsequent Non-NeSL active invitees should be made inactive.

If 'Pause signing journey' is enabled. if an NeSL signer fails verification and there are subsequent non-NeSL signers, then-

> The subsequent non-NeSL signer will remain inactive even after the previous NeSL signer has signed.

> There would be an email triggered to the sender that verification has failed and the signing journey has been paused.

Failed TAB:

In the Failed TAB, the failure reason will be 'Signed but Verification Failed'. This is the same as the Failure Reason provided when 'Accept but Respond with Result' is enabled as Acceptance Condition. This decision was taken keeping in mind the impact adding a new failure reason would have (scope increase in Report service) and the limited usecases for this scenario.

Activity Logs

There will be a log recording when verification fails. the log will have the report type 'Signed But Verification Failed'

Webhooks:

We haven't updated the webhook payload incase 'Pause Signing Journey' is turned ON. We'll send the same webhook response which is sent incase 'Accept but Respond with Results' is configured at account level.

An Admin who will be setting ‘Pause Signing Journey’ config ON will know exactly for which parameter they’ve set the config (pincode, title etc.). The integration done by the Admin’s organisation can consider next steps if a parameter’s (pincode) verification response comes as false.

September 20, 2023
Improvement
New Feature
Bug Fix
NeSL
Signing journey

September 2023

GPS Location & Accuracy based Restrictions (Geofencing)

We are excited to announce a new feature called GPS Location and Accuracy based restriction, aka Geofencing. With this feature, our clients can now exercise precise control over document signing by ensuring:

1. The signing can be done from within a specific location only

2. Captured GPS location's accuracy to be within a certain threshold

How does it work?

1. Location-based restriction: Senders can specify coordinates and a permissible radius for where an invitee can sign. If the invitee's captured location falls within the allowed area, they can proceed with the signing journey; otherwise, they will need to try again.

2.  Accuracy-based restriction: Senders can set an accuracy threshold for the captured location during document sending. If the invitee's captured location's accuracy exceeds this threshold at the time of signing, they won't be able to complete the journey and will have to try again

Setup:

1. The organization must be granted access from the Admin Panel.

2. In the Account Tab > Department > Invitee Config, clients can manage default permissible radius and default accuracy thresholds.

Sending Journey

1. These new options are available in Invitee > Invitee level/More Options > Enable security features > Capture GPS Location.

2. Senders can choose to enable location-based restriction, accuracy-based restriction, or both in New document Flow/Workflow/APIs/Excel Upload.

3. For accuracy-based restriction, an Accuracy Threshold is required, while location-based restriction requires coordinates in degrees format and a permissible radius (default values are shown as set in the Setup section).

Signing Journey

1. During GPS location capture, these restriction checks are assessed.

2. Invitees can proceed only if the restrictions are not breached; otherwise, relevant messages are shown

When there is no breach and location is captured successfully

When location-based restriction is breached i.e. invitee is outside the allowed location

When accuracy-based restrictions are breached. We are now showing accuracy along with captured GPS coordinates here.

September 6, 2023
Improvement
New Feature
Bug Fix
eSign
Signing journey

September 2023

Leegality WhatsApp Pings

We're excited to announce a game-changing feature that will elevate the way our clients communicate with their customers. Now, invitees can receive all communications such as invitation links, expiry reminders, completed document PDFs, Audit Trail PDFs, etc. directly on their WhatsApp! This feature represents a significant enhancement over our previous methods of SMS and email communication.

Setup

1. To enable this feature for a client, simply grant them access in the Admin Panel and set the per-session cost.

2. Clients can manage settings from their Dashboard: Account> Department > Invitee Configurations> Enable WhatsApp for Communications with Signers

Sender Journey:

Senders can now activate WhatsApp for invitees in the sender journey, as illustrated below:

Step 1

Step 2

Once the invitation is sent, you'll notice a WhatsApp icon next to the phone number, indicating that communications will be sent to the invitee via WhatsApp.

Additionally, our new logs feature will keep the sender informed about the status of their messages (sent, delivered, read), allowing them to take the most relevant actions.

Communications to Invitee

All communications during the signing journey will be sent exclusively via WhatsApp.


September 6, 2023
Improvement
New Feature
Bug Fix
eSign
Signing journey

August 2023

Invitee Level Error Messages

What's Changing:

Previously for NeSL flows, on the Details Page, error messages were displayed for all NeSL invitees, regardless of whether they had signed the document or not. This often led to confusion, especially when a signed invitee was mistakenly shown with an error message. Users were prompted to reach out to already-signed invitees for another signature, causing unnecessary hassle.

The Improved Experience:

Now, error messages will only be displayed on the invitee card of the invitee who haven't signed the document yet and is active. This means you'll have a clear and accurate view of which invitee requires your attention, eliminating any confusion about the signing status of those who have already signed and those who are not active yet.

In this ss, NeSL signer 1 has faced an error. Since signer 2 and 3 are not active, the error message is not being displayed on their invitee cards.

We have renamed NeSL Lending flows from ‘Individual’ and ‘Non-individual’ to ‘Individual Lending’ and ‘Non-Individual Lending’.
These changes have been made in the NeSL form Account Tab.

August 30, 2023
Improvement
New Feature
Bug Fix
NeSL

August 2023

Review process for NeSL's flows

We've made a new update to enhance our Information Review process, specifically for NeSL's flows.

Why This Change?

Previously, reviewers could only check the main document or template that was about to be signed. But with t NeSL gaining traction, it became clear that reviewers needed to see more. When using NeSL, senders have to fill in detailed information about the borrower and specifics about the loan and stamp. This includes essential details like loan details, stamp data, and information about the invitees.

What's New?

Now, if a document has both a reviewer and NeSL signers, the reviewer can see the entire NeSL form completed by the sender. This means they can easily check the accuracy of the sender's entries in the NeSL form and decide whether to approve or decline the document.

August 9, 2023
Improvement
New Feature
Bug Fix
Reviewer
NeSL

August 2023

Expiring Soon Tab on Dashboard

To improve the performance & load time of the "Expiring Soon" tab, we have introduced a filter on the "Expiring Soon" Tab.  You can now either see documents in this category "Sent" by you, or "Received" by you.  

Earlier, both these categories were listed in the same view, which caused performance issues, but now they are listed separately, depending on the filter chosen.

August 2, 2023
Improvement
New Feature
Bug Fix
eSign

July 2023

Enhancement in Low Balance Notifications (stamps)

Earlier, the system only notified users when their unused stamps, expired and reserved stamps  fall below a specified threshold.

However the inclusion of expired and reserved stamps gave a false idea regarding the available stamps for use. Due to which, timely low balance notifications weren't getting triggered to the clients, leading to halt in client operations at many instances as the stamps weren't available for usage.

Now, with this enhancement, we will exclude the expired and reserved stamps while counting triggering Low Balance Notification for stamps.

July 19, 2023
Improvement
New Feature
Bug Fix
Notifications
Stamp

July 2023

Multiple NeSL profiles under a single organisation

Announcing the enhancement to NeSL flows that will allow our clients to have multiple service types, such as Lending, Non-Lending and eBG (coming soon, stay tuned) under the same organisation.

In the past, our clients were limited to mapping only one type of service to each organisation.

However, with our latest update, NeSL credentials can be added for multiple services (or registration types) as separate profiles under a single organisation.

Changes in the Client Dashboard

1. The added profiles will be reflected in the client's Dashboard as well in Accounts Tab > Department > NeSL eSign Config

2. In the sending journey while updating the form, user will see the registration types according to the added profiles.

3. This is applicable on Excel uploads and API calls as well. Based on the registration type specified in the form/Excel/API, mapped profile and credentials will automatically apply.

Here's what this enhancement means for you and our clients:

1. By enabling multiple profiles, we empower our BFSI clients who have diverse operations and want to operate from the same organisation, to efficiently handle different workflows, reducing the need for multiple accounts and simplifying overall management.

2. This also helps our CS team as they won't need to manage multiple accounts for the same organisation with more than one service types.

3. Lower time for onboarding the client. Setting up different accounts adds unnecessarily to the time to onboard the client. With this, time to onboard such clients will reduce.

July 19, 2023
Improvement
New Feature
Bug Fix
NeSL

May 2023

End to End Encryption in APIs

Leegality APIs now support end-to-end encryption through an additional payload encryption capability.  This enables customers to add an additional layer of security and ensure that the API payloads are encrypted using client specific key pairs.  To know more visit our API documentation: https://docs.leegality.com/v3#section/Payload-Encryption

May 24, 2023
Improvement
New Feature
Bug Fix
API Documentation
API
Document security

May 2023

Cloud DSC Support for Group Invitations

You can now configure cloud DSC (Digital Signature Certificate) as a sign type option for group invitations.

This new addition is readily available across our New Document Flow, Workflows, and API 3.0 version. However, please note that this function is not compatible with API 2.1 due to its limitations in supporting Group Invitees.

The attached image provides a glimpse into the Cloud DSC Options in the Workflow Creation process. As a Workflow Creator, you have the autonomy to set the signer ID for each participant individually, or delegate this responsibility to the Workflow Runner to arrange at the time of Workflow execution. In addition, we have also added a verification module. This will allow Workflow Creators to cross-verify the details of a signer with the information present in their Certificate Details, further enhancing the reliability and security of Cloud DSC as a sign type.

May 25, 2023
Improvement
New Feature
Bug Fix
Cloud DSC
Group Invitations

May 2023

New Docsigner API

We have rolled out a new API to eSign invitations created with DocSigner eSign. This is done to speed up the signing process for documents in queue to be automatically e-signed (via doc signer).  

With this new API, instead of configuring Automated Docsigner and keeping the customers waiting for upto a few minutes, our clients can immediately call the new DocSigner Signing API to eSign the docsigner invitation without any wait time.  

Note:  This API works only with Docsigner invitations (not automated docsigners).  The Docsigner must also be hosted on Leegality's server.  

May 1, 2023
Improvement
New Feature
Bug Fix
API
Docsigner

May 2023

Group Invitee Emails Revamp

We have rolled out an update to notification emails that get triggered for group invitations.  Earlier, the emails sent for group invitations were identical to the emails sent for indivdual invitations.  This would confuse group invitees, because the emails would not give any contextual information such as the name of their group, other signers in the group, the threshold of the group, as well as the status of other signers in the group.  

The revamped notification emails will now cover all of this contextual information for the grouped signatories. See the KB here

May 2, 2023
Improvement
New Feature
Bug Fix
Group invitee

May 2023

Biometric Aadhaar eSign Flow

We have added support for the Morpho & Precision PB 510 devices through the backup ESP verasys, in the Aadhaar biometric flow.  To use the flow, customers will have to download the latest version of the Leegality Helper App that's available for download from the Google Playstore.

May 29, 2023
Improvement
New Feature
Bug Fix
Aadhaar
Biometric

April 2023

Sign upload automatic detection

We have made upgrades to Sign Upload on app1. Till now, users have been able to upload a signature drawn on plain white paper. However, we have taken this a step further and developed an automatic signature detection system.

With this new update, users can now upload a picture of a document with a signature anywhere on the page. The system will automatically detect the signature and draw a crop box around it. This feature will be especially helpful for users in rural areas who found the additional step of manually cropping the image around the signature to be time-consuming and tedious.

Additionally, this new feature also works with PAN cards where the signatures are clear and visible in good lighting conditions. We hope that this new update will make the Sign Upload feature even more accessible and user-friendly for all our users.

April 10, 2023
Improvement
New Feature
Bug Fix
Sign Upload
Signing journey

April 2023

Stamp form updates

2 new fields have been added to the stamp form in the product i.e. a.) Purchased By - In case an intermediary is purchasing the stamps on someone's behalf b.) Stamp Duty paid by - This can be either one of the first party or the second party mentioned.

This is relevant for eStamp purchases for certain customers who act as intermediaries for their own customers.

April 8, 2023
Improvement
New Feature
Bug Fix
Stamp Procurement
Bharat Stamp

April 2023

Affix Multiple Revenue Stamps

An enhancement has been made to revenue stamps whereby you can now attach more than 1 revenue stamps to a document (which was earlier restricted to 1)

Things to note:

  • A new parameter has been added to API 2.1 create request - revenueStampQuantity, where the quantity of revenue stamps to be attached needs to be mentioned.
  • This parameter will appear in the excel template and API 3.0 create request when the workflow creator leaves this field blank (meaning it is to be filled at runtime)

In order to ensure backward compatibility "revenueStamp Quantity" if not passed will assume a value of 1 in the API since before this implementation customers did not need to pass this parameter to attach a single revenue stamp.

April 5, 2023
Improvement
New Feature
Bug Fix
Revenue Stamps
Bharat Stamp

March 2023

NeSL Non-Lending Flow

We are excited to announce the launch of the highly anticipated NeSL non-lending flow. This new feature allows banks to use NeSL for non-financial use cases such as-

  1. Opening escrow accounts
  2. Signing NDAs
  3. Opening bank accounts

Compared to Lending flows (Individual or Non-Individual), the NeSL non-lending flow does not contain any loan details (such as loan number, sanction number, and EMI amount) in its form. However, the Stamp Details and Invitee Details remain the same for Non-Lending flow.

In the sending journey, if NeSL eSign type is enabled for a signer, after the invite page, senders need to fill the NeSL form. This form will now have a new option called ‘Operational Creditor’. We’ll be changing this name to ‘Non-Lending’ soon, so stay tuned! This option corresponds to the non-lending flow.

A few things to keep in mind:

  1. Although this is the non-lending flow, while configuring ‘Contract Relation’ of the 1st invitee, NeSL has asked us to add Debtor as the value.
  2. In Non-lending flow, the 1st invitee can be both, an individual OR an organisation (depending on the usecase). Depending on the value of ‘Legal Constitution’ and ‘Official Doc ID’ in Invitee Details, validations such as Registered/ Communication Address/ pincode will either be mandatory or optional

Please note that the non-lending flow cannot be used with NeSL Lending Credentials configured for your organization. If you wish to enable the non-lending flow, please contact our Support Team to change your credentials.

March 28, 2023
Improvement
New Feature
Bug Fix
NeSL

March 2023

Webhook Profile IDs and Payload Encryption

In previous release of custom webhook headers, clients were enabled to add additional headers to the webhook calls for authentication purposes.

A. Profile IDs:

Please note, once configured we were appending these headers to all the webhook calls. But clients may require to:

1. add headers only to webhook call of certain documents/workflows

2. add different types of headers to different webhooks

To cater to these needs:

1. At the time of configuring webhook headers, a Profile ID would now be generated.

2. This Profile ID would be shared with the clients over a secure email.

3. Senders can add this Profile ID in workflows, new documents Flows or API calls.

4. Only the invitations having an associated Profile ID would have the mapped additional headers in the webhook calls

For APIs: this profile ID can be passed at this path: $.invitees[].webhook.profileId

For Co-ordiante Picker Webhook: path: $.coordinate_picker_webhook_profileId

For New Document and Workflow Configuration Flows: Go to Invitee Level Options > Add custom URLs and webhooks > Webhook Profile ID.

B. Payload Encryption:

The Webhook Payload can be encrypted as per the clients' request. The following steps are required for encryption

  1. Client shares their encryption request with a public key. This request would be configured in Leegality's system
  2. And a Profile ID would be generated against it 
  3. The sender can pass this profile ID (as mentioned in the section above)
  4. The webhook payload would be encrypted using the client's public key and will be sent in encrypted form during the webhook calls
  5. Clients will use the associated private key to decrypt the payload and access the information

A little bit about encryption

Payload Encryption provides another layer of security to webhooks. We have used AES (Advanced Encryption Standard) Encryption Algorithm with CBC (Cipher Block Chaining) mode to encrypt the payloads of the webhook.

Using the client’s public key, a 256 bits AES key is encrypted and then this AES key is used to encrypt the payload.

March 28, 2023
Improvement
New Feature
Bug Fix
Webhooks
Payload Encryption

March 2023

DocSigner Configurations

Now, whenever a customer wants to store their DocSigner Certificate on Leegality's server, they can do it by themselves without any support/ tech team involvement.

Background-

Currently, clients have 2 ways of configuring a DocSigner Certificate:

  1. Configure a Signature Certificate at the client's server end
  2. Configure a Signature Certificate on the  Leegality's server end

Till now, if a client wanted to configure their certificate at Leegality's server end, it required the customer to reach out to Leegality, and the doc signer was configured by Leegality’s team internally.

Now, we have provided a config for clients to seamlessly configure their Docsigner Certificate on Leegality's environment.

March 24, 2023
Improvement
New Feature
Bug Fix
Docsigner

March 2023

Audit trail download in activity logs

The activity logs for completed documents will now have a link to download the Audit Trail.  This link can be used to download the Audit Trail even after the document is deleted.

Using this functionality, customers can directly download audit trails from the dashboard without reaching out to our support team. 

The link will be accessible to the sender & invitees of the document, admins in the organization, and other users and CCs with whom the document has been shared.

March 14, 2023
Improvement
New Feature
Bug Fix
Audit Trail
Activity Logs

March 2023

NeSL Multi Document Support

We are excited to announce the latest addition to NeSL: The NeSL MultiDoc feature! This new feature allows users to send multiple documents with corresponding eStamps affixed just before each document, providing a more organized and user-friendly experience.

In the current process, all stamps are affixed together before the documents, which can be confusing for users who prefer the appearance of stamps affixed just before their corresponding document. With NeSL MultiDoc, each eStamp has a certificate number that is imprinted on the document it corresponds to, making it easy for users to identify which stamp corresponds to which document.

Note that you can attach multiple stamps to a single document.

Version 1 of this feature includes support in API 2.1 flow.

March 1, 2023
Improvement
New Feature
Bug Fix
NeSL

March 2023

Concurrent Login Restriction

Now concurrent logins from the same user ID (phone/email) will not be allowed for Dashboard logins.

March 1, 2023
Improvement
New Feature
Bug Fix
Concurrent Login

February 2023

Custom Webhook Header for Authentication

Previously, a standard webhook structure was available for communication of invitation status and signed documents.

Now, the clients wanting to authenticate the webhook calls from Leegality can add custom headers to these webhook calls according to their needs.

Why do we need it?

Authentication is a standard process, especially for API calls from outside systems. Currently, 'private salt' allows clients to authenticate these calls. Clients, due to reasons like compatibility with their existing systems, may want to authenticate headers as well. Previously, we have received such requests from SIB (using Nucleus), Tata AIG, Grant Thronton, etc.

This should improve the onboarding process for our clients and make it smoother.

What kind of parameters can be added to the headers?

Rather than allowing only a certain type of authentication method, we have productised this solution which is capable of supporting a wide variety of authentication from simple basic authentication via user ID and password to complicated OAuth2.0 via tokens. Clients can add both static and dynamic (fetched from an API) key-value pairs in the webhook headers

How to configure the headers?

Step 1: Clients can share their authentication requirements over a secure email.

For static fields, expected key-value pairs would be required.

For dynamic fields (API fetched), API documentation and expected key-value pair would be required.

Step2: We will configure these from the backend and inform the client of the expected response

Step 3: Once deployed, clients should expect all their webhook calls to have these additional headers

For dynamic parameters, an API call will be made to the URL (shared by client in the API documentation) to fetch the required parameters in real time and they will be added to the headers like in the case of static parameters.

February 15, 2023
Improvement
New Feature
Bug Fix
Webhooks

April 2023

Revenue Stamps Update | Multiple Revenue Stamps

A few months back, we rolled out support for Revenue Stamps, which is a unique category of stamps used for Demand Promissory Notes (DPNs) and other documents. We are now rolling out an upgrade which allows you to affix more than one Revenue Stamp for a document.

You can specify the number of revenue stamps you want to affix to your document when creating a new document via the dashboard or through APIs.

Dashboard Flows:

In the dashboard flows, you can specify the number of revenue stamps by entering the value in the "Number of Revenue Stamps" input field after enabling Revenue Stamps.

API Flows:
For API flows, a new parameter has been added to API 2.1 create request - revenueStampQuantity, where the quantity of revenue stamps to be attached needs to be mentioned.

In workflows, you can configure the revenue stamp quantity when creating the workflow, or alternatively pass the quantity when running the workflow via the dashboard or the API 3.0.

In order to ensure backward compatibility, if "revenueStamp Quantity" is not passed, we will assume a value of 1 in the API.

April 5, 2023
Improvement
New Feature
Bug Fix
Stamp
Revenue Stamps

January 2023

Revenue Stamps

We have launched a new module that affixes revenue stamps exclusively.

Things to note:

  1. You need to create a stamp series for Revenue Stamp
  2. Revenue Stamp will be available as a separate toggle once the stamp series is created
  3. You can only add Revenue Stamps to a document, they cannot be added to a group.
January 24, 2023
Improvement
New Feature
Bug Fix
Stamping

January 2023

Regional Languages

We have launched Regional Languages in the signing journey on the production environment! We now support the following 10 languages in the signing journey : India: - English, Hindi, Marathi, Gujarati, Kannada, Tamil, Telugu, Malayalam, Bengali, and Odia.

January 17, 2023
Improvement
New Feature
Bug Fix
Regional Languages

January 2023

API documentation loading issue

We’ve resolved the bug that was causing the API documentation to not open on some devices.

January 5, 2023
Improvement
New Feature
Bug Fix
API

December 2022

Improved NeSL experience - Email and SMS

In all NeSL flows (F2F and nonF2F), we will now send a Leegality email/SMS with the signing URL.

The signing URL will be visible on the Details Page and will also be received in the 2.1/3.0 API response. 

Things of note:

  • The email sent by Leegality with the signed URL can be customized and can support custom branding. You can offer this option to customers.
  • The instructions email has been removed from the flow since we are now directly sending the signing URL to the signer.
December 23, 2022
Improvement
New Feature
Bug Fix
NeSL

December 2022

SFTP Upgrades

We have made minor updates to SFTP- 

  1. Included IRN in the email which is triggered upon failure of transfer via SFTP.
  2. Added a subscript below the input parameter 'Destination'- 

Note: Please add a forward slash (/) after entering the destination

December 21, 2022
Improvement
New Feature
Bug Fix
SFTP

December 2022

Document and Stamp ID spillover issue

We’ve fixed the issue that made the document ID and stamps ID spillover on the document content when multiple stamps were attached to the document.

Now a maximum of 10 IDs will be digitally imprinted on the document and the rest of the stamp IDs will be available in the document properties.

December 16, 2022
Improvement
New Feature
Bug Fix
Stamping

December 2022

API for manual activation of invitations

We've added an API for the manual activation of invitations! This new API is a part of API 3.1-

https://docs.leegality.com/v3#tag/API-3.1/paths/~1v3.1~1invitation~1activate/put
This API can activate any inactive invite when required. When to use this - when an intervening signer is unable to sign but the sender wants other signers to proceed with signing.

December 11, 2022
Improvement
New Feature
Bug Fix
API

November 2022

Resend OTP Timer

Reduced the ‘Resend OTP’ timer from 60 seconds to 30 seconds on the Dashboard login page. This is to help improve the user experience while using the Dashboard.

November 20, 2022
Improvement
New Feature
Bug Fix
Signing journey

September 2022

New UI for NeSL

We have launched a new UI for the NeSL Forms and made improvements to make the form filling experience better for clients.

September 30, 2022
Improvement
New Feature
Bug Fix
NeSL
Dashboard

September 2022

Sign Upload

We have launched the Physical Signature Capture on production environment (app1).

Typically banks and other financial systems require that the drawn signature resembles closely to the signature in their records for approval. 

Signature upload will be one of the virtual signs that can be configured where a user will be able to upload a signature drawn on a plain white paper.

September 15, 2022
Improvement
New Feature
Bug Fix
Sign Upload
Virtual Signature

September 2022

API 2.1 - Update related to stamping and eSign coordinates

A new parameter has been added called "replicateStampCoordinates". 

If this parameter is passed as "true", then the eSign coordinates passed for page 1 will be replicated for all the stamp papers in the document.

This feature is useful for API integrations where customers have integrated the 2.1 API and need to pass page specific eSign coordinates, but who are unsure how many stamp papers will be added through group stamping. 

These customers can now pass "replicateStampCoordinates" as "true" and be assured that all stamp papers (regardless of how many get attached) carry the necessary eSign coordinates, without affecting eSign coordinates on other pages.

September 13, 2022
Improvement
New Feature
Bug Fix
Stamping
API

September 2022

CDSL support added to Aadhaar eSign (OTP)

We have integrated another ESP (CDSL) for the Aadhaar eSign (OTP) flow.

It will work similar to all other ESPs currently live including NSDL & Verasys with the same auto-switch functionality.

September 6, 2022
Improvement
New Feature
Bug Fix
Aadhaar eSign
Signing journey

August 2022

Contact Book

We have launched Contact Book on production environment (app1).

This will appear under MY DRAWER once access is enabled via Admin Panel.You can Add, Edit, and Share contacts within the organisation.

To add contacts:

  • Tick the checkbox while sending out invites and the contacts will be auto saved in your contact book. 
  • You can also manually add contacts or use excel upload to bulk upload contacts. 
  • You can label contacts and search by labels whenever needed 
  • You can just start typing and choose from a dropdown of contacts to select the relevant contact. 
  • Contacts from your organisation will be auto added in your Contact Book with the label "Organization" so you don't have to manually add your colleagues in the Contact Book
  • You can also share or send contact details to these "Organization" contacts so that the process of adding contacts become smooth and speedy for the entire organization. 
  • You can save a confidential contact as a secret contact in your contact book and others in the organization won’t be able to access or view it. 

Refer the knowledge bank article here for more info and screenshots: https://support.leegality.com/portal/en/kb/articles/contact-book

August 20, 2022
Improvement
New Feature
Bug Fix
Contact Book
Dashboard

July 2022

Optimised NeSL Support Flow

We have optimised NeSL Support flow by displaying Transaction ID to users. Transaction ID for NeSL Sign Invitations will be visible on the Details Page.

Previous Flow: 

  1. Whenever a client has any issue with an NeSL sign invitation, they would message Leegality's support team the document ID. 
  2. Support team would connect with Tech Team to get the Transaction ID for the aforementioned sign invitation. 
  3. This transaction ID would be shared with NeSL to understand the reason for this error. 
  4. NeSL's response would be communicated to the client. 

New Flow: 

Whenever a client has an issue with NeSL, the client can get the Transaction ID from the Details page and reach out to NeSL directly, without involving the support team & tech team 

OR 

  1. The client can share transaction ID with the support team. 
  2. The support team can then reach out to NeSL without involving the tech team.
July 22, 2022
Improvement
New Feature
Bug Fix
NeSL
Dashboard

June 2022

Bulk Cloud DSC

You can now eSign upto 5 documents in a single flow using Cloud DSC. This feature can be accessed when signing documents from the received folder (which have Cloud DSC type enabled).

June 16, 2022
Improvement
New Feature
Bug Fix
Cloud DSC
Dashboard
Received folder

May 2022

New Wallet

The wallet tab has been revamped with an all-new purchase & transaction history experience allowing users to purchase credits and stamps easily and view transactions seamlessly.

May 18, 2022
Improvement
New Feature
Bug Fix
wallet
Dashboard

May 2022

Multi-stamping functionality in NeSL flow

We have added Multi-stamping functionality in NeSL flow. Instead of generating just one stamp for every use-case, we can now generate multiple stamp papers.

A user can attach up to 10 eStamps having different values to the document for the NeSL sign instead of combining multiple stamp values into a single stamp paper. 

Multi-stamping is supported through Dashboard, API flow as well as excel flow.

Multi-Stamping solves for the following problems: 

  • When we upload multiple PDFs in the sending journey, they’re merged as one single PDF. 
  • If a client uploads 2 documents to be signed by NeSL eSign, the documents are merged into a single PDF, but the client will have to pay stamp duty for both the documents.
May 6, 2022
Improvement
New Feature
Bug Fix
NeSL
Stamping

March 2022

Reject Sign Invitations

Invitees can now reject sign invitations in the signing journey itself, and provide a message at the time of rejecting invitations.

This will enable senders to distinguish between sign invitations that the invitee does not want to sign and sign invitations that the invitee has not yet opened/ forgotten to sign. 

This also opens another channel of communication between senders & invitees - messages which would have to be communicated offline can now be communicated inside the Leegality app.

March 21, 2022
Improvement
New Feature
Bug Fix
Signing journey

March 2022

NeSL Stamping Update

Kerala has been added to the list of states that support NeSL eStamping.

March 17, 2022
Improvement
New Feature
Bug Fix
NeSL
Stamping

March 2022

ePass token support on MacOS

ePass tokens are now supported on MacOS for the DSC & Bulk DSC flows.

March 13, 2022
Improvement
New Feature
Bug Fix
DSC

March 2022

Verification Details on Dashboard

You can now check verification details on the dashboard. If verification is enabled for Aadhaar, DSC, Cloud DSC or NeSL, you will be able to view whether the verification was a success or a failure, and what was the parameter that caused the failure (if any).

You can also view the digital sign certificate in case the sign is successfully applied to the document. 

Note: This will be applicable only to new invitations created henceforth.

March 4, 2022
Improvement
New Feature
Bug Fix
Dashboard
eSign verification

February 2022

Update to the coordinate picker webhook

The mac parameter has been added to the webhook. This allows users to verify that the webhook call is coming from Leegality's servers. 

See more: 

https://docs.leegality.com/webhooks_resources#tag/Coordinate-Picker-Webhook

February 20, 2022
Improvement
New Feature
Bug Fix
API
Webhooks

February 2022

Revamped Notification Tab

The Notifications Tab of the dashboard has been revamped to make it more user-friendly and self-serviceable.

February 16, 2022
Improvement
New Feature
Bug Fix
Dashboard

February 2022

Updates regarding NeSL

1. NeSL eSign is now supported on the 2.1 API as well.

Look out for the parameter called neslData in the API documentation: https://docs.leegality.com/#tag/eSigning-Gateway/paths/~1sign~1request/post

2. NeSL e-stamp support has now been extended to a total of 19 states including West Bengal & Madhya Pradesh.

February 7, 2022
Improvement
New Feature
Bug Fix
NeSL
Stamping
API

January 2022

New Details API (v3.1)

We have rolled out a new version (v 3.1) of the Details API. 

The 3.1 Details API is a powerful & flexible API that can be used to fetch all data & files related to documents sent/signed using Leegality. 

Notable improvements:

1) The new API covers a number of fields which were previously not covered in our Details API, including fields pertaining to new features like CC, Cloud DSC, Reviewer Rejection & Invitee Groups. 

2) The new API has been designed in a way that is highly scalable - when new fields are added in the future, we can simply upgrade the API without affecting existing integrations. This is expected to improve the roll-out time of new features being added to the Details API in the future. 

3) The new API is highly flexible - clients can pick & choose exactly those data points they want to receive, while ignoring the rest. 

Link: https://docs.leegality.com/v3#tag/API-3.1/paths/~1v3.1~1document~1details/get

January 29, 2022
Improvement
New Feature
Bug Fix
API

January 2022

New Settings Tab

We have also released a revamped version of the Settings Tab on Production. 

This will take care of several visual inconsistencies and improve usability and self-servicibility.

January 11, 2022
Improvement
New Feature
Bug Fix
Dashboard

December 2021

Upgrade to Reviewer role

In workflows which have at-least 1 reviewer, there will be an option under "Advanced Options" called "Prevent Changes to Signing Order".

When this toggle is enabled at the time of creating a workflow, the workflow runner will not be able to manually activate invitees or delete invitees. 

This will ensure that signers in the signing order after a reviewer will only be able to sign if the reviewer approves the document. 

This feature has been developed to enhance the robustness of the reviewer feature, and then solidify its use case as a "maker-checker". 

Note 1: This feature will be available to all clients who have reviewers enabled. 

Note 2: This feature is specific to workflows. Its not available in the New Document Flow/ API 2.1.

December 21, 2021
Improvement
New Feature
Bug Fix
Reviewer
workflows

December 2021

Auto-fill duplicate text fields in Templates

You can now create text-boxes using our template generator in a way that filling one text box automatically fills a number of other text boxes.

This will work for small textboxes and large textboxes. 

This upgrade is targeted towards template use cases where certain text fields (like name or address) are repeated in several places in a document. 

The new upgrade will allow users to easily fill multiple boxes with the same input value. 

This is a dashboard only feature without any changes to APIs or Excel Upload. A demo video will be released shortly.

December 19, 2021
Improvement
New Feature
Bug Fix
Templates

December 2021

Coordinate Picker

'Coordinate Picker' feature have been introduced in the Leegality application.

This feature can be enabled for a particular organisation from the Config in Admin panel and then can be configured through

Accounts >>Department>> Invitee configs. 

The Coordinate picker sender can drop custom coordinates on the document before sending it to invitees via both Leegality Helper or SDK. 

Coordinate Picker feature is currently live for API 2.1 on Sandbox.

December 5, 2021
Improvement
New Feature
Bug Fix
API

November 2021

Custom Messages

In the signing journey, an alert will be shown for message in the left corner when custom message is added by the sender same as that for the invitees.

November 17, 2021
Improvement
New Feature
Bug Fix
Signing journey
Signing Add-ons

November 2021

Custom Branding

Custom colour issue for the department: Earlier Sign button and the loading bar in the signing journey had the default colour (blue) irrespective of the colour set for the department. Now the button and the loading bar in the signing journey will have the custom colour set.

November 10, 2021
Improvement
New Feature
Bug Fix
Signing journey
Custom Branding

November 2021

Date Filter in Document Listing

Custom date range issue on the Document Listing page: Earlier when the custom date range was set by the user, then the dates on the listing screen disappeared and the documents were shown for All Dates. Now the exact date range is shown and the documents are listed as per the range set by the user.

November 5, 2021
Improvement
New Feature
Bug Fix
Dashboard

November 2021

Account Tab in Dashboard

Earlier when the logged in user switched the user from shared accounts and navigates to Accounts>> Department, then Activity logs were shown. Now the fix has been done and the logged in user can see all tabs under Department tab.

November 3, 2021
Improvement
New Feature
Bug Fix
Dashboard

November 2021

Received Folder in Dashboard

Document listing fix: Earlier when a document(with signing order enabled) was received to a single invitee multiple times, then multiple rows of the same document was shown in the Received folder although one of the logged in user was inactive. Now the fix has been done, only a single row of the

Document will be shown in the received folder for which the logged in user is active

November 2, 2021
Improvement
New Feature
Bug Fix
Dashboard

November 2021

New Feature: Reviewer Rejection Comments

Much awaited feature 'Reviewer Rejection comments' is now live.

With this feature, the reviewer will have the capability to add a comment when the document is rejected. And this message will be reflected in the following: 

(i) Invitee details on the Document details page 

(ii) Signing update and Document completion mails triggered to the Reviewer, Sender and CC.

November 1, 2021
Improvement
New Feature
Bug Fix
Reviewer

October 2021

DSC Sign Verification

Earlier, DSC Name and SmartName verification validations were not handled in the Dashboard. Now, the checks have been added, and it is matched with the certificate details.

October 22, 2021
Improvement
New Feature
Bug Fix
eSign verification
DSC

October 2021

Group Invitation Notifications

Group invitations - Post completion message has been updated.

When the signer/reviewer accesses the URL after the group is completed, the message shown was:

"You do not have access to this URL". 

Now, the message has been updated to:

"This group invitation is already complete".

October 19, 2021
Improvement
New Feature
Bug Fix
Group Invitations

October 2021

Stamp APIs

1. API to fetch Stamp Consumption details - New field 'Expired' has been added which signifies the number of stamps expired in every stamp series.

Earlier, all the expired stamps were shown in the 'unused' column under stamp details. 

2. API to show expiry date of stamps - This API will show the list of stamps which are going to expire. 

This API has two request parameters - 'lookUpPeriod' and 'includeExpired'.

“LookupPeriod” defines the timeframe for checking stamp expiry. The default value of 'lookUpPeriod' is 30, which will show the stamps which will expire in 30 days.

“includeExpired” defines whether you want to get data of stamps which have already expired.  The default value is false, which will exclude the stamps which are already expired.

Documentation: https://docs.leegality.com/v3.1#tag/API-3.1/paths/~1v3.1~1series~1expiry/get

October 14, 2021
Improvement
New Feature
Bug Fix
API
Stamping

October 2021

Biometric Virtual Sign feature live

The biometric virtual sign feature is live on app1.

Customers can use the MantraMFS 100 biometric device to apply an electronic fingerprint as part of the virtual sign journey. 

The flow has been implemented for New Document, Workflow, and API flows.

October 9, 2021
Improvement
New Feature
Bug Fix
Fingerprint Virtual sign
Signing journey

October 2021

Issue with Email Customization resolved

Issue: When Email Customization (signer specific emails) is done for a client, signer mails were triggered in the case of Reviewer also.

This issue has been resolved now and default set of Reviewer notifications will be triggered when none of Emails are customized for Reviewer. The fix has been deployed on App1.

October 4, 2021
Improvement
New Feature
Bug Fix
Custom branded emails
Reviewer
Notifications

October 2021

Fixes on Sandbox and App1

1. When Custom mapped excel was uploaded by the user, the values for the fields Radio button and Check box were not filled out in the generated Document. Although, the values were correctly filled out in the Document when Excel was upload without custom mapping. 

This issue has been fixed now for Custom mapping.

2. When a stamp group is used, we specify the Group name as well as the Stamp Value in the API payload.

But in the Audit trail ( of completed document), it showed Stamp value as the Stamp series (series added in the stamp group). 

Suppose a stamp group PB01 has stamp series 01 (denomination 50) and the Stamp value entered was 200. Then in the final document, there were 4 stamp pages but in the Audit trail - the field Stamp value was equal to 50 (instead of 200). 

This issue has now been fixed.

October 2, 2021
Improvement
New Feature
Bug Fix
Custom mapping in workflows
Dynamic stamping
Audit Trail

September 2021

API documentation updated for CC and Cloud DSC

API documentation has been updated for CC and Cloud DSC. 

Notes: 

1) The following APIs have been updated: API 2.1 (create eSign request), API 3.0 (create eSign request), Success & Error Webhooks, Details API 3.0, Transaction Status API, and Reactivate Expired Documents API. 

2) Cloud DSC will be referred to as "Offline_Sign" in the APIs due to technical reasons. Appropriate explanations are being added to the documentation for ease of reference. 

3) API 2.1 support for Cloud DSC does not support the option to fix signer ID at the moment.

September 21, 2021
Improvement
New Feature
Bug Fix
API Documentation

September 2021

CC Feature

CC Feature is live on app1

September 17, 2021
Improvement
New Feature
Bug Fix
CC

September 2021

Fixes on app1

1. The wording for sign type 'eMudhra' has been changed from "Offline sign" to "Cloud DSC". 

The change will be reflected in the Dashboard settings, Sending journey, Details page, Activity logs, Audit trail as well as the Signing journey.

2. Earlier only jpg format of image file was supported in the Image dynamic field within the template (in Safari browser). Now it supports both .jpg and .png formats of images.

September 15, 2021
Improvement
New Feature
Bug Fix
Template engine
Cloud DSC

September 2021

Cloud DSC

Cloud DSC (emudhra) is supported on both API 2.1 and API 3.0.

September 9, 2021
Improvement
New Feature
Bug Fix
Cloud DSC
API2.1
API 3.0

September 2021

Cloud DSC

eMudhra is live on Production environment

September 3, 2021
Improvement
New Feature
Bug Fix
Cloud DSC

August 2021

Fixes on app1

1. Earlier when the stamp expiry was extended, the page did not refresh automatically. Now, the issue has been handled, on extending the expiry - page will be refreshed. 

2. When the extend expiry button is pressed, an alert should pop up for confirmation added before extending the expiry of stamps to prevent accidental clicks.

A confirmation pop-up with message "Are you sure? - Do you want to extend the expiry?" has been added. 

3. Earlier only webhook version 2.1 was supported in the New Document Flow and all versions were supported on the Workflow. 

Now, all webhook versions - 2.1, 2.2 and 2.3 are also supported in the New document flow same as that in the Workflow.

6. There was an issue while loading the template with header and footer. Quite lengthy templates when coupled with the header and footer the document generation failed in the Document creation and signing journey. 

We have optimized the method through which it would be much less time taking. But, if the template has current page number in the header or footer then it might take some time.

August 28, 2021
Improvement
New Feature
Bug Fix
Dashboard
Webhooks
Template engine

August 2021

CC invitees

A new category of invitees has been added named CC. 

The purpose of CC invitee is to keep a track of

all the document related activities.

CC feature can be enabled for a particular organisation from the Config in Admin panel and then through Account level settings. 

CC feature is currently live for New Document flow on Sandbox.

August 14, 2021
Improvement
New Feature
Bug Fix
CC
Notifications
Sandbox

August 2021

Fixes on app1

1. When a reviewer is completing its reviewingjourney, default sign coordinates were being shown, which was misleading for the clients, as a reviewer actually does eSign the document. 

Therefore, in order to remove the conflict, eSign coordinates have been removed from the reviewer journey. 

2. When a document was being created with a stamp group containing expired stamp series, then a non-stamped document was getting created, instead of an error being shown. 

This has been fixed --> an error message will now be visible on the Front End saying "Insufficient stamps in the stamp group to create desired stamp value". 

This check has been added in the New Document flow, Workflow, API 3.0 and API 2.1. 

3. Earlier when hyperlinks were added in the template header or footer, then document generation failed in both sending and signing journey. 

In order to avoid this issue, the hyperlink functionality has been removed from header and footer in both Dashboard and Admin panel. 

4. Earlier the stamp series list had columns - total, reserved, used, unused, blocked, and process. But the expired stamps were not included in any of these columns, making it difficult for the user to figure out the no. of expired stamps. 

Therefore, an Expired column has been added on the stamp series listing screen. This feature was previously added on for Client Dashboard and has now also been added in Admin panel.

August 11, 2021
Improvement
New Feature
Bug Fix
Reviewer
Signing journey
Dynamic stamping

August 2021

Fixes on Sandbox and app1

1. Earlier the clients were getting confused between the Sandbox, App1 environment, and were using Sandbox environment for Production activities. In order to make it more evident, we have added a banner on the top which clearly says "Testing Environment" across all screens (on the Sandbox environment).

The fix has currently been deployed on Kepler (signing journey) and will soon be launched in the Sending journey.

2. Issue that rate of Interest field did not take decimal value. Now, the validation has been changed and can accept decimal values upto 2 decimal places. 

3. The custom consent length has been increased from 500 to 1000 characters. 

4. Few of the labels(Invitee level configs and Signing journey options) in Workflow and New document flow were different. Therefore, to make it alike and more user friendly label changes have been made in Workflow(same as New Document Flow). 

5. Clients faced an issue where users with many sign invitations had to login and logout multiple times. Therefore, in order to avoid login and logout, we have integrated Web SDK in Dashboard. 

When sign/approve button is clicked from Document details page or Document listing page(Received tab), the user will be redirected to a New Tab to complete the signing jouney. Once the signing is completed, the window will automatically close and the parent window data will be refreshed. 

August 6, 2021
Improvement
New Feature
Bug Fix
NeSL
Sending journey
Dashboard

August 2021

NeSL

NeSL is live on app1

August 3, 2021
Improvement
New Feature
Bug Fix
NeSL

August 2021

Updates on app1

Currently, proforma invoices for stamp paper orders are generated in a cumulative format containing both the BOS and the service charges part in the same invoice. Now, proforma invoices will be split into 2 parts in case there is a stamp paper order - BOS and Service charges proforma will form 2 pages of a single pdf 

Note: any other taxable items will be included in the Non-BOS proforma

August 1, 2021
Improvement
New Feature
Bug Fix
Billing & Invoicing

July 2021

Documentation for NESL

Documentation for NESL has also been published.

July 27, 2021
Improvement
New Feature
Bug Fix
NeSL

July 2021

Update on NeSL eSign

NeSL eSign has been deployed on the sandbox environment.

July 25, 2021
Improvement
New Feature
Bug Fix
NeSL

July 2021

Update to Face Capture

An instruction has been added to Face capture steps

July 21, 2021
Improvement
New Feature
Bug Fix
Face capture
Signing journey

July 2021

Feature to flatten

Feature to flatten is live on app1. 

We can enable this feature in Accounts>> Department >> Document Configuration >> Toggle on "Enforce conversion of Editable PDFs into Uneditable PDFs.

If the toggle is enabled and any document is created from either New document flow or workflow, the final document will be flattened/non-editable. 

NOTE: This feature has been disabled for existing clients. It will be automatically enabled for new users.

July 14, 2021
Improvement
New Feature
Bug Fix
PDF flattening
Sending journey

June 2021

Multi PDF support in API 2.1

Multi PDF support in API 2.1 has been deployed on app1. 

https://docs.leegality.com/v2#tag/eSigning-Gateway/paths/~1sign~1request/post

June 29, 2021
Improvement
New Feature
Bug Fix
Sending journey
API
Multi-PDF

June 2021

Postman Collection

Postman Collection has been updated with all the new

June 23, 2021
Improvement
New Feature
Bug Fix
API
Postman

June 2021

Update

1. Upload file limit exceeded to 15MBs. Earlier the upper limit to upload files in document creation was 9 MBs. 

Minor fixes deployed on app1:

1. Mandatory check for Radio button and checkbox in the signing journey. 

2. Image upload issue in the sending journey

June 19, 2021
Improvement
New Feature
Bug Fix
Sending journey

June 2021

MFA

MFA is live on app1

June 17, 2021
Improvement
New Feature
Bug Fix
MFA
Document security

June 2021

Updates

1. Radio button deselect issue in the Sending journey.

2. Label should not be repeated for the same group of Checkbox/Radio button in the Signing journey. 

3. Documentation published for POST - Create an eSigning request from API 2.1

(a) Smartname Verification Request > invitees > Signatures > config > verifySmartName 

(b) Two Factor Authentication Request > invitees > twoFactorAuthentication

June 15, 2021
Improvement
New Feature
Bug Fix
Sending journey
Signing journey
API2.1

May 2021

Documentation published

1. Expiry date format changed in POST request- Create an eSigning Request. Response Schema > Data > expiryDate

2. Attachments description changed for GET - API to check document details. 

(i) Response Schema > Data > Attachments (attachments uploaded by sender)

(ii) Response Schema > Data > Invitations > Attachments (attachments uploaded by the invitee in the signing journey).

May 30, 2021
Improvement
New Feature
Bug Fix
API

May 2021

Fixes on App1

1. Active Status flag inside the invitee details window on the Document details page. 

2. Radio button name disappearing in the Signing journey.

May 21, 2021
Improvement
New Feature
Bug Fix
Signing journey

May 2021

Update: Default coordinates when more than 30 invitees

If a document is uploaded with more than 30 invitees in the New Document Flow, the default coordinates will be placed only for the first 30 invitees. However, the sender will be able to manually configure coordinates for all invitees.

A message explaining the above will pop-up on the coordinates setting page in such a scenario. 

This change has been implemented to facilitate smooth loading of documents even in situations where a large number of invitations have been configured.

May 11, 2021
Improvement
New Feature
Bug Fix
Sending journey
Custom Coordinates

May 2021

Update to APIs

1) Deleting a Sign Invitation: This API allows for deletion of individual invitations, without deleting a document as a whole. 

Earlier, we provided API support only for deleting the entire document. 

Link: 

https://docs.leegality.com/v3#tag/eSigning-Gateway/paths/~1sign~1request~1invitation/delete

2) Manual Completion of Documents: This API allows for manual completion of documents, which do not have any pending eSigns. 

Link: https://docs.leegality.com/v3#tag/eSigning-Gateway/paths/~1sign~1request~1complete/post

May 10, 2021
Improvement
New Feature
Bug Fix
API

May 2021

Update: Mandatory fields check for Workflow Run

Mandatory fields check added for Workflow Run has been deployed on all Sandbox and App1

May 8, 2021
Improvement
New Feature
Bug Fix
workflows

May 2021

Update: Support for various fonts

Support for various fonts in the template has been deployed on Sandbox and App1

May 6, 2021
Improvement
New Feature
Bug Fix
Template engine

May 2021

Documentation for Group Invitee

The Documentation for Group Invitee has been published. 

https://docs.leegality.com/v3

May 3, 2021
Improvement
New Feature
Bug Fix
Group invitee
API 3.0
workflows
No results found
Clear Search