CreateNotice
 | Note: CreateNotice replaces
CreateAlert, which was deprecated in
Falcon 6.3.
|
Syntax: CreateNotice("name", "value", expirationDays, "noticeSeverity", "externalEventCode", "entityAssociation", associatedScore, "freeFormText")
Arguments:
- name is the name of the notice (60-character limit). This argument is required. If you enter a name of length 0, the notice is not inserted into the database and a database error is generated.
- value is the notice ID.
- expirationDays is an integer indicating the number of days during which the notice will be presented in the Case Manager Notices window.
- noticeSeverity describes the severity of the notice. The maximum length is 10 bytes.
- externalEventCode identifies the source of the notice. The maximum length is 10 bytes.
- entityAssociation : This value is either
CUSTOMER,ACCOUNT,SERVICE, or " " (an empty string). It specifies the entity (an account, customer, or service) the notice is associated with. The default isSERVICE, that is, if entityAssociation is blank, empty, or unknown, the notice created will be of typeSERVICE. - associatedScore: If the notice is created based on a score, this integer is the score value associated with creation of the notice. A value between 0 and 999 is supported.
- freeFormText: Specifies additional details regarding the notice. The field is limited to 200 bytes (for each notice).
Return Type: None
Description: The notices associated with a case are displayed in the Case Manager Notices window with the most recent notice displayed at the bottom. Notices are aged off in line with the Expiration Days parameter specified in the CreateNotice function. As the aging criteria of cases are different from the aging of notices, there can be a scenario where the case is still in the system but the notice on it has expired. If you want the notices to persist longer, keep the Expiration Days parameter higher, an option could be to match it with the case status which has the longest aging criteria. Although this would not guarantee that the notice will persist for the life of the case, it will ensure the notice stays with the case for the longest period of time.
The Notices window shows any notices that contain the same customer, account, or service identifiers, and the most recent notice is displayed last. CreateNotice supports up to 10 notices per transaction.
To create a notice, the incoming transaction's
service_xid must have a value. If the value is blank and a rule tries to create a
SERVICE-level notice, the notice is not created and the server logs an error in pmax.log, similar to the following.
21035fba: hncRules Jun 21 13:22:06 : ERROR: write_dbfe_alert: IGNORING SERVICE-LEVEL NOTICE CREATION REQUEST BECAUSE THE FEED DOES NOT CONTAIN A SERVICE IDExample:
{
.....
CreateNotice("RuleHighScore900", CRTRAN25.transactionDate, 9, "SeverityHigh", "EventCode4", "SERVICE", ffmFrdCard.Score,
"Refer to the block decision matrix A when statusing this case.");
}This example invokes
CreateNotice when
ffmFrdCard.Score >= 900 and the transaction score for the service is over 900.
SERVICE indicates the notice that should be related to the PAN on the transaction.