Versions Compared

Old Version 7

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

Saved on

compared with

New Version 8

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. If archiving these transactions is needed , it must be tended to by the application.


Steps

  1. Submit a request as per the details in Create transaction as a platform-managed user.
  2. Lequinox platform signs the create transaction request message on behalf of the platform-managed user.
  3. Lequinox platform creates the transaction.
  4. Lequinox platform archives the transaction details along with timestamps.
  5. TransactionResponse is returned.


Plantuml


Error messages

Expand
title


HTTP status codeMessageComments
400Invalid role ID formatThe parameters 'corporateId' or 'applicationAccessId' or 'privateId' in User is incorrectly formatted.  User can be either a 'creator' or 'participant' of ManagedUserCreateTransactionRequest.
400Input not valid: Attachment fileName can not be emptyThe parameter 'fileName' is missing in Attachment of ManagedUserCreateTransactionRequest
   400Input not valid: Attachment content can not be emptyThe parameter 'content' is missing in /wiki/spaces/LPDA510/pages/1804247of ManagedUserCreateTransactionRequest
400Input not valid: Participant can not be of unknown type: null

This error is returned when

Participant can refer to either 'creator' or 'participant' parameter of ManagedUserCreateTransactionRequest

400Input not valid: Participant corporateId can not be null for corporate or server user. Participant can refer to either 'creator' or 'participant' parameter of ManagedUserCreateTransactionRequest
400Input not valid: Participant applicationAccessId can not be null for private or corporate user.Participant can refer to either 'creator' or 'participant' parameter of ManagedUserCreateTransactionRequest
400Input not valid: Participant privateId can not be null for private or corporate user.Participant can refer to either 'creator' or 'participant' parameter of ManagedUserCreateTransactionRequest
400Managed identity was not foundThe parameters 'corporateId' or 'applicationAccessId' or 'privateId' in User is incorrect. User can be either a 'creator' or 'participant' of ManagedUserCreateTransactionRequest.
400Input not valid: Creator can not be empty
400Input not valid: Participant list can not be empty
400Input not valid: Service package can not be empty
500An unexpected error occurred: null

This error is returned when

500

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

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

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