Versions Compared

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 connected to the application 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

accounts or external personal identities as they represent another organisation. If archiving these

transactions

transaction events 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 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.
  • The platform retrieves the server account of the requesting application.
  • The platform retrieves the organisation to which the application belongs.
  • The platform creates the transaction.
  • The platform
    1. 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.

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

    1. The platform creates the transaction for the server account.

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

    3. The platform returns the TransactionResponse.

    Plantumlcloud
    toolbarbottom
    filenamePlantUML Diagram 1.

    plantuml

    svg
    originalHeight371
    datarVTBbtswDP0aoacMstwUvTpOih6yIVh2L1iLToTIkifJ3rCvH2V1aaI2XVHUNgzjkXx6fJTMrrkP4MLQacarqx/Y9RoCsrJigs8fxAOP8PII0V3OimImIu4PyvTgoKOAxBYGHe6sCd+gQ0LuUY8YVANZ5hZ/Dmga/Ireww4rrXaG4AZNQJflfreDkbV1hiKCF/MsvCHlqlE9mLCwTqKrrbYx81FDc8jX3YO0v5TZ0XcL2uMLMilTNF/mzlqSFlv7x89EyafrYuZW/YkmFIIysiT/ZMCXtWpxrQwuSOzOpVaP/Hgb7/+WnrV9KouevZJRQ0uiHu3vhPXPlk0Foup7TUMKytIUBGHg6bVeVYmv5svbpXitcE1alCFeweOeaa3rTgk2T/U3y9Wqfnc9aTzlKD5GsjgjERnJszOD0cocUCYQmqDGuNNT+7xKJsxYuUoNTSegdphyggPjY000jkyOAwj7GIETS89pN2mlyZyMd4Muqo+SR9BKTuX+QnIS4d9Uwea18ejG6ehA09D+ChfotnQEP42scs1eja+IkxhAaX80lpX17EVPMiub/JKYm3iOTNNi1xyNpB/ZXw==
    compressedtrue
    originalWidth488
    revision3