Data Extracts
Table of Contents
In order to facilitate customer’s various needs, including additional integrations and information needs, we provide data extracts for a variety of data objects from both the Approvals & Disclosures and Third-Party Management applications.
What is Provided?
The following data objects are provided in a delta manner - with the exception of the initial extract - which is a full extract - regardless of the delta period. Please see Appendix A below for the fields provided and relationships amongst the data objects.
| Data Object | Description | Delta Type |
|---|---|---|
| Actions | A listing of all actions associated with the request, activities, and / or parties. | Request Patterns |
| Activities | A supportive listing of activities associated with a request. | Request Pattern |
| Parties | The foundational details for parties. | Party Pattern |
| Party Addresses | Addresses associated with parties. | Party Pattern |
| Party Details | The available attributes about the party. | Party Pattern |
| Requests | The core data object which represents the basic details of the request. | Request Pattern |
| Requests Activities Parties | The data which allows connectivity between the request’s activities and the associated parties and responses | Request Pattern |
| Responses | A listing of all questions and responses associated with the request, activities, and / or parties. | Request Pattern |
| Users | A listing of users of the system and the based attributes associated with the user. | Party Pattern (less fair market value concerns) |
| Role Privileges | A listing of privileges per role. | User Privileges Pattern |
| User Groups | A listing of group assignments per user. | User Privileges Pattern |
| User Privileges | A listing of privileges per user. | User Privileges Pattern |
| User Roles | A listing of roles per user. | User Privileges Pattern |
| Tasks | A listing of tasks that is or not associated with a request. | Task Pattern |
| Request File Attachments | A listing of file attachments per request. | Request Pattern |
| Risk Scoring | The basic risk scoring details associated with a request for which risk scoring is enabled. | Request Pattern |
| Risk Scoring Criterias | The risk scoring criteria that is associated with a risk scoring record. | Request Pattern |
| Request Activity Approval Steps | A listing of approval steps for activity. | Request Pattern |
| Request Recipient Approval Steps | A listing of approval steps for recipients. | Request Pattern |
Request Pattern records are shared when the associated request meets any of the following conditions:
- New Request within delta time period.
- New Request version within delta time period.
- Any action (submit, approve, reject, etc.) taken on the request.
Party Pattern records are shared when the associated request meets any of the following conditions:
- New Party within delta time period.
- New / updated party information attributes within delta time period.
- New / updated party fair market value (FMV) details within delta time period.
Scope and Format of Data
Customers will be provided with SFTP details where the files will be dropped.
The files begin running at the following times and are dropped into the STFP when done. (Approximately 30 minutes from start time.)
- Stage extracts are run daily at 6:00 AM UTC.
- Production extracts are run daily at 2:00 AM UTC.
Formatting
The files generated will be done so with the following characteristics:
- CSV Extension.
- Comma utilized as the delimiter.
- Column headers provided with each file which are lowercase with no special characters or spaces (underscores used).
- Values separated by the comma (“,”) delimiter.
- All text fields are quoted with the double quote character.
- Any literal double quote characters embedded are escaped with another double quote character.
- Utf-8 encoding.
File Naming
Structure - [customer_name]_[appliciation]_[data_object]_[run_date]_[extract_type]_[data_from]_[data_to].[extension]
e.g., acme_approvals_requests_20220721180505_delta_20220720_20220720.csv
- customer_name - single word name of the customer
- application - single word name of the application
- data_area - single word name of the data object
- run_date - the date when the extract was run in the following format: YYYYMMDDHHMMSS
- extract_type - either full or delta
- data_from - the date for the start of data in the following format: YYYYMMDD
- data_to - the date for the end of data in the following format: YYYYMMDD
- extension - the value for the extension (currently only csv)
SFTP Details
With the SFTP directory, the following folder structures will exist:
- /[customer_name]/extracts/ - Root directory where any extract documentation will be stored, in addition to the directories that will store the extract files themselves.
- /[customer_name]/extracts/_adhoc - Directory where any ad-hoc (requested out of the typical periodic processing of extracts) will be placed.
- /[customer_name]/extracts/[YYYY-MM]* - The directory which will be dynamically created based on the date of the data extracted (not the run date).
As an example, the files generated on 7/01/2022 for data created/modified on 6/30/2022 will have the following file paths and names:
/acme/extracts/202206/acme_approvals_requests_20220701180505_delta_20220630_20220630.csv
/acme/extracts/202206/acme_approvals_parties_20220701180505_delta_20220630_20220630.csv
Appendix A: Data Dictionary
Actions
| Data Object | Field | Order | Definition |
|---|---|---|---|
| actions | action_id | 1 | The unique ID for the action. |
| actions | action_datetime | 2 | The datetime when the action took place. |
| actions | actioned_by_party_id | 3 | The actioner's unique ID which types to users / parties data objects. |
| actions | actioned_by_name | 4 | The name of the actioner. |
| actions | actioned_by_role | 5 | The actioner's role when performing the action. |
| actions | action_type | 6 | The action type (e.g., submit, update, approve). |
| actions | request_id | 7 | The unique ID value for the request which links to the requests data object. |
| actions | formatted_request_id | 8 | The unique ID - formatted - for the request. |
| actions | actioned_object_type | 9 | The type of object that was actioned upon (e.g., Activity, Party, Questionnaire, Request) |
| actions | actioned_object_id | 10 | The unique ID value for the actioned_object_type. |
| actions | request_step_order | 11 | A integer, which when sorted, allows the understanding of the order of the desired request step. |
| actions | request_step_name | 12 | The name of the request step. |
| actions | comment | 13 | The comment provided alongside the action (per the actioned_by_party_id), if available. |
| actions | requires_mitigation | 14 | The user denoted that mitigation is required. |
| actions | voided | 15 | The user voided their action. |
| actions | modified_datetime | 16 | The short value/code identifying the specific customer. |
| actions | customer_id | 17 | The date which was used when determining the records to extract. Is the max value between the records insert or update timestamp. |
Activities
| Data Object | Field | Order | Definition |
|---|---|---|---|
| activities | activity_id | 1 | The unique ID which relates to the specific request activity. |
| activities | request_id | 2 | The ID which relates to the requests data object (id field). |
| activites | formatted_request_id | 3 | The unique ID - formatted - for the request. |
| activities | is_primary_activity | 4 | The record is the primary activity for the request. |
| activities | activity_status | 5 | This activities current status (e.g., Awaiting Approval, Draft, Recorded, etc.). |
| activities | is_active | 6 | Is the activity active? |
| activities | activity_name | 7 | The default name of the Activity. |
| activities | amount | 8 | The amount associated with the activity. |
| activities | currency_code | 9 | The currency associated with the amount field. |
| activities | modified_datetime | 10 | The date which was used when determining the records to extract. Is the max value between the records insert or update timestamp. |
| activities | customer_id | 11 | The short value/code identifying the specific customer. |
Parties
| Data Object | Field | Order | Definition |
|---|---|---|---|
| parties | party_id | 1 | The unique ID for the party. |
| parties | name | 2 | The full name of the specific party. |
| parties | name_informal | 3 | The alternative name for parties, specifically the preferred name for the individual and informal name for the organization. |
| parties | source_type | 4 | Whether the party is classified as an individual or organization. |
| parties | function | 5 | The function for the party, if available. |
| parties | subfuction | 6 | The sub-function for the party, if available. |
| parties | is_worker | 7 | Is the party a worker? |
| parties | is_govt | 8 | Is the party a government official? |
| parties | is_hcx | 9 | Is the party an Healthcare Provider or Organization? |
| parties | is_3p_or_vendor | 10 | Is the party a third party or vendor? |
| parties | is_bank | 11 | Is the party a bank? |
| parties | is_customer | 12 | Is the party a customer? |
| parties | is_state_owned | 13 | Is the party owned by the state? |
| parties | created_datetime | 14 | Created timestamp for the party. |
| parties | updated_datetime | 15 | Updated timestamp for the party. |
| parties | customer_id | 16 | The short value/code identifying the specific customer. |
| parties | fmv_amount | 17 | The amount associated with the party as their fair market value. |
| parties | fmv_currency_code | 18 | The fmv_amount associated currency code. |
| parties | fmv_effective_date | 19 | The date for which the FMV amount became effective. |
| parties | fmv_specialty_code | 20 | The specialty associated with the party and the fair market value. |
| parties | fmv_tier_code | 21 | The tier associated with the party and the fair market value. |
| parties | modified_datetime | 22 | The date which was used when determining the records to extract. Is the max value between the records insert or update timestamp. |
| parties | 23 | The email associated with the party. | |
| parties | erp_id | 24 | An ID for the party used by external system. |
| parties | country | 25 | The country of the party. |
| parties | is_active | 26 | Whether or not the party is active. |
| parties | is_blocked | 27 | Whether or not the party is blocked. |
| parties | note | 28 | Any notes about this party. |
Party Addresses
| Data Object | Field | Order | Definition |
|---|---|---|---|
| party_ addresses | party_id | 1 | The unique ID for the party. |
| party_ addresses | type | 2 | The type of address (i.e. home, business). |
| party_ addresses | address_line_1 | 3 | The first line of the address. |
| party_ addresses | address_line_2 | 4 | The second line of the address. |
| party_ addresses | city | 5 | The city of the address. |
| party_ addresses | state | 6 | The state of the address. |
| party_ addresses | country | 7 | The country of the address. |
| party_ addresses | postal_code | 8 | The postal code of the address. |
| party_ addresses | modified_datetime | 9 | The date which was used when determining the records to extract. Is the max value between the records insert or update timestamp. |
| party_ addresses | customer_id | 10 | The short value/code identifying the specific customer. |
Party Details
| Data Object | Field | Order | Definition |
|---|---|---|---|
| party_ details | party_id | 1 | The unique ID for the party. |
| party_ details | info_code | 2 | The code that describes the type of information attribute. |
| party_ details | value | 3 | The information value. |
| party_ details | customer_id | 4 | The short value/code identifying the specific customer. |
| party_ details | modified_datetime | 5 | The date which was used when determining the records to extract. Is the max value between the records insert or update timestamp. |
Requests
| Data Object | Field | Order | Definition |
|---|---|---|---|
| requests | formatted_request_id | 1 | The ID which relates to the requests data object (id field). |
| requests | formatted_id | 2 | The unique ID - formatted - for the request. |
| requests | code | 3 | The type of the request |
| requests | status | 4 | The current status of the request. |
| requests | type | 5 | The name of the request type. |
| requests | created_datetime | 6 | The datetime when the request was created. |
| requests | first_submission_datetime | 7 | The datetime when the request was submitted (first time). |
| requests | latest_submission_datetime | 8 | The datetime when the request was submitted (latest time). |
| requests | last_updated_datetime | 9 | The datetime when the request was last updated - with regards to versions (not actions taken upon the request). |
| requests | completion_datetime | 10 | The datetime when the request was completed. |
| requests | submitter_party_id | 11 | The party_id for the user that submitted the request. This value relates to the users data object (and the parties data object). |
| requests | title | 12 | The title value given to the request. |
| requests | amount | 13 | The sum total amount for the request. |
| requests | currency_code | 14 | The currency associated with the amount field. |
| requests | application | 15 | The specific application of relevancy (e.g., disclosures, pre-approval, third party management). |
| requests | modified_datetime | 16 | The date which was used when determining the records to extract. Is the max value between the records insert or update timestamp. |
| requests | customer_id | 17 | The short value/code identifying the specific customer. |
| requests | parent_request_id | 18 | The ID for the parent request (if it exists). Associates a request to a composite request (ex. campaign) |
| requests | forms_of_support | 19 | Comma separated list of values that denote the forms of support selected within the request |
| requests | sub_type | 20 | Comma separated list of values that denote the request subtypes selected within the request |
Requests Activities Parties Linkage
| Data Object | Field | Order | Definition |
|---|---|---|---|
| requests_ activities _parties _linkage | request_id | 1 | The ID which relates to the requests data object (id field). |
| requests_ activities _parties _linkage | formatted_request_id | 2 | The unique ID - formatted - for the request. |
| requests_ activities _parties _linkage | activity_id | 3 | The ID which relates to the activities data object (id field). |
| requests_ activities _parties _linkage | activity_status | 4 | The status of the activity (in_progress, approved, etc). |
| requests_ activities _parties _linkage | party_id | 5 | The ID which relates to the parties data object (id field). |
| requests_ activities _parties _linkage | party_status | 6 | The party’s status (e.g. awaiting_approval, approved, canceled) |
| requests_ activities _parties _linkage | amount | 7 | The amount allocated to the party for that activity |
| requests_ activities _parties _linkage | currency_code | 8 | The currency associated with the amount field. |
| requests_ activities _parties _linkage | activity_party_status | 9 | The status of the activity_party (in_progress, approved, etc). |
| requests_ activities _parties _linkage | modified_datetime | 10 | The date which was used when determining the records to extract. Is the max value between the records insert or update timestamp. |
| requests_ activities _parties _linkage | customer_id | 11 | The short value/code identifying the specific customer. |
| requests_ activities _parties _linkage | local_amount | 12 | The amount allocated to the party for that activity (may be in tenant’s default currency, or a user selected currency, when currency differs from tenant default) |
| requests_ activities _parties _linkage | local_currency_code | 13 | The local currency associated with the amount field. (may be in tenant’s default currency, or a user selected currency, when currency differs from tenant default) |
Responses
| Data Object | Field | Order | Definition |
|---|---|---|---|
| responses | request_id | 1 | The ID which relates to the requests data object (id field). |
| responses | formatted_request_id | 2 | The unique ID - formatted - for the request. |
| responses | activity_id | 3 | The ID which relates to the specific request activity. |
| responses | party_id | 4 | The party ID when party relevant. |
| responses | question_code | 5 | A system code used to identify the exact question (e.g., q_company_active_negotiations_to_expand_business_04). |
| responses | library_item_code | 6 | A system code used to identify the general question (e.g., company_active_negotiations_to_expand_business). |
| responses | question_default_text | 7 | The default text assigned for the question. |
| responses | response_data | 8 | The response data value is a single field with varying types. |
| responses | response_type | 9 | The response type column is provided to support any parsing needs. |
| responses | response_order | 10 | A number which represents the placement question in the questionnaire. |
| responses | attachment_names | 11 | When the response has associated files attached, the filenames are available in this field. When multiple files, the names are delimited by the characters **. |
| responses | modified_datetime | 12 | The date which was used when determining the records to extract. Is the max value between the records insert or update timestamp. |
| responses | customer_id | 13 | The short value/code identifying the specific customer. |
Users
| Data Object | Field | Order | Definition |
|---|---|---|---|
| users | party_id | 1 | The system ID uniquely identifying the party that is a worker. |
| users | name | 2 | The user's full name. |
| users | status | 3 | The current status of the employee (e.g., active, inactive). |
| users | function | 4 | The function (typically the department) specified for the user. |
| users | division | 5 | User division. |
| users | business_area | 6 | User business_area. |
| users | subfunction | 7 | User subfuction. |
| users | 8 | The user's email address. | |
| users | username | 9 | The system username used to log into the application. |
| users | external_id | 10 | The user's external (company) ID, when available. |
| users | country | 11 | The country name denoted for the employee. |
| users | is_active | 12 | Whether or not the user is active. |
| users | is_blocked | 13 | Whether or not the user is blocked. |
| users | created_datetime | 14 | The datetime value signifying when the user was initially created. Example value: "2022-05-16 22:35:42.620000000 +00:00". |
| users | modified_datetime | 15 | The date which was used when determining the records to extract. Is the max value between the records insert or update timestamp. |
| users | customer_id | 16 | The short value/code identifying the specific customer. |
| users | user_id | 17 | The user ID uniquely identifying the user. |
Role Privileges
| Data Object | Field | Order | Definition |
|---|---|---|---|
| role_privileges | role_code | 1 | Codified name of role. |
| role_privileges | privilege_code | 2 | Codified name of privilege. |
| role_privileges | modified_datetime | 3 | The date which was used when determining the records to extract. Is the max value between the records insert or update timestamp. |
| role_privileges | customer_id | 4 | The short value/code identifying the specific customer. |
User Groups
| Data Object | Field | Order | Definition |
|---|---|---|---|
| user_groups | user_id | 1 | The user ID uniquely identifying the user. |
| user_groups | group_id | 2 | The user ID uniquely identifying the group. |
| user_groups | group_code | 3 | The codified name of the group. |
| user_groups | group_name | 4 | The plain text name of the group. |
| user_groups | is_active | 5 | Whether of not the user has an active assignment to that group. |
| user_groups | modified_datetime | 6 | The datetime the user group assignment was last modified. |
| user_groups | customer_id | 7 | The short value/code identifying the specific customer. |
User Privileges
| Data Object | Field | Order | Definition |
|---|---|---|---|
| user_privileges | user_id | 1 | The user ID uniquely identifying the user. |
| user_privileges | privilege_code | 2 | Codified name of privilege. |
| user_privileges | is_grant | 3 | Boolean that explicitly allows or disallows this privilege. False value is primarily used when a user_role is granted but a privilege within that role has been removed for that user. |
| user_privileges | modified_datetime | 4 | The date which was used when determining the records to extract. Is the max value between the records insert or update timestamp. |
| user_privileges | customer_id | 5 | The short value/code identifying the specific customer. |
User Roles
| Data Object | Field | Order | Definition |
|---|---|---|---|
| user_roles | user_id | 1 | The user ID uniquely identifying the user. |
| user_roles | role_code | 2 | Codified name of role. |
| user_roles | modified_datetime | 3 | The date which was used when determining the records to extract. Is the max value between the records insert or update timestamp. |
| user_roles | customer_id | 4 | The short value/code identifying the specific customer. |
Tasks
| Data Object | Field | Order | Definition |
|---|---|---|---|
| tasks | task_id | 1 | The unique ID for the task. |
| tasks | task_formatted_id | 2 | The unique ID - formatted - for the task. |
| tasks | title | 3 | The title for the task. |
| tasks | due_date | 4 | The due date for the task. |
| tasks | status_code | 5 | The tasks status (e.g. draft, in_progress, completed, canceled). |
| tasks | category | 6 | A category for the task that is specific to the customer (e.g. mitigation, ad_hoc). |
| tasks | type_code | 7 | A type for the task that is specific to the customer (e.g. documentation, consult with and individual, other). |
| tasks | submitted_by_user_id | 8 | The user ID of the user who submitted the task. |
| tasks | assigned_to_user_id | 9 | The user ID for the user who is assigned to the task. |
| tasks | request_id | 10 | The request’s unique identifier that is associated with this task. |
| tasks | modified_datetime | 11 | The date which was used when determining the records to extract. Is the max value between the records insert or update timestamp. |
| tasks | customer_id | 12 | The short value/code identifying the specific customer. |
Request File Attachments
| Data Object | Field | Order | Definition |
|---|---|---|---|
| request_file_ attachments | id | 1 | Unique identifier for the file attachment. |
| request_file_ attachments | fk_table | 2 | The table name associated with the file attachment (request table). |
| request_file_ attachments | fk_id | 3 | The request’s unique identifier that is associated with this file attachment. |
| request_file_ attachments | user_id | 4 | The unique identifier of the user. |
| request_file_ attachments | uploaded_filename | 5 | The filename. |
| request_file_ attachments | uploaded_file_timestamp | 6 | When the filename was created. |
| request_file_ attachments | uploaded_file_size | 7 | The size of the file. |
| request_file_ attachments | uploaded_file_type | 8 | The file type. |
| request_file_ attachments | catalog_filename | 9 | Filename identification. |
| request_file_ attachments | attach_timestamp | 10 | Timestamp of when the file was attached. |
| request_file_ attachments | modified_datetime | 11 | The date which was used when determining the records to extract. Is the max value between the records insert or update timestamp. |
| request_file_ attachments | customer_id | 12 | The short value/code identifying the specific customer. |
Risk Scoring
| Data Object | Field | Order | Definition |
|---|---|---|---|
| risk_scoring | request_id | 1 | The request’s unique identifier that is associated with this risk score. |
| risk_scoring | risk_level | 2 | Overall risk score (e.g. low, medium, high). |
| risk_scoring | risk_score_value | 3 | The risk score (decimal point value out of the max risk score value). |
| risk_scoring | max_risk_score_value | 4 | The highest risk level possible for this score. |
| risk_scoring | modified_datetime | 5 | The date which was used when determining the records to extract. Is the max value between the records insert or update timestamp. |
| risk_scoring | customer_id | 6 | The short value/code identifying the specific customer. |
Risk Scoring Criterias
| Data Object | Field | Order | Definition |
|---|---|---|---|
| risk_scoring_ criterias | request_id | 1 | The request’s unique identifier that is associated with this risk scoring criteria. |
| risk_scoring_ criterias | default_title | 2 | The label/title of the request’s questionnaire that is related to this individual risk criteria. |
| risk_scoring_ criterias | importance | 3 | Importance weight of this risk criteria for the overall score. |
| risk_scoring_ criterias | potential_value_achievement | 4 | The individual risk criteria’s risk score value, that is used to calculate the overall risk score. |
| risk_scoring_ criterias | response | 5 | The request’s questionnaire response that is related to this individual risk criteria. |
| risk_scoring_ criterias | risk_result | 6 | The individual risk criteria risk level score. |
| risk_scoring_ criterias | template_code | 7 | The system template code for the type of request. |
| risk_scoring_ criterias | template_item_code | 8 | The system template item code for the request. |
| risk_scoring_ criterias | template_questionnaire_code | 9 | The system template questionnaire code for the request. |
| risk_scoring_ criterias | modified_datetime | 10 | The date which was used when determining the records to extract. Is the max value between the records insert or update timestamp. |
| risk_scoring_ criterias | customer_id | 11 | The short value/code identifying the specific customer. |
| risk_scoring_ criterias | risk_area | 12 | The risk area of this risk scoring criteria. |
Risk Scoring Adjustment
| Data Object | Field | Order | Definition |
|---|---|---|---|
| risk_scoring_ adjustment | request_id | 1 | The request’s unique identifier that is associated with this risk scoring adjustment. |
| risk_scoring_ adjustment | customer_id | 2 | The short value/code identifying the specific customer. |
| risk_scoring_ adjustment | risk_adjustment_id | 3 | The unique identifier of the risk scoring adjustment. |
| risk_scoring_ adjustment | risk_area | 4 | The risk area of this particular adjustment. |
| risk_scoring_ adjustment | adjustment_type | 5 | The type of adjustment. |
| risk_scoring_ adjustment | categories | 6 | Categories for this adjustment. |
| risk_scoring_ adjustment | score_impact | 7 | The score impact that will affect the associated risk. |
| risk_scoring_ adjustment | user_id | 8 | The identifier of the user who created this manual risk scoring adjustment. |
| risk_scoring_ adjustment | comments | 9 | Any comments a user added when creating this manual adjustment. |
| risk_scoring_ adjustment | status | 10 | If this adjustment is active or inactive (boolean of true or false). |
| risk_scoring_ adjustment | modified_datetime | 11 | The date which was used when determining the records to extract. Is the max value between the records insert or update timestamp. |
Request Activity Approval Steps
| Data Object | Field | Order | Definition |
|---|---|---|---|
| request_ activitiy_ approval_ steps | request_id | 1 | The request’s unique identifier that is associated with this activity approval step record. |
| request_ activitiy_ approval_ steps | formatted_request_id | 2 | The request’s unique identifier that is associated with this activity approval step record. |
| request_ activitiy_ approval_ steps | primary_activity_status | 3 | Status of the primary activity (approved, canceled, etc). |
| request_ activitiy_ approval_ steps | approver_user_id | 4 | The user id of an approver of this activity. |
| request_ activitiy_ approval_ steps | approver_is_active | 5 | Indicates if the user is active or has been reassigned (false if they were reassigned). |
| request_ activitiy_ approval_ steps | workflow_step_id | 6 | The identifier of the workflow step of approval. |
| request_ activitiy_ approval_ steps | workflow_action_type | 7 | The action taken by the approver, empty if they have not taken an action. |
| request_ activitiy_ approval_ steps | workflow_action_datetime | 8 | When the action of the approver was taken (empty if no action was taken). |
| request_ activitiy_ approval_ steps | request_step_id | 9 | The request step identifier. |
| request_ activitiy_ approval_ steps | request_step_order | 10 | Order of request steps, used to determine the order of each approver. |
| request_ activitiy_ approval_ steps | request_step_name | 11 | Title of the approver group for this primary activity approval step. |
| request_ activitiy_ approval_ steps | modified_datetime | 12 | The date which was used when determining the records to extract. Is the max value between the records insert or update timestamp. |
| request_ activitiy_ approval_ steps | customer_id | 13 | The short value/code identifying the specific customer. |
Request Recipient Approval Steps
| Data Object | Field | Order | Definition |
|---|---|---|---|
| request_ recipient _ approval_ steps | request_id | 1 | The request’s unique identifier that is associated with this activity approval step record. |
| request_ recipient _ approval_ steps | formatted_request_id | 2 | The request’s unique identifier that is associated with this activity approval step record. |
| request_ recipient _ approval_ steps | request_party_id | 3 | The request party id associated with this recipient. |
| request_ recipient _ approval_ steps | request_party_status | 4 | The recipient’s overall approval status. |
| request_ recipient _ approval_ steps | recipient_party_id | 5 | The recipient's party id. |
| request_ recipient _ approval_ steps | approver_user_id | 6 | The user id of an approver of this activity. |
| request_ recipient _ approval_ steps | approver_is_active | 7 | Indicates if the user is active or has been reassigned (false if they were reassigned). |
| request_ recipient _ approval_ steps | workflow_step_id | 8 | The identifier of the workflow step of approval. |
| request_ recipient _ approval_ steps | workflow_action_type | 9 | The action taken by the approver, empty if they have not taken an action. |
| request_ recipient _ approval_ steps | workflow_action_datetime | 10 | When the action of the approver was taken (empty if no action was taken). |
| request_ recipient _ approval_ steps | request_step_id | 11 | The request step identifier. |
| request_ recipient _ approval_ steps | request_step_order | 12 | Order of request steps, used to determine the order of each approver. |
| request_ recipient _ approval_ steps | request_step_name | 13 | Title of the approver group for this recipient approval step. |
| request_ recipient _ approval_ steps | modified_datetime | 14 | The date which was used when determining the records to extract. Is the max value between the records insert or update timestamp. |
| request_ recipient _ approval_ steps | customer_id | 15 | The short value/code identifying the specific customer. |
Extract Diagram

Appendix B: Change Log
Appendix B: Change Log
- Added a new field to the responses data object called library_item_code and clarified the descriptions.
-
1/23 Added fields related to data model changes:
-
party
- email (moved from party information)
- erp_id (moved from party information)
-
request
- parent request id (in order to relate campaign request and sub-requests)
-
party
- Mar 28, 2023
Added a new extract for extracting party addresses: party_address
These changes make alterations to existing column names and will require updates to downstream consumption.
-
All tables:
- ID references have been updated to be consistent across exports:
- action_id
- request_activity_id -> activity_id
- party_id
- request_id
- formatted_request_id
-
The formatted request ID (ex. EXF-000-001) has been added to accompany request ID where present.
-
Actions
- id -> action_id
- + formatted_request_id
-
Activities
- id -> activity_id
- + formatted_request_id
-
Parties
- id -> party_id
- + country
- + is_active
- + is_blocked
-
Party Details
- No change
-
Request Activity Parties
- request_activity_id -> activity_id
- + formatted_request_id
-
Requests
- id -> request_id
- formatted_id -> formatted_request_id
- submitter_id -> submitter_party_id
-
Responses
- request_activity_id -> activity_id
- + formatted_request_id
-
Responses for currency values now have currency code prepended to the value:
- 100 -> USD 100
-
Users
- id -> party_id
- + division
- + business_area
- + subfunction
- + is_active
- + is_blocked
- May 30, 2023
Added new table extracts:
- User Role
- User Privileges
- Role Privileges
- Tasks
- Request File Attachments
- Risk Scoring
- Risk Scoring Criterias
Updated the following existing table:
-
Request Activity Parties
- + party_status
- June 29, 2023
Added new table extracts:
- Request Activity Approval Steps
- Request Recipient Approval Steps
Updated the following existing tables:
-
Request Activity Parties
- + activity_status
- + activity_party_status
-
Request File Attachments
- + attachment_timestamp
-
Parties
- + note
- September 7, 2023
Added blank responses from optional questions. Only includes responses going forward.
- November 16, 2023
Added new table extract:
- risk_scoring_adjustments
Added risk_area to risk_scoring_criteria extract
Added user_id to users extract
- January 5, 2024
Added forms_of_support and sub_type to the requests extract
- February 9, 2024
Added user_groups category extract
- March 8th, 2024
Added local_amount and local_currency_code to request_activity_parties_linkage