Change Request Summary report Description

[rleir]

Hi,

When we run the Change Request Summary report  (Actions -> View Summary Report), the Description and Proposed Solution fields are blank.  The other fields get reported correctly. 

We also get an Error which might not be related:

[ContainerBackgroundProcessor[StandardEngine[Catalina]]] com.ptc.netmarkets.util.misc.DBOperationHttpSessionListener - No active method context

wt.method.server - Dead method context [id= ... ... ]  threadName=Thread-nnn] was never unregistered 

This is a Jasper report.

thanks -- Rick

[rleir]

Hi team:

This failure is consistent on every run of the  Change Request Summary report.  

Same on a very lightly loaded WC server.

(I have been told 'This would be a priority issue')

We also get an Error log:

Message: Dead method context [id=nnn, threadName=Thread-nn] was never unregistered
Context Label: /Windchill/netmarkets/jsp/report/jasper/jasperAsyncHeartBeat.jsp

Is that related?

Do we have to configure HeartBeat as described in the following page?

https://community.jaspersoft.com/documentation/jasperreports-server-administration-guide/v550/configuring-heartbeat

I have not mentioned this to our security people yet.

thanks -- Rick

[rleir]

Hot on the trail through:

$ view loadFiles/reports/LoadJasperChangeManagementSummaryReports.xml
$ view codebase/netmarkets/jsp/changeReports/ChangeRequestSummaryReport.jsp
$ view codebase/netmarkets/jsp/changeReports/ChangeItemSummaryReport.jspf    
$ view codebase/netmarkets/javascript/change2/changeReports.js

Still trying to get the Description and Proposed fields populated.   Please help

cheers -- Rick

[SWeiler_9940261 · Accepted solution]

What version of Windchill? This could be because description and proposed solution are RTF as of 11.1. See support case:

https://www.ptc.com/en/support/article/cs298196?language=en&posno=2&q=rich%20text&source=search

[rleir]

As you say, this is probably a RTF issue. But after much work trying to reconfigure everything to work with RTF, we come up with a roadblock in ODATA which does not seem to support the RTF fields. 

Who is able to get the RTF fields via ODATA? How did you do it?

thanks -- Rick

[rleir]

Also, is there a way to configure the Change Request Summary report to use the old non-RTF fields? This is the OOTB Jasper report at

domain.com/Windchill/netmarkets/jsp/report/jasper/reportViewAsync.jsp?
contextOid=VR%3Awt.change2.WTChangeRequest2%3A170009271&
oid=com.ptc.windchill.enterprise.report.Report%3A374985952& 

When viewing a Change Request, in the Action menu select 'View Summary Report'.

thanks -- Rick

[rleir]

Ping

[rleir]

The .jasper file can be found at:

Windchill]$ ll codebase/JasperReports/Change\ Management/Change\ Request\ Summary\ Report.jasper

-rwxr-xr-x. 1 winadmin winadmin 160069 Jul 29 23:55 'codebase/JasperReports/Change Management/Change Request Summary Report.jasper'

You can take a copy of this and open it in the Community Version of Jasper Studio. Click the 'Source' tab and you see the .jrxml code: it seems to have been de-compiled from the .jasper. The rich text fields can be located. Small changes were made to the data-source spec code so we would get the non-richtext data. But we still get a blank output in these fields. The relevant .jrxml lines, 782 and 783:

								<textElement markup="html"/>
								<textFieldExpression><![CDATA[$F{Description}]]></textFieldExpression>

Maybe I need to locate the data adaptor class and modify that too?