APAR status
Closed as fixed if next.
Error description
Open a notification Requirement Record. On the Notify person section, add a person. Open it, set it to role, than X out of the browser. Then open the record back up, and the fields are out of synch with the selection.
Local fix
No
Problem summary
The root cause was the meta data was getting out of sync if you canceled the record. To resolve this, I now call the triNotificationRule - Synchronous - On Change triRuleTypeLI workflow on the loading of the form. This ensures that the meta data for the person / role, is set properly if the user had canceled out before
Problem conclusion
Notification Rules for added to a Notification Requirement will now show the proper fields when the Person or Role option is selected. This is targeted to the 1h2017 application release.
Temporary fix
Comments
APAR Information
APAR number
IV93296
Reported component name
TRI APP PLTFM R
Reported component ID
5725F26RE
Reported release
350
Status
CLOSED FIN
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2017-02-10
Closed date
2017-02-16
Last modified date
2017-02-16
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Modules/Macros
999
Fix information
Applicable component levels
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSHEB3","label":"IBM TRIRIGA Application Platform"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"350","Edition":"","Line of Business":{"code":"LOB59","label":"Sustainability Software"}}]
Document Information
Modified date:
30 March 2022