Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 20 Next »

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.

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'.

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. The platform returns the TransactionResponse.





  • No labels