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 checks if the participant of the transaction is revoked. Refer to REVOKE of /wiki/spaces/LPDA510/pages/1804140. Revoked participant cannot sign the transaction.
The platform checks if the transaction can be opened and signed and is not locked. Refer to TIMELOCK_BEFORE and TIMELOCK_AFTER of Service.
It then signs the transaction on behalf of platform-managed user.
The platform archives the signed status of the transaction along with the timestamp.
The platform returns the ParticipantStatusResponse.

Error messages

HTTP status code	Message	Comments
400	The application with the specified key could not be found
400	Unknown error	This error message is returned when the same user tries to sign the transaction more than once. the parameter 'transaction' in ManagedUserTransactionRequest is incorrect.
400	Input not valid: Transaction can not be empty	This error message is returned when the parameter 'transaction' is missing in ManagedUserTransactionRequest.
400	Invalid role ID format	The parameters 'corporateId' or 'applicationAccessId' or 'privateId' in User are not in the correct format.
400	Input not valid: Participant can not be null.	This error message is returned when the user parameter is not mentioned in ManagedUserTransactionRequest.
400	Input not valid: Participant can not be of unknown type: null	This error message is returned when The participant is empty. The parameter 'type' is missing from User (participant).
400	Input not valid: Participant corporateId can not be null for corporate or server user.
400	Input not valid: Participant applicationAccessId can not be null for private or corporate user.
400	Input not valid: Participant privateId can not be null for private or corporate user.
400	Managed identity was not found	The parameters 'corporateId' or 'applicationAccessId' or 'privateId' in User is incorrect.
500	An unexpected error occurred: Type definition error: [...] An unexpected error occurred: JSON parse error: [...]	These error messages are returned if one or more parameters are of the wrong type.

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 checks if the participant of the transaction is revoked. Refer to REVOKE of /wiki/spaces/LPDA510/pages/1804140. Revoked participant cannot sign the transaction.
The platform checks if the transaction can be opened and signed and is not locked. Refer to TIMELOCK_BEFORE and TIMELOCK_AFTER of Service.
It then signs the transaction on behalf of platform-managed user.
The platform archives the signed status of the transaction along with the timestamp.
The platform returns the ParticipantStatusResponse.

Error messages

HTTP status code	Message	Comments
400	The application with the specified key could not be found
400	Unknown error	This error message is returned when the same user tries to sign the transaction more than once. the parameter 'transaction' in ManagedUserTransactionRequest is incorrect.
400	Input not valid: Transaction can not be empty	This error message is returned when the parameter 'transaction' is missing in ManagedUserTransactionRequest.
400	Invalid role ID format	The parameters 'corporateId' or 'applicationAccessId' or 'privateId' in User are not in the correct format.
400	Input not valid: Participant can not be null.	This error message is returned when the user parameter is not mentioned in ManagedUserTransactionRequest.
400	Input not valid: Participant can not be of unknown type: null	This error message is returned when The participant is empty. The parameter 'type' is missing from User (participant).
400	Input not valid: Participant corporateId can not be null for corporate or server user.
400	Input not valid: Participant applicationAccessId can not be null for private or corporate user.
400	Input not valid: Participant privateId can not be null for private or corporate user.
400	Managed identity was not found	The parameters 'corporateId' or 'applicationAccessId' or 'privateId' in User is incorrect.
500	An unexpected error occurred: Type definition error: [...] An unexpected error occurred: JSON parse error: [...]	These error messages are returned if one or more parameters are of the wrong type.