Versions Compared

Old Version 2

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

Saved on

compared with

New Version Current

changes.mady.by.user Technical writer

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

for

as a platform-managed user

will give

 gives the transaction the status ‘Opened’ and ‘Signed’, even if the application does not call the Open transaction

for

as a platform-managed user first.

Steps

  1. Submit a request

as per the

  1. in accordance with the details in Sign transaction

for

  1. as a platform-managed user.

Lequinox platform checks if the participant of the transaction is revoked. Refer to REVOKE of /wiki/spaces/LPDA510/pages/1804140. Revoked

  1. The platform validates the request by verifying, among other things:

    1. that the transaction is specified in the TransactionRequest.

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

Info

Refer to the serviceType ‘REVOKE’ in the API endpoint Service. A revoked participant cannot sign the transaction.

Lequinox platform checks if

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

and is not locked.

.

Info

Refer to TIMELOCK_BEFORE and TIMELOCK_AFTER

of Service.It then

in the API endpoint Service.

  1. The platform unlocks and opens the transaction to sign.

  2. The platform signs the transaction on behalf of platform-managed user.

Lequinox

  1. The platform

archives

  1. updates the signed-status of the transaction

along with

  1. in the

timestamp

  1. archive.

  2. The platform returns the ParticipantStatusResponse

is returned

  1. .

plantuml

Plantumlcloud

Error messages

toolbar

expand

bottom

titleHTTP status codeMessageComments400Unknown error

This error is returned when

400Input not valid: Transaction can not be emptyThis error is returned when the parameter 'transaction' is missing in ManagedUserTransactionRequest.400Invalid role ID formatThe parameters 'corporateId' or 'applicationAccessId' or 'privateId' in User is incorrectly formatted. 400Input not valid: Participant can not be null.This error is returned when the user parameter is not mentioned in ManagedUserTransactionRequest.400

Input not valid: Participant can not be of unknown type: null

This error is returned when

  • The participant is empty.
    • The parameter 'type' is missing from User (participant).
400Input not valid: Participant corporateId can not be null for corporate or server user.400Input not valid: Participant applicationAccessId can not be null for private or corporate user.400Input not valid: Participant privateId can not be null for private or corporate user.400Managed identity was not foundThe parameters 'corporateId' or 'applicationAccessId' or 'privateId' in User is incorrect. 500

An unexpected error occurred: Type definition error: [...]

An unexpected error occurred: JSON parse error: [...]

These errors are returned if one or more parameters is of the wrong type.

filenamePlantUML Diagram 1.svg
originalHeight358
datanVTBbtswDP0aYycPstIUvTpOih2yNli6c6FadCJEplxJzoZ9/SipS22txYrZRhCQ7z0+UrSLK+a8sH7sdcHqTw/QD1p4KBZ1wdnykT+yEF5fQnQvyqoqeYi7k8JBWNFTQkInRu1vDfo70QNFvoA+g1etyJB7eB4BW/gKzokD1FodkMItoAebYb+ZEWVjLFKGs2qZpXfkXLVqEOhXxkqwjdEmIJ+0aE953aOQ5ofCA/3vhHbwl5iUKZuXuTWGrIXW/ugXfMHi9S5yr36FIVScEBnIvQzg81Z1sFUIKzJ7sKnViz7chPuf1FnbU1v0HJUMHjoy9WR+ptjwOrJI4PUwaDokrwydAqeYcPSz3dRJr2HrmzV/i7glLwpJl7OwM52x/VRg98K/Xm82zYf55HGqUf2fyGomwjOR18mMqBWeQKagaL06h01P7bM6DaEsFpvUUHwD9mldvRXoAiOMLVUSExNlL5CWW4YiLq71VH2XCsYZZfI7sIEf9M5CKxkPxr0Dvh8AXWbmbWRw/THk94FqQsQeg1lHTJAlfSX8GKKmC+NcNpjS8zkovPCEbY/qDKlTC360Ifcwg19Eu7i+09ONNAn51OaReErFFQOU9AH7DQ==
compressedtrue
originalWidth545
revision3