V1.0
delete
/ec-dataaction-svc/rest/v1.0/studies/{studyId}/{mode}/signconfiguration/{id}
Deletes a signature configuration entry for the given ID. The specified configuration is removed completely from the study's workflow signature requirements. Returns the deleted configuration details in the response object, so clients can confirm deletion and log the previous state if needed.
Request
Path Parameters
-
id(required): string(uuid)
Unique identifier (UUID, uppercase HEX string) of the signature configuration to be deleted.Example:
222EABDE1B9648F69D3B6250880A2B09 -
mode(required): string
Mode of the study, accepts: test, active, or training.Example:
test -
studyId(required): string
Unique identifier (UUID, 32-character uppercase hexadecimal string) representing the study.Example:
3F2504E04F8911D39A0C0305E82C3301
There's no request body for this operation.
Back to TopResponse
Supported Media Types
- application/json
200 Response
Successfully deleted the signature configuration. Response contains the details of the deleted configuration as a SignConfiguration object inside the RestResponse wrapper.
Root Schema : SignConfiguration
Type:
objectEntity model representing persisted signature configuration in the database. Properties include forms/visits, settings, lifecycle, and audit info.
Show Source
-
affidavitCodeValue: string
Affidavit code value associated with the signature requirement.Example:
Electronic Signature Affidavit -
comment: string
Minimum Length:
0Maximum Length:2048Comment regarding the last change made to the entity.Example:Imported via migration tool. -
configName(required): string
Minimum Length:
0Maximum Length:4000Name/title for the signature configuration.Example:Archive Visit Config -
emailReminder: string
Indicates if email reminders are active ('Y' or 'N').Example:
Y -
id: string
(UUID)
Unique identifier(UUID, 32-character uppercase hexadecimal string) for the persisted signature configuration.Example:
11223344556677889900AABBCCDDEEFF -
operationType: string
Minimum Length:
1Maximum Length:16Operation type on the record, can have values CREATED, MODIFIED or REMOVEDExample:REMOVED -
reason: string
Minimum Length:
0Maximum Length:255Reason for the entity creation or latest modification.Example:Initial import. -
requiredBy: string
(UUID)
Delimited UUID string indicating users required to sign in (UUID, 32-character uppercase hexadecimal string).Example:
99887766554433221100AABBCCDDEEFF -
requiredOn(required): string
Minimum Length:
0Maximum Length:16Allowed Values:[ "CASEBOOK", "VISIT", "FORM" ]Level at which signature is required.Example:FORM -
requiredOnForms: string
Delimited string of form UUIDs to which config applies.Example:
AABBCCDD11223344556677889900EEFF -
requiredOnVisits: string
(UUID)
Delimited string of visit UUIDs (UUID, 32-character uppercase hexadecimal string) to which config applies.Example:
FFEEDDCCBBAA99887766554433221100 -
targetAfter: string
Event or milestone after which target is to be achieved. values can be start, completion.Example:
start -
targetDate: integer
(int64)
Target date for signature as integer.Example:
3 -
targetSet(required): string
Minimum Length:
0Maximum Length:1Indicator if a target date/condition is set (Y or N).Example:Y -
triggerAnswer: string
String or delimited string of answers that act as trigger.Example:
No -
triggerQuestion: string
(UUID)
UUID (UUID, 32-character uppercase hexadecimal string) of the trigger question for conditional rules.Example:
55AA44BB33CC22DD11EEFF0011223344
Examples
400 Response
Invalid or missing ID parameter.
Root Schema : RestResponse
Type:
Show Source
object-
errorData: object
ErrorResponseData
Structure representing an error response from the reporting service. Contains an error code, human-readable message, and details.
-
result: object
result
-
status: string
-
version: integer
(int32)
Nested Schema : ErrorResponseData
Type:
objectStructure representing an error response from the reporting service. Contains an error code, human-readable message, and details.
Show Source
-
details: object
details
Detailed error context or debugging information such as validation error, stack trace, or field/parameter cause.
-
errorCode: string
Application or business-specific error code representing the error type.Example:
REPT_401 -
errorMessage: string
Human-readable error message describing the failure or issue.Example:
Unauthorized: User does not have access to the requested resource
Nested Schema : result
Type:
objectNested Schema : details
Type:
objectDetailed error context or debugging information such as validation error, stack trace, or field/parameter cause.
Example:
User role is missing required permission REPORTING_VIEW. Field: userId