Versions Compared

Old Version 16

changes.mady.by.user Technical writer

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

transaction events for external role

accounts or external

accounts or external personal identities as they represent another organisation.

500
  • An unexpected error occurred: JSON parse error: [...]
  • An unexpected error occurred: Type definition error: [...]
These error messages are returned if one or more parameters are of the wrong type.

Steps

  1. Submit a request in accordance

with the

  1. with the details in Open transaction as a platform-managed user.

  2. The platform

performs the following validations:If the participant of

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

    1. that the transaction is specified in the TransactionRequest.

    2. that participant's access to the transaction is not revoked.

Info

Refer to the REVOKE attribute of Service for more information.

If

c. that the transaction can be opened and is not locked.

Info

Refer to TIMELOCK_BEFORE and TIMELOCK_AFTER

of 

attributes of Service for more information.

The

  1. ​The platform opens the transaction.

  2. The platform

archives

  1. updates the opened status of the transaction

along with

  1. in the

timestamp

  1. archive.

  2. The platform returns the TransactionMessageResponse.

Plantuml

Error messages Moved to API endpoint page

ExpandtitleHTTP status codeMessageComments400The application with the specified key could not be found400Input not valid: Participant can not be null.This error message is returned if the 'user' parameter of ManagedUserTransactionRequest is missing.400Input not valid: Transaction can not be emptyThis error message is returned if the 'transaction' parameter of ManagedUserTransactionRequest is missing or is empty.400An error has occurredThis error message is returned if the transaction data of ManagedUserTransactionRequest is not in the correct format.400Input not valid: Participant can not be of unknown type: null

This error message is returned if

400Input not valid: Participant corporateId can not be null for corporate or server user.400

Input 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.400Unknow errorThis error message is returned if a wrong 'type' is specified for User. For example, a CORPORATE type is mentioned as SERVER.


Plantumlcloud
toolbarbottom
filenamePlantUML Diagram 1.svg
originalHeight308
datanVTBbtswDP0aYycPitwMvTpOih2yLVh3LxiLToTIkifJ2bCvH2llqaO22DDbCIzHx8dHinFxJ0IEH8feFKJ+9w37wUDEoqoLKZZP8kkwvL5CdFflYlFKxsNJ2wE89BRQ2MFo4oOz8TP0SMhHNGeMuoWM+YjfR7QtfsIQ4IC10QdLcIs2os+4X91oVeO8pYgUi2UW3pFz3eoBbFw5r9A3zjhm7g20p7zuEZT7oe2B3jswAV+IKZWieZkH58gat/ZHv5CVmK43mY/6Fw9hIYmRkcJlAO+3usOttrgiswefWr3q4z3ff029aXtui56jVuyhI1N79zNhw/PIpgRZD4OhQ4ra0SlIwiDQz3ZTJ71GrO/X8rXELXnRlnSl4J3pnO/nArtL/of1ZtP8cz55nGss/k9kdSMiM5HnyYzWaHtClUBooz7zpqf2RZ2GUBbVJjU0/QO+DMjrGj3YwBk8tlQJZibKHiwtt+IiYVrrufouFZxmlMnv0HM+653BaDUdTHiDzF5CZuZ1Zu3boz5jTpZCd+w87cDesDuw7LpYNnYcqHzKOXLEUTlUJX0w4siottcQJP1LX2l5qqbMvE7zuDVLj8J8NrfIdBbFnUCr6DP1Gw==
compressedtrue
originalWidth615
revision3