This parameter defines the time at which the signature is made; the different times that can be defined are: 

SignStep: Begin

  • Description: The signature will be performed in the first step, serving as acknowledgement and authentication before displaying any content.
  • The process depending on whether the EviSign has attachments or not is as follows:
    • Without attachments: Acknowledgement of receipt + Identity verification ⇒ Acceptance/Rejection of the main document.
    • With prior attachments (Prior information): Acknowledgement of receipt + Identity verification ⇒ Prior information ⇒ Acceptance/Rejection of the main document.
    • With subsequent attachments (Attachments): Acknowledgement of receipt + Identity verification ⇒ Acceptance/Rejection of main document ⇒ Acceptance/Rejection of subsequent attachments.
    • With previous and subsequent attachments: Acknowledgement of receipt + Identity verification ⇒ Acceptance of previous information ⇒ Acceptance/Rejection of main document ⇒ Acceptance/Rejection of subsequent attachments.

SignStep: BeforeDoc

  • Description: The signature shall be performed at a step before the main document is displayed.
  • The process depending on whether the EviSign has attachments or not is as follows:
    • Without Attachments: Identity verification ⇒ Acceptance/rejection of the main document.
    • With previous attachments (Prior information): Prior information ⇒ Identity verification ⇒ Acceptance/Rejection of the main document.
    • With subsequent attachments (Attachments): Identity verification ⇒ Acceptance/Rejection of main document ⇒ Acceptance/Rejection of subsequent attachments.
    • With previous and subsequent attachments: Pre-information ⇒ Identity verification ⇒ Acceptance/Rejection of main document ⇒ Acceptance/Rejection of post-attachments.

SignStep: AfterDoc

  • Description: The signature shall be performed during the reading of the main document.
  • The process depending on whether the EviSign has attachments or not is as follows:
    • Without attachments: Acceptance/rejection of the main document.
    • With previous attachments (Prior Information): Prior Information ⇒ Acceptance/Rejection of the main document.
    • With subsequent attachments (Attachments): Acceptance/Rejection of main document ⇒ Acceptance/Rejection of subsequent attachments.
    • With previous and subsequent attachments: Previous information ⇒ Acceptance/Rejection of main document ⇒ Acceptance/Rejection of subsequent attachments.

SignStep: End

  • Description: The signature shall be performed in the last step.
  • The process depending on whether the EviSign has attachments or not is as follows:
    • Without attachments: Acceptance/rejection of the main document.
    • With previous attachments (Prior Information): Prior Information ⇒ Acceptance/Rejection of the main document.
    • With subsequent attachments (Attachments): Acceptance/Rejection of main document ⇒ Acceptance/Rejection of subsequent attachments.
    • With previous and subsequent attachments: Prior information ⇒ Acceptance/Rejection of main document ⇒ Acceptance/Rejection of attachments.

Edit NOTE: Do not mix the "SignStep" parameter with the obsolete "SignDelivery" parameter.

Exceptions to SignStep behaviour

As stated in the EviSign help page, the SignDelivery parameter is deprecated as of August 2018.

The behaviour of mixing SignStep and SignDelivery (when it was not deprecated) was as follows:

  • SignDelivery = true and SignStep = Begin, will result in SignStep = BEGIN.
  • SignDelivery = true and SignStep is not reported, will result in SignStep = BEGIN.
  • SignDelivery = false and SignStep is not reported, will result in SignStep = AFTERDOC.
  • SignDelivery = false and SingStep = (BeforeDoc, AfterDoc, End), will result in the value chosen in SignStep.
  • The following cases will raise an exception as they are not compatible:
    • SignDelivery = true and SignStep = (BeforeDoc, AfterDoc, End).
    • SignDelivery = false and SignStep = Begin.

This information is included as part of the compatibility of SignStep and SignDelivery, but remember not to use SignDelivery with SignStep.


  • No labels