18.08.2013 Views

Service Pack Readme (Adapt)

Service Pack Readme (Adapt)

Service Pack Readme (Adapt)

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

CE10WIN_EN_SP3<br />

All viewers<br />

ADAPT00376024<br />

Description:<br />

Patch ID: 36958127<br />

An error message may display sensitive information as part of the message when non-numeric characters are appended to a report number.<br />

Here is an example of a modified URL that would produce such an error message:<br />

http://server/crystal/enterprise/ePortfolio/en/reportviewer.csp?reportNumber=164ABC<br />

New Behavior:<br />

This problem is resolved.<br />

ADAPT00388041<br />

Description:<br />

Patch ID: 37063101<br />

When users view reports in Crystal Enterprise that contain memo fields with the "Can Grow" option selected and the "Keep Object Together"<br />

deselected, the memo field shows the last line of text at the bottom of the page and sometimes repeats that line at the top of the next page.<br />

New Behavior:<br />

This problem is resolved.<br />

ADAPT00388635<br />

Description:<br />

Patch ID: 37215967<br />

When reports that use an edit mask in a parameter are viewed in the ActiveX viewer, reports show incorrect or missing data.<br />

The cause of the problem is that underscore characters, which denote the length of the edit mask, are being appended to the end of the value<br />

entered. So, the value never matches a value in the database and, therefore, no data is returned.<br />

New Behavior:<br />

Underscore characters, rather than being appended to the end of the value, are replaced by values in the edit mask. The correct data is returned<br />

from the database.<br />

Automation<br />

ADAPT00376798<br />

Description:<br />

Patch ID: 37143852<br />

Report data may fail to be exported when users export a report through a Viewer in the Java Reporting Component (JRC).<br />

In that case, the record selection formula compares a database field against a parameter. For example:<br />

{Customer.Country} = {?country}<br />

This problem occurs when the report’s parameter field and database field are both strings, and the value of the parameter is empty. That is, the<br />

value that is provided to the parameter when the report is refreshed is as follows: ""<br />

New Behavior:<br />

This problem is resolved.<br />

Business View

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!