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

      Refer to the attribute ‘type’ in User for more information.
    3. if attachments are specified, that file names and content are provided.
    4. that the server account of the application is enabled.
  3. The platform creates the transaction for the application server account.
  4. The platform archives the transaction details along with timestamps.
  5. The platform returns the TransactionResponse.





  • No labels