JSON Response Tags are Shuffled in REST Step
Fixed JSON elements order. Now it is preserved.
Support Case: 00888721
Invoke Call Not Working
Removed the full path name from the MultiPartMime step. Only the file name is passed when the file is uploaded.
Support Case: 00917446
File Encoding Does Not Work Correctly
Added an option for Platform Default to encoding.
Support Case: 00933291
Updated the Following Pages:
The HTTP/HTML Step Does Not Show the Response Headers
Corrected an issue to show the correct response headers.
Support Case: 00932920
Not Able to Format JSON Payload in VSI File
Fixed a defect in our JSON editor that prevents formatting of JSON arrays.
Support Case: 00902683
Removed Content-type header if response does not have a body.
Support Case: 00867834
Can't See Events in Inspection View
Inspection view was not showing data if the request details contained double quotes. Fixed to handle this scenario.
Support Case: 00889310
Value Included Japanese Characters for Uploading File is Recorded Incorrectly for Website Recording
Fixed a problem with Japanese translation for a string; now the value "Base64 encoded data" appears in English even on a Japanese machine.
Support Case: 00902573
Date Format wstimestampformat Not Detected When Generating VSI From RR Pairs
Fixed live response date timezone and Zulu timezone. Previously, the date with time zone (or time zone offset) was written incorrectly. The time zone was truncated, then the response date was written in the system time zone and the time zone was concatenated. Now, we retrieve the time zone offset from the RR response file, and write response date in that time zone offset. We also fixed Zulu time zone in the live requests. Before, 2017-09-18 15:08:20.888Z date format was not parsed successfully, so VSE took it as a string, not as a date.
Support Case: 00904196
Multiple Services Receive Repeated Requests
In this defect we fixed the issue with Inspection view in 10.2 where in each transaction shows two false no match and one correct match entry.
Support Case: 00928159
Virtual Service from WADL
In a virtual service created from WADL, if its response has an empty body, nothing is returned (empty text). Before, the response was “UNDEFINED”.
Support Case: 00934882
Second Inspector View Windows Can't be Stretched
You can now stretch all Inspector View windows.
Support Case: 00936805
Basepath Not Consistent When Creating VS From RR Pairs
Always remove the query and fragment portions of a request URI when determining the common base path for transactions on a HTTP protocol handler, This will give consistent results when one or more transactions are recorded/imported.
Defect: DE340845, DE322966
Support Case: 00941998
Error on DevTest Portal "Creating transactions from specification failed"
Fixed visual service creation from WSDL bundle.
Support Case: 00943581
Invalid Responses for Data Driven Virtual Services
In a data driven virtual service, response inner properties are evaluated after outer properties have been resolved (evaluated). Now, response properties are not cached.
Support Case: 009938630
SV Power Users Can't Reset Password
Updated code to allow SV Power users to reset their password.
Support Case: 00974382
Logging into Portal with no Broker Running Throws Exceptions in Registry
Added a warning message in the registry log file if broker is not available:
2018-01-15 10:31:59,930Z (11:31) [qtp1925215388-371] WARN com.ca.pf.invoke.SolrService - Broker is not available: Connect to localhost:1508 [localhost/127.0.0.1] failed: Connection refused: connect
Support Case: 00869676
Creating a REST VS from RR-pairs Includes the Parameters in the Basepath
Fixed a bug in Workstation for both 9.1 and 10.2 where creating more than one service by importing R/R pairs caused all subsequent R/R imports to use the HTTP transport protocol config of whatever the first import was.
Support Case: 00870530
First Four COMMAREA Bytes to be Used as a Filter in Virtualization Needs to be Part of Workstation
We made an enhancement to filter recording and playback based on COMMAREA contents. We added a new config parameter named
FiltersApplyToCA. Details of this parameter have been added to the CNTL dataset.
Support Case: 00878392
Suite Execution Detail Report Shows Incorrect Colors
Made a fix so that when the UI was shown in Japanese, that the pass and fail options showed green and red on the Suite Execution Detail report.
Support Case: 00895466
Setting lisa.log.level to Warn or Error Does Not Eliminate all INFO Lines in the Agent Log
Agent log setting changes made in the Portal were not persisted in the remote agent’s rules.xml files. This fix corrects that.
Support Case: 00899926
VSE(s) in Performance Mode Count is Not Populating on Enterprise Dashboard
Fixed a defect that caused the "Performance VSE" count that is shown on the Enterprise Dashboard home page to show a count of zero instead of the true count. The error was specific to customers who use Oracle for their Enterprise Dashboard database.
Support Case: 00911493
Cannot Switch the Language setting to Japanese for Enterprise Dashboard
When using IE as the browser for Enterprise Dashboard, changing the language preference did not always cause the page to re-display with the new language preference.
Support Case: 00933113
Portal - VSE - List of VS and Collapse/hide Menu
Fixed an issue when you collapse or hide the menu, the array of virtual services on a VSE did not expand.
Support Case: 00942128
Error Log from Enterprise Dashboard Service After Upgrading to 10.2
Fixed a concurrency bug that could prevent the Enterprise Dashboard home page from loading when multiple users try to load the home page concurrently.
Support Case: 00952772
Portal.log file goes Beyond 10M
Created a fix to roll the portal log file.
Support Case: 00952772
Error from Portal Service
Removed non-informative messages from Portal log.
Support Case: 00967368
MAR File Gets Downloaded with Random Characters as the File Name
Fixed naming of MAR files downloaded from Portal.
Support Case: 00965021
Failed to Make SSL Connection to the Listener (IMS Connect)
Reverted a change in 10.2.4 with default SSL/TLS protocols in order to preserve backwards compatibility with older servers without reconfiguration. TLSv1.1 or TLSv1.2 can still be forced by defining 'https.protocols' in local.properties. For example: https.protocols=TLSv1.2,TLSv1.1,TLSv1,SSLv3.
Defect: DE349755, DE349756
Portal Reporting Issue
Corrected an issue where the portal.log file was not wrapping.
Support Case: 00972772