# On clicking a faulted component dynamically opens a PDF to the page where that component is faulted **URL:** \ **Category:** Ignition\ **Tags:** ignition81, database, python, vision, scripting\ **Created:** [June 30, 2025, 3:52pm UTC](https://forum.inductiveautomation.com/t/on-clicking-a-faulted-component-dynamically-opens-a-pdf-to-the-page-where-that-component-is-faulted/107939 "2025-06-30T15:52:51Z")\ **Posts on this page:** 11\ **Page:** 1
**Author:** ![Chowmya\_C1](https://avatars.discourse-cdn.com/v4/letter/c/c0e974/32.png) [@Chowmya\_C1](https://forum.inductiveautomation.com/u/Chowmya_C1)\ **Post date:** [June 30, 2025, 3:52pm UTC](https://forum.inductiveautomation.com/t/on-clicking-a-faulted-component-dynamically-opens-a-pdf-to-the-page-where-that-component-is-faulted/107939/1 "2025-06-30T15:52:51Z")
Enhance the Ignition Vision/Perspective module to support dynamic fault detection and visualization. When a component faults during unit testing, the system will: Visually indicate the fault (e.g., red border) Allow user interaction (click) Open a PDF/image view showing the faulted component with a red highlight box ---
**Author:** ![Leor\_Fishman](https://avatars.discourse-cdn.com/v4/letter/l/e19adc/32.png) [@Leor\_Fishman](https://forum.inductiveautomation.com/u/Leor_Fishman)\ **Post date:** [June 30, 2025, 3:53pm UTC](https://forum.inductiveautomation.com/t/on-clicking-a-faulted-component-dynamically-opens-a-pdf-to-the-page-where-that-component-is-faulted/107939/2 "2025-06-30T15:53:50Z")
is this a feature request? Is this asking for help doing something? ---
**Author:** ![Chowmya\_C1](https://avatars.discourse-cdn.com/v4/letter/c/c0e974/32.png) [@Chowmya\_C1](https://forum.inductiveautomation.com/u/Chowmya_C1)\ **Post date:** [June 30, 2025, 3:59pm UTC](https://forum.inductiveautomation.com/t/on-clicking-a-faulted-component-dynamically-opens-a-pdf-to-the-page-where-that-component-is-faulted/107939/3 "2025-06-30T15:59:53Z")
it's a feature request, when a fault occurs on a component, wherever the component is present in the pdf it should be shown in pdf pages(like Compressor\_1 component is faulty means then wherever Compressor\_1 is present in unit schematics pdf those all components should be highlighted) ...then red background square shape around the component should be highlighted in the pdf page and when the component condition is healthy then normal pdf(schematics flow-that I've as pdf) should popup ---
**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\ **Post date:** [June 30, 2025, 4:06pm UTC](https://forum.inductiveautomation.com/t/on-clicking-a-faulted-component-dynamically-opens-a-pdf-to-the-page-where-that-component-is-faulted/107939/4 "2025-06-30T16:06:26Z")
Ignition only generates static PDFs via its reporting module. Nothing like what you describe is possible or likely to ever be posssible. ---
**Author:** ![Chowmya\_C1](https://avatars.discourse-cdn.com/v4/letter/c/c0e974/32.png) [@Chowmya\_C1](https://forum.inductiveautomation.com/u/Chowmya_C1)\ **Post date:** [July 1, 2025, 7:34am UTC](https://forum.inductiveautomation.com/t/on-clicking-a-faulted-component-dynamically-opens-a-pdf-to-the-page-where-that-component-is-faulted/107939/5 "2025-07-01T07:34:53Z")
okay @pturmel whether the component and wires can be highlighted in electrical schematics pdf when given the component names and wire numbers ---
**Author:** ![Chowmya\_C1](https://avatars.discourse-cdn.com/v4/letter/c/c0e974/32.png) [@Chowmya\_C1](https://forum.inductiveautomation.com/u/Chowmya_C1)\ **Post date:** [July 2, 2025, 8:28am UTC](https://forum.inductiveautomation.com/t/on-clicking-a-faulted-component-dynamically-opens-a-pdf-to-the-page-where-that-component-is-faulted/107939/6 "2025-07-02T08:28:04Z")
Additionally, if you're aware of any alternative approaches or workarounds to achieve a similar outcome, I'd be very grateful to hear your suggestions. ---
**Author:** ![nminchin](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/nminchin/32/6911_2.png) [@nminchin](https://forum.inductiveautomation.com/u/nminchin)\ **Post date:** [July 2, 2025, 9:18am UTC](https://forum.inductiveautomation.com/t/on-clicking-a-faulted-component-dynamically-opens-a-pdf-to-the-page-where-that-component-is-faulted/107939/7 "2025-07-02T09:18:24Z")
I'm confused. It sounds like you're trying to make a pdf (ie portable document format) file into a scada platform..? ---
**Author:** ![Chowmya\_C1](https://avatars.discourse-cdn.com/v4/letter/c/c0e974/32.png) [@Chowmya\_C1](https://forum.inductiveautomation.com/u/Chowmya_C1)\ **Post date:** [July 2, 2025, 9:41am UTC](https://forum.inductiveautomation.com/t/on-clicking-a-faulted-component-dynamically-opens-a-pdf-to-the-page-where-that-component-is-faulted/107939/8 "2025-07-02T09:41:18Z")
Yes, is there any chance to do python scripting in backend of pdf file to show the highlight of the selected components and wires in electrical schematics pdf ---
**Author:** ![nminchin](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/nminchin/32/6911_2.png) [@nminchin](https://forum.inductiveautomation.com/u/nminchin)\ **Post date:** [July 2, 2025, 10:07am UTC](https://forum.inductiveautomation.com/t/on-clicking-a-faulted-component-dynamically-opens-a-pdf-to-the-page-where-that-component-is-faulted/107939/9 "2025-07-02T10:07:46Z")
I mean, anything is possible I guess, but why? Why not just create Views properly in Vision or Perspective? ---
**Author:** ![robertm](https://avatars.discourse-cdn.com/v4/letter/r/ea5d25/32.png) [@robertm](https://forum.inductiveautomation.com/u/robertm)\ **Post date:** [July 2, 2025, 10:36am UTC](https://forum.inductiveautomation.com/t/on-clicking-a-faulted-component-dynamically-opens-a-pdf-to-the-page-where-that-component-is-faulted/107939/10 "2025-07-02T10:36:58Z")
From experience, I can tell you that the endeavor is a waste of time. Noone will keep the pdfs and links up to date as wiring and P&IDs evolve over time. Operator's will never look at them. Technicians may, but most prefer to work with paper copies at the panels. It sounds "neat" in theory, but it isn't practical or useful. Spend your time on developing views that annunciate alarms cleanly with pertnient information. Include the drawing page or P&ID id in the alarms. On my scada, I use mouseover on any device to give info about it. That way its unobtrusive 99% of the time, but can be accessed quickly. I also have the means to select any alarm in the journal and retrieve the Ignition tag path and PLC tag location. Those are more helpful than pdfs on a screen that will quickly become outdated and serve little use. ---
**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\ **Post date:** [July 2, 2025, 2:39pm UTC](https://forum.inductiveautomation.com/t/on-clicking-a-faulted-component-dynamically-opens-a-pdf-to-the-page-where-that-component-is-faulted/107939/11 "2025-07-02T14:39:44Z")
> [@Chowmya\_C1](#): > > do python scripting in backend of pdf The PDF format only allows javascript, and only for limited functionality. Ignition does not support injecting such code into the PDF, and PDF display tools would not have access to live Ignition data, even if you **could** inject the code. Use Perspective or Vision for **live** user interfaces.