The protocol service does not validate inputDataType. Only when setting the participant data on ParticipationService, errors will occur if no type information is available for the provided inputDataType.
When considering whether this should be a warning or an error, I believe it should most likely be a warning, keeping flexibility of deploying different versions of CARP subsystems in mind. It can be that the deployment backend has a more recent version than the studies frontend, in which case it could handle study protocols with inputDataType's which are only known on the backend, but not available to the frontend runtime.
Currently, it is possible to add a protocol with invalid
DefaultParticipantAttribute
s. E.g.,As stated elsewhere:
It will be useful to fail early, upon creation of the study protocol in the studies subsystem. This can likely be done by adding a new item to
possibleDeploymentIssues
.When considering whether this should be a warning or an error, I believe it should most likely be a warning, keeping flexibility of deploying different versions of CARP subsystems in mind. It can be that the deployment backend has a more recent version than the studies frontend, in which case it could handle study protocols with
inputDataType
's which are only known on the backend, but not available to the frontend runtime.