Versions Compared

Old Version 22

changes.mady.by.user Technical writer

Saved on

compared with

New Version 23

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 transaction events 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 validates the request by verifying, among other things:
    1. that participants are specified.

    2. that participants are of a known type.

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


    3. that the organisation to which the application belongs is known.
    4. that, if attachments are specified, file names and content are provided.
    5. that the server account of the application is enabled.
  3. ((The platform retrieves creates the transaction for the application 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. The platform returns the TransactionResponse.




Plantuml