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
  • Unique identifier (UUID, uppercase HEX string) of the signature configuration to be deleted.
    Example:
    222EABDE1B9648F69D3B6250880A2B09
  • Mode of the study, accepts: test, active, or training.
    Example:
    test
  • Unique identifier (UUID, 32-character uppercase hexadecimal string) representing the study.
    Example:
    3F2504E04F8911D39A0C0305E82C3301

There's no request body for this operation.

Back to Top

Response

Supported Media Types

200 Response

Successfully deleted the signature configuration. Response contains the details of the deleted configuration as a SignConfiguration object inside the RestResponse wrapper.
Body ()
Root Schema : SignConfiguration
Type: object
Entity model representing persisted signature configuration in the database. Properties include forms/visits, settings, lifecycle, and audit info.
Show Source
  • Affidavit code value associated with the signature requirement.
    Example: Electronic Signature Affidavit
  • Minimum Length: 0
    Maximum Length: 2048
    Comment regarding the last change made to the entity.
    Example: Imported via migration tool.
  • Minimum Length: 0
    Maximum Length: 4000
    Name/title for the signature configuration.
    Example: Archive Visit Config
  • Indicates if email reminders are active ('Y' or 'N').
    Example: Y
  • Unique identifier(UUID, 32-character uppercase hexadecimal string) for the persisted signature configuration.
    Example: 11223344556677889900AABBCCDDEEFF
  • Minimum Length: 1
    Maximum Length: 16
    Operation type on the record, can have values CREATED, MODIFIED or REMOVED
    Example: REMOVED
  • Minimum Length: 0
    Maximum Length: 255
    Reason for the entity creation or latest modification.
    Example: Initial import.
  • Delimited UUID string indicating users required to sign in (UUID, 32-character uppercase hexadecimal string).
    Example: 99887766554433221100AABBCCDDEEFF
  • Minimum Length: 0
    Maximum Length: 16
    Allowed Values: [ "CASEBOOK", "VISIT", "FORM" ]
    Level at which signature is required.
    Example: FORM
  • Delimited string of form UUIDs to which config applies.
    Example: AABBCCDD11223344556677889900EEFF
  • Delimited string of visit UUIDs (UUID, 32-character uppercase hexadecimal string) to which config applies.
    Example: FFEEDDCCBBAA99887766554433221100
  • Event or milestone after which target is to be achieved. values can be start, completion.
    Example: start
  • Target date for signature as integer.
    Example: 3
  • Minimum Length: 0
    Maximum Length: 1
    Indicator if a target date/condition is set (Y or N).
    Example: Y
  • String or delimited string of answers that act as trigger.
    Example: No
  • UUID (UUID, 32-character uppercase hexadecimal string) of the trigger question for conditional rules.
    Example: 55AA44BB33CC22DD11EEFF0011223344
Examples

400 Response

Invalid or missing ID parameter.
Body ()
Root Schema : RestResponse
Type: object
Show Source
Nested Schema : ErrorResponseData
Type: object
Structure representing an error response from the reporting service. Contains an error code, human-readable message, and details.
Show Source
  • details
    Detailed error context or debugging information such as validation error, stack trace, or field/parameter cause.
  • Application or business-specific error code representing the error type.
    Example: REPT_401
  • Human-readable error message describing the failure or issue.
    Example: Unauthorized: User does not have access to the requested resource
Nested Schema : result
Type: object
Nested Schema : details
Type: object
Detailed 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
Back to Top