APAR status
Closed as fixed if next.
Error description
When a record name is changed the record itself within TRIRIGA the new name is reflected, but when querying the record via integration URL for an XML output (ex. f=xml url parameter) the specid is still referring to the record with the original name. This happens with localized users. 1. Login with user user/password, where user is not in English-US (English UK used) 2. Go to Classifications, Roles. 3. Create a new Role. Tip: To facilitate the name should start with zzz as it will show in the bottom of the query. 4. Run this query using this URI: http://server:port/html/en/def ault/rest/Integration?action=query&module=Classification&bo=triR ole&&query=triRole%20-%20Find%20-%20All%20Roles%20For%20Lease%2 0A bstract&f=xml 5. Check the newly created Role listed in the results. 6. Find the role in Classifications, Roles. 7. Rename the role. Save&Close it 8. Re-run the URI query. The name is not showing the change.
Local fix
Use an US English user.
Problem summary
When a record name is changed, it is not being reflected when requested via Webservices. The issue was that integration query urls were not returning localized values when the response is in xml format. The fix is to add two new url parameters that can be used to localize xml results. They are f=xml-loc and f=pxml-loc.
Problem conclusion
When retrieving query results via Integration Object's external url functionality, was not returning localized xml results. Two new f parameter values have been introduced, which can be added to the url in order to return localized xml results. They are f=xml-loc and f=pxml-loc. The localized values will appear in the displayValue child element of the column element, for each record in the xml results. For example <displayValue><![CDATA[Some Localized Value]]></displayValue> This is targeted to the 1h2017 release
Temporary fix
Comments
APAR Information
APAR number
IV93379
Reported component name
TRI APPLCATION
Reported component ID
5725F26AB
Reported release
352
Status
CLOSED FIN
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2017-02-14
Closed date
2017-02-14
Last modified date
2017-02-14
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
R352 PSY
UP
[{"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":"352","Edition":"","Line of Business":{"code":"LOB59","label":"Sustainability Software"}}]
Document Information
Modified date:
30 March 2022