Update a Notification Specification
patch
/bcws/webresources/v1.0/notificationManagement/notificationSpec/{id}
Updates the notification specification with the specified ID.
Request
Path Parameters
-
id(required): string
The notification specification ID, for example: 0.0.0.1+-notification_spec+1234567
Supported Media Types
- application/xml
- application/json
The notification specification to update. The minimum required parameters are:
- name
Root Schema : schema
Type:
Show Source
object
-
advanceNotifications(required): array
advanceNotifications
-
aggregateMode: integer
(int32)
Aggregation mode. Allowed Values: 0 (Send multiple notifications), 1 (Send consolidated single notification with details from all).
-
category(required): string
Free text. Use this field for classification.
-
createdAt(required): string
The creation date for the notification specification.
-
criteria(required): array
criteria
-
deliveryControlFlag: integer
(int32)
The notification control flag type. Allowed Values:
- 0 (Always Deliver)
- 1 (No delivery in silent period)
-
deliveryMethods(required): array
deliveryMethods
-
deliverySpec(required): array
deliverySpec
-
descr(required): string
The notification specification description.
-
expiresAt(required): string
The date when the notification specification expires.
-
href(required): string
The unique resource URL, used to get the notification specification object.
-
id(required): string
The notification specification ID.
-
modifiedAt(required): string
The modification date for the notification specification.
-
name(required): string
The notification specification name.
-
optType: integer
(int32)
The notification Opt In/Opt Out options. Allowed Values:
- 1 (Requires opt in)
- 2 (Requires opt out)
- 3 (Mandatory)
-
scope: integer
(int32)
The notification scope. Allowed Values:
- 1 (System)
- 2 (User)
-
startsAt(required): string
The start date for the notification specification.
-
status(required): string
The notification specification status. Allowed values: ACTIVE, INACTIVE, EXPIRED
-
systemEvent(required): string
The notification event POID type.
-
triggerType: integer
(int32)
The notification trigger type. Allowed Values:
- 0 (All)
- 1 (System)
- 2 (Auto)
-
type: integer
(int32)
The notification type. Allowed Values:
- 1 (Advance)
- 2 (Real-time)
- 3 (Predefined)
- 4 (First transaction)
- 5 (Post-due)
Nested Schema : NotificationDeliverySchedule
Type:
Show Source
object
-
offsetUnit: integer
(int32)
The notification delivery schedule offset type. Allowed values:
- 1 (Minute)
- 3 (Hour)
- 4 (Day)
- 5 (Week)
- 2 (Month)
- 0 (Year)
-
offsetValue(required): string
The notification delivery schedule offset value.
Nested Schema : NotificationCriteria
Type:
Show Source
object
-
dataType: integer
(int32)
The notification data type.The notification criteria data type. Allowed Values:
- 1 (Integer)
- 3 (Enumeration)
- 5 (String)
- 7 (POID)
- 8 (Timestamp)
- 14 (Decimal)
-
key(required): string
The notification criteria key.
-
operator: integer
(int32)
The operator for the qualifier. Allowed values:
- 0 (Equals)
- 1 (Less than)
- 2 (Greater than)
- 3 (Less than or equals)
- 4 (Greater than or equals)
- 5 (Not equal)
- 6 (Contained in string)
- 7 (Like)
-
value(required): string
The notification criteria value.
Nested Schema : NotificationDeliveryMethod
Type:
Show Source
object
-
id(required): string
The notification delivery method ID.
-
name(required): string
The notification delivery method name.
-
status: integer
(int32)
The notification delivery method status. Allowed Values:
- 1 (Active)
- 2 (Inactive)
Nested Schema : NotificationDeliverySpec
Type:
Show Source
object
-
dayOfMonth: integer
(int32)
The day of the month.
-
dayOfWeek: integer
(int32)
The day of the week.
-
deliveryPeriodEnd(required): string
The notification delivery end time. Pattern: ^([0-1]?\d|2[0-3])(?::([0-5]?\d))?(?::([0-5]?\d))?$
The notification specification to update. The minimum required parameters are:
- name
Root Schema : schema
Type:
Show Source
object
-
advanceNotifications(required): array
advanceNotifications
-
aggregateMode: integer
(int32)
Aggregation mode. Allowed Values: 0 (Send multiple notifications), 1 (Send consolidated single notification with details from all).
-
category(required): string
Free text. Use this field for classification.
-
createdAt(required): string
The creation date for the notification specification.
-
criteria(required): array
criteria
-
deliveryControlFlag: integer
(int32)
The notification control flag type. Allowed Values:
- 0 (Always Deliver)
- 1 (No delivery in silent period)
-
deliveryMethods(required): array
deliveryMethods
-
deliverySpec(required): array
deliverySpec
-
descr(required): string
The notification specification description.
-
expiresAt(required): string
The date when the notification specification expires.
-
href(required): string
The unique resource URL, used to get the notification specification object.
-
id(required): string
The notification specification ID.
-
modifiedAt(required): string
The modification date for the notification specification.
-
name(required): string
The notification specification name.
-
optType: integer
(int32)
The notification Opt In/Opt Out options. Allowed Values:
- 1 (Requires opt in)
- 2 (Requires opt out)
- 3 (Mandatory)
-
scope: integer
(int32)
The notification scope. Allowed Values:
- 1 (System)
- 2 (User)
-
startsAt(required): string
The start date for the notification specification.
-
status(required): string
The notification specification status. Allowed values: ACTIVE, INACTIVE, EXPIRED
-
systemEvent(required): string
The notification event POID type.
-
triggerType: integer
(int32)
The notification trigger type. Allowed Values:
- 0 (All)
- 1 (System)
- 2 (Auto)
-
type: integer
(int32)
The notification type. Allowed Values:
- 1 (Advance)
- 2 (Real-time)
- 3 (Predefined)
- 4 (First transaction)
- 5 (Post-due)
Nested Schema : NotificationDeliverySchedule
Type:
Show Source
object
-
offsetUnit: integer
(int32)
The notification delivery schedule offset type. Allowed values:
- 1 (Minute)
- 3 (Hour)
- 4 (Day)
- 5 (Week)
- 2 (Month)
- 0 (Year)
-
offsetValue(required): string
The notification delivery schedule offset value.
Nested Schema : NotificationCriteria
Type:
Show Source
object
-
dataType: integer
(int32)
The notification data type.The notification criteria data type. Allowed Values:
- 1 (Integer)
- 3 (Enumeration)
- 5 (String)
- 7 (POID)
- 8 (Timestamp)
- 14 (Decimal)
-
key(required): string
The notification criteria key.
-
operator: integer
(int32)
The operator for the qualifier. Allowed values:
- 0 (Equals)
- 1 (Less than)
- 2 (Greater than)
- 3 (Less than or equals)
- 4 (Greater than or equals)
- 5 (Not equal)
- 6 (Contained in string)
- 7 (Like)
-
value(required): string
The notification criteria value.
Nested Schema : NotificationDeliveryMethod
Type:
Show Source
object
-
id(required): string
The notification delivery method ID.
-
name(required): string
The notification delivery method name.
-
status: integer
(int32)
The notification delivery method status. Allowed Values:
- 1 (Active)
- 2 (Inactive)
Nested Schema : NotificationDeliverySpec
Type:
Show Source
object
-
dayOfMonth: integer
(int32)
The day of the month.
-
dayOfWeek: integer
(int32)
The day of the week.
-
deliveryPeriodEnd(required): string
The notification delivery end time. Pattern: ^([0-1]?\d|2[0-3])(?::([0-5]?\d))?(?::([0-5]?\d))?$
Response
201 Response
The notification specification was updated successfully.
500 Response
An error occurred. An exception has been raised.
Examples
This example shows how to update a notification specification by submitting a PUT request on the REST resource using cURL. For more information about cURL, see "Use cURL".
cURL Command
curl -X PUT 'http://hostname:port/bcws/webresources/version/notificationManagement/notificationSpec /0.0.0.1+-config-notificationSpec+ 2865053' -H 'content-type: application/json' -d @updateNotificationSpec.json
where:
- hostname is the URL for the Billing Care REST server.
- port is the port for the Billing Care REST server.
- version is the version of the API you're using, such as v1.0.
- updateNotificationSpec.json is the JSON file that specifies the details to update.
Example of Request Body
This example shows the contents of the updateNotificationSpec.json file sent as the request body.
[
{
"id": "0.0.0.1+-config-notification_spec+2865053",
"startsAt": "2022-11-21T09:28:00.000Z",
"expiresAt": "2023-10-28T18:29:59.000Z",
"name": "New Notification",
"descr": "descr updated",
"deliveryControlFlag": "SUPPRESS",
"systemEvent": "New Notification",
"type": "REALTIME",
"triggerType": "SYSTEM",
"scope": "USER",
"criteria": [
{
"key": "/account.ACCOUNT_NO",
"value": "12345",
"operator": "EQ",
"dataType": "STR"
}
],
"deliveryMethods": [
{
"id": "3",
"name": "EMAIL",
"status": "ACTIVE"
}
],
"deliverySpec": [
{
"firstTransaction": "WEEKS",
"deliveryPeriodEnd": "9:30",
"dayOfMonth": 31,
"dayOfWeek": 5
}
],
"advanceNotifications": [
{
"offsetUnit": "DAYS",
"offsetValue": "3"
}
]
}
]
Example of Response Body
This example shows the contents of the response body in JSON format.
{
"id": "0.0.0.1+-config-notification_spec+2865053",
"href": "http://hostname:port/bcws/webresources/version/notificationSpec/0.0.0.1+-config-notification_spec+2865053"
}