Skip to main content
Solved

Quality Seal status change date tracking

  • October 9, 2025
  • 5 replies
  • 73 views

Hi, we would like to set some automation to inform users about a Fact sheet is long time in broken seal status. How to get this information? Is this possible at all, maybe with graphql query?

In addition would be nice to have a dashboard to make this information visible (which factsheet is since when in QS broken for example)

thx for all the advice!

Best answer by Carsten

Hi ​@PeK ,
first get all FS-ids with QS Broken, then use

….

    graphql_query = """

 {allLogEvents(

    factSheetId: "%s"

    first: 1

    eventTypes: QUALITY_SEAL_BROKEN

  )

  {

    edges {

      node {

        id

        newValue

        createdAt

      }

    }

  }

  }

    """ % (factsheetidd)

….

I did not find a solution with filtering by date. What I did, I added a field Quality seal last broken just visible to the accountable subscriber. I just query all factsheets with this QS broken and this date field empty and fill it by a daily scheduled job. Another job creates a reminder to the accountable if the data is above a configurable threshold. When a QS is approved the content of  this file is deleted (search QS Approved and Quality seal last broken is not empty).
Best regards,
Carsten

5 replies

justinharclerode
Community Manager
Forum|alt.badge.img+1

Hi thanks for the question! 

 

You can now setup automation emails to send to end users that there quality seal is expiring and they need to update. The feature is here email automation. Additionally you can set an automation to create a to-do and have it expire in x-days. You could also use the To-Do API endpoint (/services/pathfinder/v1/todos) with a tool like Postman to extract all open To-Dos, including their related Fact Sheet IDs. Then, retrieve subscriber details for those Fact Sheets via the Fact Sheet API and combine the data. Then, load it into a reporting or visualization tool (e.g., Power BI, Excel, or Tableau) to create a report showing open To-Dos by subscriber. Using the external link function on dashboards you can then visual like this in LeanIX with active interactive filters. 


  • Author
  • Rookie
  • November 7, 2025

HI, ok, many thanks - the e-mail notification and the to-do (with expiration days) i’m aware of, and we are using it already. The issue is, that many users are not reacting to the to-do and once it’s due nothing happen. We somehow would like to remind these users (automatically) for example if a factsheet QS is more then 30days broken. 

According to the understanding from the API options, i cannot get out the date, right? So since when the factsheet status is for example broken? Or do i need to get the this info from the to-do details? So can i get for example the creation date of the to-do via API?

thx


  • Rookie
  • November 17, 2025

Hi PeK,

one idea would be to use the audit_log, here you can see each change an facsheets and you could build your own history with it. I don’t know any internal option to really get the history and date of a field change, except the history of the factsheet itself.


Carsten
Forum|alt.badge.img+1
  • Everlasting Love
  • Answer
  • November 18, 2025

Hi ​@PeK ,
first get all FS-ids with QS Broken, then use

….

    graphql_query = """

 {allLogEvents(

    factSheetId: "%s"

    first: 1

    eventTypes: QUALITY_SEAL_BROKEN

  )

  {

    edges {

      node {

        id

        newValue

        createdAt

      }

    }

  }

  }

    """ % (factsheetidd)

….

I did not find a solution with filtering by date. What I did, I added a field Quality seal last broken just visible to the accountable subscriber. I just query all factsheets with this QS broken and this date field empty and fill it by a daily scheduled job. Another job creates a reminder to the accountable if the data is above a configurable threshold. When a QS is approved the content of  this file is deleted (search QS Approved and Quality seal last broken is not empty).
Best regards,
Carsten


  • Author
  • Rookie
  • November 21, 2025

ok Guys, many thanks - we try in these ways.