Skip to main content
D
DA_145732124-Participant
4-Participant
June 22, 2026
Question

Visualization Job Override Issue in Windchill – Older Low-Priority Job Replacing Latest Representation

  • June 22, 2026
  • 2 replies
  • 12 views

  • Scenario 1

    • A user creates a CAD part (EPMDocument) and performs a check-in.

      • This triggers a visualization job.
      • The job is submitted to a low-priority queue.
      • Description is blank.

    • Later, the user creates a Change Notice (CN) and submits it.

      • This triggers another visualization job.
      • The job is submitted to a medium-priority queue.
      • Description is "Submitted".
  • Issue in Scenario 1:
    • When the object is sent for review, initially the correct ("Submitted") representation is visible.
      • However, once the earlier low-priority job (triggered during check-in) executes later:
        • It republishes the representation
        • Overrides the "Submitted" representation with the blank one
      • As a result, the reviewer ends up seeing an outdated representation instead of the latest one.
  • Scenario 2

    • Reviewer sends the object for rework:

      • A new visualization job is triggered (with description like "Rework")

    • After rework, the object is again submitted for review:

      • Another visualization job is triggered (description: "Submitted")
  • Issue in scenario 2
    • Ideally:
      • The latest "Submitted" representation should override the "Rework" representation.
      • But currently:
        • The behavior is inconsistent
        • The older representation may override the newer one
        • In some cases, the sequence happens in reverse (vice versa).

2 replies

T
TDT17-Peridot
17-Peridot
June 22, 2026

Hi ​@DA_14573212,

In Scenario 1, I just wanted to understand the behavior.
When you say that the "Submitted" representation is overridden by a blank representation, does that mean the blank representation becomes the default representation?
I would expect to see two representations in the Representations/Annotations table.
The blank representation as the default representation.
The submitted representation as a non-default representation.
Is my understanding correct?

D
DA_145732124-ParticipantAuthor
4-Participant
June 22, 2026

Exactly, the Blank (Description) representation overrides as default representation over the Submitted representation (Old default).

T
TDT17-Peridot
17-Peridot
June 22, 2026

I believe the issue is primarily caused by the priority change.
I would suggest setting the all triggers priority to Medium, as this would likely resolve the issue with minimal effort.
Otherwise, you may need to implement a customization to identify and delete the existing job whenever a new job is created.

D
DA_145732124-ParticipantAuthor
4-Participant
June 22, 2026

Moving everything to medium will make the purpose invalid takes too much time to for medium and less time for Low, (you may need to implement a customization to identify and delete the existing job) do you have any idea to achieve this that would be a better solution.

T
TDT17-Peridot
17-Peridot
June 22, 2026

The customization is quite complex. I implemented a similar solution using listeners.
If these are the use cases causing the job override issue in your system, I would recommend proceeding with Medium priority for the triggers, as it would be a much simpler solution.
Also, how busy are your workers? Do they process a large volume of publishing jobs?

D
DA_145732124-ParticipantAuthor
4-Participant
June 22, 2026

Our Publishing volumes are very large, moving to medium not feasible, can you tell me what Api you used to achieve that solution

Terms & ConditionsAccessibility statement