Skip to main content
7-Bedrock
February 19, 2026
Solved

Workflow System.out.println to logs working in Windchill 12, not in 13.0

  • February 19, 2026
  • 4 replies
  • 31 views
I am using Windchill PDMLink Release 13.0 and Datecode with CPS 13.0.2.6

I have several Workflows where I use system print statements for debugging purposes. Here is an example: System.out.println("+++++++"); In Windchill 12 this statement appears in the Background logs, not 13. Is there a switch to turn logging on in 13?

The history is "System.out.println" commands would be recorded in the Windchill logs for every version before Windchill 13.0. I do not see the logging anywhere for this output. Perhaps there is a switch in 13.0 that we are not aware of to direct system printing to the logs instead of some bit bucket.
    Best answer by rsutherland

    Thanks for the help and comments.  This problem solved itself.  The output started showing up in the logs as expected.  Maybe the system needed a reboot to flush whatever was causing the block.  I do use this output for debugging only so any Java errors are matched to what values variables have and what robots I am in.  Thanks again.

     

    Robert.

    4 replies

    16-Pearl
    February 20, 2026

    Hi @rsutherland,

    I have tested the same, and the sysout statements are not being printed in the BGMS logs.

    There could be multiple reasons for this, and PTC would be able to provide clarification.

    However, using System.out.println is not recommended. It is always advisable to use proper logging mechanisms such as Log4j.

    18-Opal
    February 21, 2026

    @rsutherland ,

     

    FYI, I tested System.out.println("****** testing 1 2 3 ..."); in an expression robot in Windchill 13.1.2.0 and it does write to BGMS log.

     

    I know you're on 13.0 but I thought knowing how it behaves in 13.1 would be worth knowing.

     

    Community Manager
    March 9, 2026

    Hi @rsutherland,

     

    I wanted to see if you got the help you needed.

    If so, please mark the appropriate reply as the Accepted Solution. It will help other members who may have the same question.
    Of course, if you have more to share on your issue, please pursue the conversation. 

     

    Thanks,
    Anurag 

    rsutherland7-BedrockAuthorAnswer
    7-Bedrock
    March 9, 2026

    Thanks for the help and comments.  This problem solved itself.  The output started showing up in the logs as expected.  Maybe the system needed a reboot to flush whatever was causing the block.  I do use this output for debugging only so any Java errors are matched to what values variables have and what robots I am in.  Thanks again.

     

    Robert.