Sign transaction as a platform-managed user

The Lequinox platform does not archive transactions for external role accounts or external personal identities as they represent another organisation.

Submitting the request Sign transaction as a platform-managed user gives the transaction the status ‘Opened’ and ‘Signed’, even if the application does not call the Open transaction as a platform-managed user first.

Steps

Submit a request in accordance with the details in Sign transaction as a platform-managed user.
The platform validates the request by verifying, among other things:
1. that the transaction is specified in the TransactionRequest.
2. whether or not the participant's access to the transaction has been revoked.
  
  Refer to the serviceType ‘REVOKE’ in the API endpoint /wiki/spaces/LPDA510/pages/1804140. A revoked participant cannot sign the transaction.
3. whether or not the transaction can be opened and signed.
  
  Refer to TIMELOCK_BEFORE and TIMELOCK_AFTER in the API endpoint Service.
The platform unlocks and opens the transaction to sign.
The platform signs the transaction on behalf of platform-managed user.
The platform updates the signed-status of the transaction in the archive.
The platform returns the ParticipantStatusResponse.