Issue:
If an Amendment is added to a study which has an existing active Protocol Maintenance CE (CE is either In-progress or not started), the associated Amendment CE will be created but it won't be activated yet (i.e. the workflow will not get created yet).
If this Amendment CE which doesn't yet have a workflow created is manually marked as completed, it will appear to be in a "stuck" state where the Workflow Mode and Risk are not calculated:
The impact / issue is that any subsequent Protocol Maintenance events that are system-generated (data change, scheduled maintenance, etc.) will NOT be created as expected due to this issue.
Workaround:
It is advised to not manually complete a CE which doesn't have a workflow created. However, if this should occur, please reach out to [email protected]. We can provide assistance with updating the "stuck" Amendment CE so that future system-generated Protocol Maintenance events can continue to be created as expected.
Resolution:
A bug (ADO-106996) has been logged and the issue will be fixed in a future release.
Found In Version(s):
Disclose 2.23.x
Fixed In Version(s):
Disclose 2.24 and higher versions