Typo in Script Variable name used in templates CALL.SLM.FULFILLMENT and CALL.SLM.FULFILLMENT_MAIL results in Violation error

Document ID : KB000087197
Last Modified Date : 14/04/2018
Show Technical Document Details
Issue:
Error Message :
Violation: |
or
Message |

The following templates:
 
CALL.SLM.FULFILLMENT
CALL.SLM.FULFILLMENT_MAIL

attempt to reference a variable name that contains a typo where violation is incorrectly spelled viloation, causing the message in the notification to remain empty.

The notification template dynamically creates it's message text. As a result of violation being misspelled, the violation (message) line is incorrectly displayed as:

Message: |

Note, there is no information/message text in this line.
0EMb0000001FZIt.png

The process tab that is being used to dynamically create the message spells violation in the script variables as viloation causing the problem.

Once the typo is corrected the Message is displayed correctly as:

Violation: U00045079 The status 'ENDED_NOT_OK - aborted' does not match the expected status 'ANY_OK'.

 
Environment:
OS Version: N/A
Cause:
Cause type:
Defect
Root Cause: Typo in the violation variable "viloation"
Affected:
: read &uc_slm_viloation_msg_number#,,
: read &uc_slm_viloation_msg_insert#,,
: set &slm_violation# = get_msg_txt(&uc_slm_viloation_msg_number#,&uc_slm_viloation_msg_insert#)
Resolution:
Update to a fix version listed below or a newer version if available.
 

Fix Status: Released

Fix Version(s):
Automation.Engine 12.1.0 - Available
Automation.Engine 12.0.4 - Available
Additional Information:
Workaround :
Correct the variable manually, by applying the following changes:
 
! *** incorrect line *** : read &uc_slm_viloation_msg_number#,,
: read &uc_slm_violation_msg_number#,,
 
! *** incorrect line *** : read &uc_slm_viloation_msg_insert#,,
: read &uc_slm_violation_msg_insert#,,
 
! *** incorrect line *** : set &slm_violation# = get_msg_txt(&uc_slm_viloation_msg_number#,&uc_slm_viloation_msg_insert#)
: set &slm_violation# = get_msg_txt(&uc_slm_violation_msg_number#,&uc_slm_violation_msg_insert#)
0EMb0000000IaoV.png