Versions Compared

Old Version 15

changes.mady.by.user Technical writer (Unlicensed)

Saved on

compared with

New Version 16

changes.mady.by.user Technical writer (Unlicensed)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.


Info

The Lequinox platform does not archive transactions for external role accounts or external personal identities as they represent another organisation.


Info
Submitting the request Sign transaction as a platform-managed user gives the transaction the status ‘Opened’ and ‘Signed’, even if the application does not call the Open transaction as a platform-managed user first.


Steps

  1. Submit a request in accordance with the details in Sign transaction as a platform-managed user.
  2. The platform checks if the participant of the transaction is revoked. Refer to REVOKE of validates the request by verifying, among other things:

    1. whether or not the participant's access to the transaction has been revoked.

      Info
      Refer to the serviceType ‘REVOKE’ in the API endpoint /wiki/spaces/LPDA510/pages/1804140.
    Revoked
    1. A revoked participant cannot sign the transaction.
    The platform checks if


    2. whether or not the transaction can be opened and signed

    and is not locked.

    1. .

      Info
      Refer to TIMELOCK_BEFORE and TIMELOCK_AFTER
    of
    1. in the API endpoint Service.


  3. The platform signs the transaction on behalf of platform-managed user.
  4. The platform archives the signed sign status of the transaction along with the timestamp.
  5. The platform returns the ParticipantStatusResponse.


Plantuml