Versions Compared

Old Version 11

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

Steps

  1. Submit a request in accordance

with the

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

  2. The platform validates the request.

    1. that participants are specified.

    2. that participants are of a known type.

Info

Refer to the attribute ‘type’ in User for more information.

c. if attachments are specified, that file names and content are provided.

  1. The platform signs the create transaction request message on behalf of the platform-managed user.

  2. The platform creates the transaction as the platform-managed user.

  3. The platform archives the transaction details along with timestamps.

  4. The platform returns the TransactionResponse

is returned

  1. .


Plantumlplantumlcloud
Error messages
toolbar
expand
bottom
titleHTTP status codeMessageComments400Invalid role ID formatThe parameters 'corporateId' or 'applicationAccessId' or 'privateId' in User is not in the correct format.  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 ManagedUserCreateTransactionRequest400Input 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 ManagedUserCreateTransactionRequest400Input not valid: Participant applicationAccessId can not be null for private or corporate user.Participant can refer to either 'creator' or 'participant' parameter of ManagedUserCreateTransactionRequest400Input not valid: Participant privateId can not be null for private or corporate user.Participant can refer to either 'creator' or 'participant' parameter of ManagedUserCreateTransactionRequest400Managed 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 empty400Input not valid: Participant list can not be empty400Input not valid: Service package can not be empty500An 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.
filenamePlantUML Diagram 1.svg
originalHeight371
datanVTBjpswEP0a1BOVMZtqr4Rk1UNaRU3vqwkeEivGprZJq359x3a6S7yJWi0gBM8zb948DxQPzHmwfhpUwZoP33EYFXgs6qbgbPHMn1mAVy8QnXVZVSUPuDtJPYKFgRYE9jAp/2S0/woDEvIZ1Rm97CCL3OGPCXWHX9A5OGCj5EET3KH2aLPYb2bSojVW0wpn1SJb3pJy2ckRtF8aK9C2RpkQuVfQnfK6RxDmp9QHeu5BOXxDJkRazcs8GUPSQmt/+Qtes3jcjdzJ38GEilNEFuQuBnzcyB43UuOSxB5savWFHx/D+c/Uq7bnsug6ShE09CRqb34lbHy1LCbwZhwVbZKXhnaBEwaObpt1k/hatnpc8VuJG9IiNfFyFmamN3aYE2wv+Z9W63X73/mkcc5RvY9keUXCM5JXZyatpD6hSCB0Xp7DpKf2WZNMKIt6nRqKX0BrMcV4C9qFnGBcqgUzGeUAmsZbhDIuDvacf5tKRpeyAlu0IT/wnUFJEbfG3QlOatxtOcWi1ffl3KLb0bcYMiPHHo+g+vDWv4ussd1Rnm+IE+hBKnexIE1a3ZZv2hJZZowXmPt4jcSdKx4YakE/tT8=
compressedtrue
originalWidth547
revision3