IJ06531: Parameter Values of a Notification Helper does not work properly

3.5.3-TIV-TAP-FP005-README
3.5.3-TIV-TAP-FP005-WIN
3.5.3-TIV-TAP-FP005-LIN
3.5.3-TIV-TAP-FP005-AIX

APAR status

• Closed as fixed if next.

Error description

• Symptom/Description
  
  The Parameter Field shows the placeholder when the string value
  is empty
  
  
  
  Steps to Reproduce
  
  1.    Go to Tools - Workflow Builder, Module triRequest, find WF
  triMoveRequest - triIssue ? Create NotificationHelper
  
  2.    Click the radio button, click revise
  
  3.    Click on Create triNotificationHelper? task. Click Edit
  map
  
  4.    In front of triInput4TX click X icon, uncheck the check
  box and click magnifying glass.
  
  5.    Find triDescpriptionTX (you can use ctrl+f), click radio
  button
  
  6.    Click Ok in Object Mapping window
  
  7.    Click on the Start task, click Publish
  
  8.    Make sure you are not a system user but any other with
  triPeople record associated.
  
  9.    Go to Requests ? My Requests
  
  10.    Select Space ? Move Request
  
  11.    Request is for me
  
  12.    From Building, Organization, Proposed Move Date ? any
  dummy values.
  
  13.    Make sure Describe Your Request is empty (this is
  triDescriptionTX field from triInput4TX)
  
  14.    Submit
  
  15.    Wait 1 minute
  
  16.    Go to reminders ? Notifications
  
  17.    Find the latest notification like
  
  18.    Open. Text contains {4}. It means Input4 wasn?t replaced
  because triDescriptionTX is empty.
  
  
  
  Result: Your Request for Move Services (1000605-0) was received
  on {4} and is being Processed.
  
  Expected result: Your Request for Move Services (1000605-0) was
  received on  and is being Processed.
  
  
  
  Fixed in version
  
  Resolved in TRIRIGA 3.6.0.0
  
  
  
  Fix in Description
  
  Notification content was displaying '{n}' for a parameter when
  its mapped field did not have a value. Now, an empty string
  displays for the parameter in this situation.
  (Tri-52053-IJ06531)
  

Local fix

• N/A
  

Problem summary

• Fixed a problem where Notification content displays '{n}' for a
  parameter when its mapped field does not have a value. The
  Notification now displays an empty string for the parameter in
  this situation. This issue will be resolved in our next major
  release version, which is tentatively planned for 1H 2018.
  

Problem conclusion

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

Applicable component levels