v1.0
get
/ec-dataintegration-svc/rest/v1.0/studies/{studyId}/{mode}/signconfiguration/history
Retrieves sign configuration history.
Request
Path Parameters
-
mode(required): string
Mode of the study, accepts: test, active, or training.Example:
active -
studyId(required): string(uuid)
Unique identifier (UUID, 32-character uppercase hexadecimal string) representing the study.Example:
A1B2C3D4E5F647839ABCDEF012345678
Query Parameters
-
configId: string(uuid)
Signature configuration identifier (UUID, 32-character uppercase hexadecimal string).Example:
2A5E92F1C2D54DDA9F1C0A9E7B3C2D1A -
limit: integer(int32)
Minimum Value:
0Maximum number of records to display per page.Example:100 -
offset: integer(int32)
Minimum Value:
0An order number to specify with which object you want to start retrieving result. If provided, you also need to specify a value for the limit parameter.Example:0
There's no request body for this operation.
Back to TopResponse
Supported Media Types
- application/json
200 Response
Success
Root Schema : schema
Type:
Show Source
array-
Array of:
object SignatureConfigurationDTO
Represents the configuration for electronic signatures for a study, including the required forms, visits, users, and rules.
Nested Schema : SignatureConfigurationDTO
Type:
objectRepresents the configuration for electronic signatures for a study, including the required forms, visits, users, and rules.
Show Source
-
affidavitCodeValue: string
Minimum Length:
0Maximum Length:4000Affidavit code for the configuration.Example:Electronic Signature Affidavit -
comment: string
Minimum Length:
0Maximum Length:2048Additional comments about this signature configuration.Example:Added new signature step for visit. -
configName: string
Minimum Length:
0Maximum Length:4000A user-friendly name for the signature configuration, used to distinguish it from other configurations.Example:Final Visit Sign Config -
emailReminder: string
Minimum Length:
0Maximum Length:1Indicator to send email reminder ('Y' or 'N').Example:N -
id: string
(UUID)
Unique identifier(UUID, 32-character uppercase hexadecimal string) for the signature configuration in UUID format.Example:
AABBCCDDEEFF00112233445566778899 -
objectVersionNumber: number
(int32)
Object version numberExample:
1 -
operationType: string
Operation type on the record, can have values CREATED, MODIFIED or REMOVEDExample:
CREATED -
reason: string
Minimum Length:
0Maximum Length:255Reason for the configuration or operation.Example:Other. -
requiredBy: array
requiredBy
Minimum Number of Items:
0Maximum Number of Items:4000List of user IDs (UUID, 32-character uppercase hexadecimal string) required to sign. -
requiredOn: string
Minimum Length:
0Maximum Length:16Allowed Values:[ "CASEBOOK", "VISIT", "FORM" ]Level at which signature is required.Example:FORM -
requiredOnForms: array
requiredOnForms
Minimum Number of Items:
0Maximum Number of Items:4000List of form IDs(UUID, 32-character uppercase hexadecimal string) required to sign. -
requiredOnVisits: array
requiredOnVisits
Minimum Number of Items:
0Maximum Number of Items:4000List of visit IDs(UUID, 32-character uppercase hexadecimal string) required to sign. -
softwareVersionNumber: number
(int32)
Software version numberExample:
1 -
targetAfter: string
Minimum Length:
0Maximum Length:16Allowed Values:[ "COMPLETION", "START" ]Event after which the target is considered achieved.Example:COMPLETION -
targetDate: integer
(int64)
Target date for signature as integer.Example:
2 -
targetSet: string
Minimum Length:
0Maximum Length:1Indicator if target is set ('Y' or 'N').Example:Y -
triggerQuestion: string
Unique Identifier (UUID, 32-character uppercase hexadecimal string) of the trigger question for conditional rules.Example:
55AA44BB33CC22DD11EEFF0011223344 -
userId: string
User ID(UUID, 32-character uppercase hexadecimal string) that performed the operation in UUID format.Example:
00112233445566778899AABBCCDDEEFF -
versionEnd: string
(date-time)
The end date until which the data is applicable or valid.Example:
2023-12-31T23:59:59Z -
versionStart: string
(date-time)
The timestamp marking the beginning of the validity period for this record version within the system.Example:
2023-01-01T00:00:00Z
Nested Schema : requiredBy
Type:
arrayMinimum Number of Items:
0Maximum Number of Items:
4000List of user IDs (UUID, 32-character uppercase hexadecimal string) required to sign.
Show Source
-
Array of:
string(uuid)
List of user IDs (UUID, 32-character uppercase hexadecimal string) required to sign.
Example:
[
"DDEEFF00112233445566778899AABBCC"
]Nested Schema : requiredOnForms
Type:
arrayMinimum Number of Items:
0Maximum Number of Items:
4000List of form IDs(UUID, 32-character uppercase hexadecimal string) required to sign.
Show Source
-
Array of:
string(uuid)
List of form IDs(UUID, 32-character uppercase hexadecimal string) required to sign.
Example:
[
"A1B2C3D4E5F607182736454647484950"
]Nested Schema : requiredOnVisits
Type:
arrayMinimum Number of Items:
0Maximum Number of Items:
4000List of visit IDs(UUID, 32-character uppercase hexadecimal string) required to sign.
Show Source
-
Array of:
string(uuid)
List of visit IDs(UUID, 32-character uppercase hexadecimal string) required to sign.
Example:
[
"5A6B7C8D9E0F10293847560123456789"
]Examples
400 Response
Bad_Request
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