The Monitoring feature provides the ability to receive notifications when changes occur to content contained in specific data products and D-U-N-S Numbers®.
D&B Direct+ data API provides access to numerous products, each with a set of attributes. Monitoring allows you to receive notifications when any of those attribute values change for the D-U-N-S Number in the registration.
For more information on the products, please see the Data Product APIs.
D&B Direct+ Monitoring Registrations represent a request to monitor a set of D-U-N-S Numbers against one of the D&B Direct+ Data Products. It also includes details on how notifications are to be delivered and other information necessary for monitoring.
The D-U-N-S Numbers can be specified as:
The Monitoring Registration also allows for an optional request for a seed (or baseline) of the data to be delivered per the delivery channel configuration in the Registration.
Note: For China, due to recent regulatory changes limited data is available for online & monitoring.
A seed file provides a baseline of data for the Monitoring Registration. When you create a registration, if Seed File = True:
Change notifications provide details about changes that occur to D-U-N-S Numbers within the Monitoring Registration.
Once a registration is created and processed, regular notifications are delivered to the destination and at the frequency specified in the registration.
For STP and S3, multiple files may be received depending on the number of notifications. The individual notifications are grouped by D-U-N-S Numbers and in date/time ascending order. A single D-U-N-S Number will never be split between multiple files. Best practice to update a single D-U-N-S Number, is to process the notifications in a file in order.
While it is unlikely, it is possible that the same D-U-N-S Number will have more than one UPDATE notification in a single package.
In order to receive change notifications, a Monitoring Registration must be created; a separate registration is required for each product and version you want to monitor.
To create a registration, the following information needs to be provided; customers should work with their Dun & Bradstreet Representative to have registrations created:
Property | Description |
---|---|
Subscriber | The subscriber ID assigned by Dun & Bradstreet that uniquely identifies the subscriber. The subscriber for which the registration is created allows that subscriber to later manage the registration through the APIs. |
Identifier | A string used to identify the registration. The reference must be unique for each subscriber. This value cannot be changed once the registration is created. |
Description | A description for the registration. Provide a description that
clearly identifies the purpose of the registration. Valid contents: Up to 256 characters that can include A-Z, a-z, 0-9, and the following special characters: . , - |
Product | The product ID provided by Dun & Bradstreet that
identifies the product to be included in this registration. Only
one product can be included in a registration. The product
cannot be changed once the registration is created.
IMPORTANT: The following products cannot be registered for a universe :
|
Product version | The version ID (e.g., v1) that identifies the product version to be used for this registration. Only one version can be included in a registration. The version cannot be changed once the registration is created. |
Universe or LOD | Indicates whether the registration is for a Universe or List
of D-U-N-S Numbers.
This value cannot be changed once the registration is created. |
Seed File | Indicates if a seed file should be delivered. Valid values:
|
Notification Frequency | Indicates how often notifications will be delivered. Valid values:
If there are no new notifications, a 0 notification header file will be delivered for the specified frequency. |
Delivery Trigger | Indicates how notifications will be delivered. Valid values:
|
Notification Type | Indicates the level of detail each change notification will
include for any D-U-N-S Number that has changed. Valid values:
|
Destination Type | The communications protocol used to transfer change
notifications and any other material related to the
registration. Valid values:
|
File Transfer Profile | The specific location for file delivery; one of the following:
|
S3 Encryption Key | A key used to encrypt the files delivered to S3. This is
required if the File Transfer Profile is S3 and is not
applicable otherwise. For information on setting up S3 for monitoring access, Configure S3 Bucket. |
Email Addresses | Email addresses for users to be notified regarding monitoring activities for this Registration. A D&B contact email (employee or partner) must be included in this list. |
JSON Path Inclusion | For the data product being monitored, the JSON paths that will
be monitored. Only changes to the values for these paths will be
included in notification files. Changes to other values will not
be delivered through monitoring. Either jsonPathInclusion or jsonPathExclusion may be specified. See Element-Level Monitoring for more information. |
JSON Path Exclusion | For the data product being monitored, the JSON paths that will
not be monitored. Changes to values for all other paths in the
product will be included in monitoring notifications. Either jsonPathInclusion or jsonPathExclusion may be specified. See Element-Level Monitoring for more information. |
The Destination Type and File Transfer protocol identify where monitoring files are delivered (both seed and notification files).
Element-Level Monitoring provides the ability to choose the elements for which you want to receive monitoring notifications. The available elements are limited to those in the product being monitored. Elements can be configured in the request of Create a Registration and Edit Registration Details APIs through the jsonPathInclusion OR jsonPathExclusion parameters.
We strongly recommend customers work with their Dun & Bradstreet Representative to enable this feature.
Element-Level Monitoring does not apply to FULL_PRODUCT registrations or Seed files; the entire product record for the D-U-N-S Number is included in Seed files.
If you are updating an existing registration, it is highly-recommended that you use the Get Registration Details API to first pull the existing configuration, so you do not inadvertently omit an existing path. Update registration does an overwrite of the previous configuration
Provides the ability to pull change notifications for a small LOD registrations through API. It is recommended that pull API is only used for small registrations as it is more efficient and effective to have large numbers of notifications delivered via push (files). The registration must have been created with deliveryTrigger set to API_PULL in order to use the pull API. This is available for both FULL_PRODUCT and UPDATE notification types. FileTransferProfile is required for this type of registration to receive the seed files (if seed=true) and the exception file. It is not recommended to use longer deliveryFrequency WEEKLY or MONTHLY. In order to pull the notifications through API, the registration must be unsuppressed. Notifications are available for up to 4 days to be pulled. For technical specifications refer: Pull new Notifications.
Notifications which are pulled are available for replay (to be re-pulled) via the replay API for 14 days. If notifications are not pulled for 4 days then they will be removed and a re-seed will be necessary. For technical specifications refer: Replay(re-pull) Notifications.
File types accepted for List of D-U-N-S Numbers Registration are:
The Exception file is a tab-delimited text file and contains one line per D-U-N-S Number for which there was a processing exception.
DUNS Code Information
808080808 40003 101010101
707070707 40002
606060606 10001
Attribute | Data Type | JSON Type | Description |
---|---|---|---|
DUNS | Element | Integer | The D-U-N-S Number is an identification number assigned by Dun & Bradstreet that uniquely identifies the entity in accordance with the Data Universal Numbering System (DUNS). |
Code | Element | Integer | A number assigned by Dun & Bradstreet that uniquely
identifies the reason for this exception. One of the following:
|
Information | Element | String | If the D-U-N-S Number was transferred, contains the D-U-N-S Number to which it was transferred. The transferred TO D-U-N-S Number is not part of the Registration; to add it, use the Add DUNS to Registration API. (See the Monitoring, Add DUNS to existing Registrations API page.) |
! Authorization is required from your D&B representative before registering for the this product.
Family Tree Monitoring is a joint venture between the D&B Direct+ and D&B D+ Monitoring teams to deliver notifications which are complementary to the existing Family Tree API. The supported monitoring product is called FULL_FAMILY_TREE
As part of the Monitoring Registration there is an option to request a seed file. This file is a baseline extract of the data requested in the Registration. Once the registration is processed, the seed files will be delivered per the delivery channel configuration in the Registration.
A seed delivery includes two types of files: Seed Header and Seed Data.
Provides metadata for the Seed Data file, such as number records, along with Seed Data file names delivered per the delivery channel configuration in the Registration.
Sample: PRD_MKTLNK_STP_2017020808104948_SEED_HEADER.json
{
"fileHeader" : {
"headerType" : "SEEDFILE",
"fileId" : "rrt-f98e3872-a-eu-6623-63069210-1",
"inLanguage" : "en-US",
"reference" : "PRD_MKTLNK_STP ",
"productId" : "aasmcu",
"versionId" : "v1",
"totalRecordCount" : 92456097,
"fileTimeStamp" : "2017-01-05T09:59:46.988Z",
"files" : [
{
"name" : "PRD_MKTLNK_STP_20170208124948_SEEDFILE_1.zip",
"hash" : "71a00d72f7d3f7caaec0b174dc444dccfaa0e230af85bbe444d8365b98083ba0"
},
{
"name" : "PRD_MKTLNK_STP_20170208124948_SEEDFILE_2.zip",
"hash" : "8f33b5469f92f4aba4d41c06475090f491ff3dfabec92474298c368cb60c3f67"
},
{
"name" : "PRD_MKTLNK_STP_20170208124948_SEEDFILE_3.zip",
"hash" : "d21535ba1bfff44144465ad038f0a0555a371fdb0f3dd5f61b20ea71684b94be"
},
{
"name" : "PRD_MKTLNK_STP_20170208124948_SEEDFILE_4.zip",
"hash" : "8b6e1206a29ec1fb09ee7c13598df6602245894e201f9556532c7b722a89aedb"
},
{
"name" : "PRD_MKTLNK_STP_20170208124948_SEEDFILE_5.zip",
"hash" : "619bfe4684a4852b222fc40a6d64b26242a3778e51d0f889e66abce1de8d688e"
},
{
"name" : "PRD_MKTLNK_STP_20170208124948_SEEDFILE_6.zip",
"hash" : "b363db52412800435cf8528ef58feb64d54444940b609df244e4bb53ef728c8e"
},
{
"name" : "PRD_MKTLNK_STP_20170208124948_SEEDFILE_7.zip",
"hash" : "717eb5a4f5d913eeca5610d3b3f4aa0d6266ff40553f87b4cf2f2e6e49f92bd9"
},
{
"name" : "PRD_MKTLNK_STP_20170208124948_SEEDFILE_8.zip",
"hash" : "c46e5a13e64772bd8cc0d3bd6b4cb7a5a61b339ea92984d78ba1326871d6cba5"
}
]
}
}
Attribute | Data Type | JSON Type | Description |
---|---|---|---|
fileHeader | Aggregate | Element | The details of the information in the file. |
fileHeader.headerType | Element | String | The type of the seed header file. Possible values:
|
fileHeader.reference | Element | String | The unique identifier assigned to the Monitoring Registrations when it was created. |
fileHeader.fileID | Element | String | The file's unique identifier. |
fileHeader.fileTimeStamp | Element | String | The date and time, in ISO 8601 UTC Z standards, when the response was created by the application. |
fileHeader.inLanguage | Element | String | An IETF BCP 47 code value that defines the language in which this product was rendered. |
fileHeader.productId | Element | String | The product ID associated with the Monitoring Registration |
fileHeader.versionId | Element | String | The product version ID associated with the Monitoring Registration |
fileHeader.totalRecordCount | Element | Integer | The total number of records included with this seed request. |
fileHeader.files | Aggregate | Object | The details of the seed data files. |
fileHeader.files.name | Element | String | The name of the seed data file. |
fileHeader.files.hash | Element | String | The hash size of the seed data file. |
The Seed data file is a text file; each record in the file is in JSON format and contains one line per D-U-N-S Number included in the Monitoring Registration.
For details on the JSON structure, please see the applicable data product's API Response documentation.
Once the seed file is consumed, the Registration must be unsuppressed to receive notifications. This can be done with the Monitoring API. (See the Monitoring, Suppress or Unsuppress API page.)
Once a registration request is processed and notifications are unsuppressed, if necessary, change notifications are pushed to the chosen delivery channel (STP, S3) with the frequency specified in the Monitoring Registration.
STP and S3 notification deliveries include:
{
"fileHeader" : {
"reference" : "STG_CMPELK",
"headertype" : "NOTIFICATION",
"fileId" : 0,
"fileTimeStamp" : "2017-01-18T13:51:31.923Z",
"inLanguage" : "en-US",
"productID" : "cmpelk",
"productVersion" : "v1",
"totalRecordCount" : 192939522,
"files" : [
{
"name" : "STG_CMPELK_20170118133445_NOTIFICATION_1.zip",
"hash" : "e9494312b6f13f6f65d3200700b6370aa745680aaaed166ac2ad3f86a6849ec4"
},
{
"name" : "STG_CMPELK_20170118133445_NOTIFICATION_2.zip",
"hash" : "b23d4c50d9f1a2f40562b2fbaabed69ebb3876259526e77f0c6a13b263a3ba1b"
}
],
"notificationCount" : [
{
"count" : 597659,
"type" : "ENTER"
},
{
"count" : 6256,
"type" : "TRANSFER"
},
{
"count" : 191706866,
"type" : "UPDATE"
},
{
"count" : 191,
"type" : "UNDER_REVIEW"
},
{
"count" : 18155,
"type" : "EXIT"
},
{
"count" : 597862,
"type" : "SEED"
},
{
"count" : 12330,
"type" : "DELETE"
},
{
"count" : 201,
"type" : "UNDELETE"
},
{
"count" : 2,
"type" : "REVIEWED"
}
]
}
}
Attribute | Data Type | JSON Type | Description |
---|---|---|---|
fileHeader | Aggregate | Object | The details of the information in the file. |
fileHeader.reference | Element | String | The unique identifier assigned to the Monitoring Registrations when it was created. |
fileHeader.headerType | Element | String | The type of the seed header file. Possible values:
|
fileHeader.fileID | Element | String | The file's unique identifier. |
fileHeader.fileTimeStamp | Element | String | The date and time, in ISO 8601 UTC Z standards, when the response was created by the application. |
fileHeader.inLanguage | Element | String | An IETF BCP 47 code value that defines the language in which this product was rendered. |
fileHeader.productID | Element | String | The product ID associated with the Monitoring Registration |
fileHeader.productVersion | Element | String | The product version ID associated with the Monitoring Registration |
fileHeader.totalRecordCount | Element | Integer | The total number of records included with this seed request. |
fileHeader.files | Aggregate | Object | The details of the seed data files. |
fileHeader.files.name | Element | String | The name of the seed data file. |
fileHeader.files.hash | Element | String | The SHA-256 hash of the seed data file. |
fileHeader.notificationCount | Aggregate | Object | The details of the type of notifications in the file(s). |
fileHeader.notificationCount.count | Element | Integer | The number of records of the type. |
fileHeader.notificationCount.type | Element | String | The type of notification (see D-U-N-S Number Status Types). |
Notification files are text files. They contain one row for each notification, which is in JSON. Each row starts with the notification type and then includes applicable details of the D-U-N-S Number for which the notification applies. The notifications are grouped by D-U-N-S Numbers and then are in ascending order by timestamp. The notifications for a single D-U-N-S Number will never be split across multiple files; the order of D-U-N-S Numbers in a file or between files is not guaranteed.
D-U-N-S Numbers monitoring notification files use the following naming convention:
Intra_Day Notifications: REFERENCE_YYYYMMDDHHMMSS_FILE-TYPE_FILE-NUMBER
Daily Notifications: REFERENCE_YYYYMMDDHHMMSS_FILE-TYPE_FILE-NUMBER
Weekly Notifications: REFERENCE_YYYYMMDD_FILE-TYPE_FILE-NUMBER
Monthly Notifications: REFERENCE_YYYYMM_FILE-TYPE_FILE-NUMBER
Where:
A Notification file may contain:
Each record in the file may contain the following elements, based on the notification type.
File Element | Data Type | Description | Notification Types |
---|---|---|---|
type | String | The type of notification. | All |
organization | Object | The details of the entity's organization. | All |
organization.duns | String | The D-U-N-S Number is an identification number assigned by Dun & Bradstreet that uniquely identifies the entity in accordance with the Data Universal Numbering System (DUNS). | All |
elements | Array | Array of elements of the D-U-N-S Number that have been updated. | UPDATE, SEED |
elements.element | String | JSON Path of element that has been updated. | UPDATE, SEED |
elelments.previous | String | Previous value of the element.See the specific product response for details on attributes and values included in this section. | UPDATE |
elements.current | String | Current value of the element.See the specific product response for details on attributes and values included in this section. | UPDATE |
elements.timestamp | String | The date and time, in ISO 8601 UTC Z standards, when this element was updated by the application. | UPDATE |
organization.dunsControlStatus | String | The details of the entity established to provide products and/or services in the marketplace or to the community. | TRANSFER, DELETE, UNDELETE |
organization.dunsControlStatus.dunsTransfers | Array | History of D-U-N-S Number deletes and D-U-N-S Number transfer for this entity. | TRANSFER |
organization.dunsControlStatus.dunsTransfers.retainedDUNS | String | In the event that the D-U-N-S Number of this entity is retired, this field contains the D-U-N-S Number to reference for future product requests | TRANSFER |
Monitoring tracks several types of changes:
Notification Type | Explanation |
---|---|
DELETE | The D-U-N-S Number has been deleted; it is no longer available through Direct+ APIs or Monitoring. |
ENTER | The D-U-N-S entered the Universe in the Monitoring
Registration. This may occur when a new D-U-N-S Number is
created or an existing one is changed so it now meets the
Universe criteria. Example 1: Registration is configured for Commercially Active Universe.
|
EXIT | The D-U-N-S Number is no longer part of the Universe in the
Monitoring Registration. This occurs when a D-U-N-S Number is
deleted, transferred, or the content changes so that it no
longer meets the Universe criteria. Example 1: Registration is configured for Commercially Active Universe
|
REVIEWED | The review of the D-U-N-S Number has been completed; changes notifications will now be processed for this D-U-N-S Number. |
SEED |
|
TRANSFER | The D-U-N-S Number has been transferred to another D-U-N-S Number; the retained D-U-N-S Number is also transmitted. |
UNDELETE | The D-U-N-S Number has been undeleted and is now available through Direct+ APIs and Monitoring. |
UNDER_REVIEW | The D-U-N-S Number is currently under review. No change notifications will be received while the D-U-N-S Number is in this state. However, the D-U-N-S Number remains in the registration so when the status changes the appropriate notification(s) will be delivered based on the new status. |
UPDATE | Content related to the subject D-U-N-S Number has been updated. |
For Dun & Bradstreet Managed Universe Registrations, the notifications are only sent if the D-U-N-S Number meets the Universe conditions.
For LOD Registrations, the notifications are only sent if the D-U-N-S Number is part of the Monitoring Registration.
Unless otherwise noted, the information below applies to both UPDATE and FULL_PRODUCT registrations.
Activity | Notification Types for Universe Registrations | Notification Types for LOD Registrations | Notes |
---|---|---|---|
A new D-U-N-S Number is created. |
|
n/a | SEED record only included if Registration has Seed File = True. |
A D-U-N-S Number is marked as deleted. |
|
|
Any pending notifications for the registered D-U-N-S Number before it became deleted will be sent. However, while the D-U-N-S Number has a status of deleted, no further update notifications will be sent. UPDATE or SEED depends on Registration notificationType setting. |
A D-U-N-S Number is undeleted. |
|
|
For Universe registration, a SEED record only included if
Registration has Seed File = True. For LOD registration, a SEED record is included if Registration as Seed File = True OR notificationType is FULL_PRODUCT. |
The D-U-N-S Number data changes, which may include: - New content - Updated content - Removed content |
|
|
UPDATE or SEED depends on Registration notificationType setting. |
The D-U-N-S Number data changes cause it to no longer meet the Universe criteria. |
|
n/a | |
DUNS-A is transferred to DUNS-B. DUNS-A was in Registration; DUNS-B is not. | For DUNS-A
|
For DUNS-A
|
For LOD Registrations, modify Registration to remove DUNS-A and add DUNS-B. |
DUNS-A is transferred to DUNS-B. DUNS -B was in Registration; DUNS-A is not. | No notification. | No notification. | |
A D-U-N-S Number is placed under review. |
|
|
|
The review of a D-U-N-S Number is completed. |
|
|
SEED is only included if Registration included SEED request. |
A D-U-N-S Number is added to Registration. | n/a |
|
SEED is only included if Registration included SEED request. |
A D-U-N-S Number is removed from Registration. | n/a |
|
|
A D-U-N-S Number is under review AND is Transferred | For DUNS-A
|
|
If the registration does not include a Seed File = True, in order to baseline a D-U-N-S Number that has been added to the Registration or has Entered the Universe, a data API call can be used.
{
"type":"DELETE",
"organization":{
"duns":"217825255"
}
}
{
"type":"ENTER",
"organization":{
"duns":"217825255"
}
}
{
"type":"EXIT",
"organization":{
"duns":"217825255"
}
}
{
"type":"REVIEWED",
"organization": {
"duns":"217825255"
}
}
{
"type":"SEED",
"organization":{
"duns":"611710674",
...(product contents here)
}
}
{
"type":"TRANSFER",
"organization":{
"duns":"611710674",
"dunsControlStatus":{
"dunsTransfers"[{
"retainedDUNS":"064332299"
}
]
}
}
}
{
"type":"UNDELETE",
"organization":{
"duns":"217825255"
}
}
{
"type":"UNDER_REVIEW",
"organization":{
"duns":"217825255"
}
}
{
"type":"UPDATE",
"organization":{
"duns":"217825255"
}
"elements": [ {
"element":"organization.registeredAddress.streetName",
"previous":"BUILDING 4, HATTERS LANE, CROXLEY GREENBUSINESS PARK",
"current":"BUILDING 4, HATTERS LANE",
}
]
{
"type":"UPDATE",
"organization":{
"duns":"217825255"
}
"elements": [ {
"element": "organization.industryCodes",
"previous": [
{
"typeDescription": "North American Industry Classification System 2012",
"description": "Unclassified Establishments",
"priority": 1,
"code": "999990",
"typeDnBCode": 24664
},
{
"typeDescription": "D&B Hoovers Industry Code",
"description": "Nonclassifiable establishments",
"priority": 1,
"code": "2058",
"typeDnBCode": 25838 },
{
"typeDescription": "US Standard Industry Code 1987 - 4 digit",
"description": "Nonclassified establishment",
"priority": 1,
"code": "9999",
"typeDnBCode": 399
},
{
"typeDescription": "D&B Standard Industry Code",
"description": "Nonclassifiable establishments",
"priority": 1,
"code": "99990000",
"typeDnBCode": 3599
},
{
"typeDescription": "NACE Revision 2",
"description": "Undetermined",
"priority": 1,
"code": "9999",
"typeDnBCode": 29104
}
],
"current": [
{
"code": "238210",
"description": "Electrical Contractors",
"typeDescription": "North American Industry Classification System 2012",
"typeDnBCode": 24664,
"priority": 1
},
{
"code": "1857",
"description": "Electrical Contractors",
"typeDescription": "D&B Hoovers Industry Code",
"typeDnBCode": 25838,
"priority": 1
},
{
"code": "1731",
"description": "Electrical contractor",
"typeDescription": "US Standard Industry Code 1987 - 4 digit",
"typeDnBCode": 399,
"priority": 1
},
{
"code": "17310203",
"description": "Environmental system control installation",
"typeDescription": "D&B Standard Industry Code",
"typeDnBCode": 3599,
"priority": 1
},
{
"code": "C",
"description": "Construction",
"typeDescription": "D&B Standard Major Industry Code",
"typeDnBCode": 24657,
"priority": 1
},
{
"code": "4321",
"description": "Electrical installation",
"typeDescription": "NACE Revision 2",
"typeDnBCode": 29104,
"priority": 1
}
]
}
]
{
"type":"UPDATE",
"organization":{
"duns":"217825255"
}
"elements": [ {
"element":"organization.telephone",
"previous": [
{
"telephoneNumber":"5555551212",
"isdCode":"86",
"isUnreachable":false
}
],
"current": [
{
"telephoneNumber":"5555551000",
"isdCode":"86",
"isUnreachable":false
}
],
"timestamp":"2016-07-29T13:22:19Z"
}
]
{
"type":"UPDATE",
"organization":{
"duns":"217825255"
}
"elements": [ {
"element":"organization.telephone",
"previous":[],
"current":[
{
"telephoneNumber":"57687353158",
"isdCode":"86",
"isUnreachable":false
}
],
"timestamp":"2016-07-29T13:22:19Z"
}
]
{
"type":"UPDATE",
"organization":{
"duns":"217825255"
}
"elements": [ {
"element":"organization.telephone",
"previous":[
{
"telephoneNumber":"5555551212",
"isdCode":"86",
"isUnreachable":false
}
],
"current":[]
}
]
Regular notifications will not be delivered under the following circumstances:
Maintenance Window
Periodically, the D&B Direct+ system must undergo maintenance. During these periods, notification delivery is suspended to ensure consistency with Direct+ API content.
When reinstated, notifications include all changes that occurred during the maintenance window.
During system maintenance monitoring notifications are not delivered. They are accumulated and packaged once the maintenance is complete. The delivered files contain each individual . This provides you with all the interim changes that occurred during the maintenance window.
NOTE: This is different than suppression. When a Monitoring Registration is suppressed, interim updates are not included in the notification once delivery is unsuppressed.
Suppressed Notifications
Notifications may be suppressed through the API. During this period, the system aggregates the changes for each day into a single UPDATE notification. When the notifications are unsuppressed, the aggregated notifications are delivered. The previous value is the last value delivered before the notifications were suppressed and the current value is the value of the last change before the notifications are delivered.
On Hold Notifications
Notifications may be placed on hold through the API (excluding UBO and Family Tree registrations). The On Hold state will retain the registration configurations, but the system will not process the registration. Registrations can be subsequently transitioned from the On Hold state to Current state. When it is changed from On Hold to Current, then the following logic applies:
In order for monitoring to deliver files to S3 and ensure they are encrypted, the monitoring user must be given access.
The following is sample configuration for the IAM policy to be applied:
{
"Version": "2012-10-17",
"Statement": [
{
"Sid": "Monitoring Bucket permissions",
"Effect": "Allow",
"Principal": {
"AWS": "arn:aws:iam::219829223284:user/otmutransfer"
},
"Action": "s3:PutObject",
"Resource": "arn:aws:s3:::customer-bucket-name/*"
}
]
}
{
{
"Sid": "Allow use of the key",
"Effect": "Allow",
"Principal": {
"AWS": "arn:aws:iam::219829223284:user/otmutransfer"
},
"Action": [
"kms:Encrypt",
"kms:ReEncrypt*",
"kms:GenerateDataKey*"
],
"Resource": "arn:aws:kms:us-east-1:219829223284:key/8d27048e-9b70-47a2-af7d-79982a417561" ---> Customer key ARN
}
All Universes include the following rules:
Description | Universe ID | Universe Rules |
---|---|---|
Full Universe | FULL | This universe includes D-U-N-S Numbers that meet the general rules listed above. No additional rules are applied. |
Active in Japan | ACTVJP | This universe includes D-U-N-S Numbers that meet all the following criteria: - Country is Japan (JP) - Operating Status is Active |
Alternative Linkage | LNKALT | This universe includes D-U-N-S Numbers that meet all the following criteria: - Alternative Linkage element is present and not null. |
Commercially Active | CMCLACTV | This universe includes D-U-N-S Numbers that meet all the following criteria: - Company is not de-listed - Mail is deliverable - Operating Status is Active |
Decision HQ | AASDHQ | This universe includes D-U-N-S Numbers that meet all the following criteria: - isStandalone=false or null |
Exclude Branches | EXBRCH | This universe includes D-U-N-S Numbers that meet all the following criteria: - Is not a branch |
Fortune 1000 | F1000 | This universe includes D-U-N-S Numbers that meet all the following criteria: - Fortune1000 = True - Operating status is Active |
Global IT Buydex | AASBIG | This universe includes D-U-N-S Numbers that meet all the following criteria: - IT Buydex element is present and not null - Operating status is Active |
Global Marketable & Corporate Linkage | MKTLNK | This universe includes D-U-N-S Numbers that meet all the following criteria: - dunsControlStatus.isMarketable is True - isStandalone is false. |
Material Change | AASMCU | This universe includes D-U-N-S Numbers that meet all the following criteria: Either - Opportunity Final Segment Code is present and not null. - Material Change Segment Code element is present and not null. And - Operating Status is Active |
Minority Linkage | LNKMIN | This universe includes D-U-N-S Numbers that meet all the following criteria: - Minority Linkage element is present and not null. |
Total Loss Predictor | AASTLP | This universe includes D-U-N-S Numbers that meet all the following criteria: - Total Loss Predictor element is present and not null. |
Upward Linkage | LNKUPD | This universe includes D-U-N-S Numbers that meet all the following criteria: - isStandalone is false |
Active in US | ACTVUS | This universe includes D-U-N-S Numbers that meet all the following criteria: - Country is United States (US) - Operating Status is Active |
Please refer to the Onboarding Guide by clicking here