Versions Compared

Old Version 13

changes.mady.by.user Technical writer

Saved on

compared with

New Version 14

changes.mady.by.user Technical writer

Saved on

Key

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

You can let the CDI server create and sign the transaction with specified participants and attachments. This way, the application server account is the actual creator of the transaction.

Info

For the time being, the services "Monitor status", "Monitor status by participant" and "Multisign" are considered present in the CDICreateTransactionRequest and set to the value 'true'.


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 details in Create transaction for the application.
  2. The platform performs the following validations:
    1. Participants must be specified
    2. Participants must be of known type. Refer to type in User
    3. Organisation to which the application belongs should be known
    4. If attachments are specified then the file name and content should be provided.
    5. If the server account of the application is enabled.
  3. The platform retrieves the server account of the requesting application
  4. The platform retrieves the organisation to which the application belongs.
  5. The platform creates the transaction.
  6. The platform archives the transaction details along with timestamps.
  7. TransactionResponse is returned.




Plantuml


Error messages

Expand
title


HTTP status codeMessageComments
400Input not valid: Participant privateId 'XXXX' is not in the correct format.Where 'XXXX' is the value for the 'privateId' parameter submitted in the request .
400Input not valid: Participant corporateId 'XXXX' is not in the correct format.Where 'XXXX' is the value for the 'corporateId' parameter submitted in the request .
400Input not valid: Participant corporateId can not be null for corporate or server user.
400Invalid role ID formatThis error message is returned if the parameter 'privateId' or 'corporateId' is not in the correct format.
400Input not valid: Participant privateId can not be set for server user.
400Input not valid: Participant corporateId can not be set for private user.
400Input not valid: Participant corporateId can not be null for corporate or server user.
400Input not valid: Participant can not be of unknown type: nullThis error message is returned if the parameter "type" is missing from /wiki/spaces/LPDA510/pages/1804027
400Input not valid: Participant privateId can not be null for private or corporate user.
400Input not valid: Attachment fileName can not be empty
400Input not valid: Attachment content can not be empty
400Input not valid: Participant can not be of unknown type: null
400Input not valid: Participant list can not be empty
400Input not valid: Service package can not be empty
400

Unable to create transaction

This error message is returned if a deactivated user is included as a participant in the transaction.
500An unexpected error occurred: null

This error message is returned if

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