Proofing report for more than one stage | Community
Skip to main content
spencer_w
spencer_w
Level 2
August 8, 2025
Solved

Proofing report for more than one stage

  • August 8, 2025
  • 2 replies
  • 282 views

Hi all, 

 

Is it possible to create a proofing approval report that will only show me proofs that have more than one stage? 

 

We're currently experiencing some trouble with non-reviewing users accidentally opening proofs and creating an automatic second stage. 

 

While I haven't found an easy way to prevent that, having a report that shows me proofs which have been effected is a good compromise. 

 

Our "normal" proofs always only have a single stage, so this report would help me spot anything that's gone awry at a glance. 

 

I tried using the built-in reporting filters, but I wasn't able to figure this out on my own. Is it even possible?

Best answer by skyehansen

I don't know that it's possible to show proofs with more that one stage. You can check for this in the API explorer. So you need to figure out other ways the two types of proof approval differ.

 

In your original post you mentioned that the second stage of review does not have a deadline -- implying that your "legit" proof workflows DO have a deadline every time.

 

With that in mind, I think probably one of the ways you can locate or distinguish between the two types (non-deadline vs deadline) would be to create a document version report and filter for proof deadline is null (or not null).**

 

**note that you would also want to filter on Document Version | Is Current Version to make sure you're only looking at the current versions.

** Looks like in a document report, the "Current Version | Proof Deadline" field may also work for this.

 

I did a very cursory test but you would want to test more extensively in your own environment to make sure this is a good solution for this situation.

2 replies

skyehansen
Community Advisor and Adobe Champion
skyehansenCommunity Advisor and Adobe ChampionAccepted solution
August 9, 2025

I don't know that it's possible to show proofs with more that one stage. You can check for this in the API explorer. So you need to figure out other ways the two types of proof approval differ.

 

In your original post you mentioned that the second stage of review does not have a deadline -- implying that your "legit" proof workflows DO have a deadline every time.

 

With that in mind, I think probably one of the ways you can locate or distinguish between the two types (non-deadline vs deadline) would be to create a document version report and filter for proof deadline is null (or not null).**

 

**note that you would also want to filter on Document Version | Is Current Version to make sure you're only looking at the current versions.

** Looks like in a document report, the "Current Version | Proof Deadline" field may also work for this.

 

I did a very cursory test but you would want to test more extensively in your own environment to make sure this is a good solution for this situation.

    spencer_w
    spencer_wAuthor
    Level 2
    September 2, 2025

    Thanks so much! This did exactly what we needed. I hadn't thought to use the null deadline as my data point but it worked perfectly in lieu of trying to filter by stage. 

     

    If anyone is searching in the future, we set the report filters as follows: 

    • Proof Approval >> Is Current Document Version = Equal True
    • Document Version >> Proof Deadline = Null
    • Document Version >> Proof Decision = Contains Pending 

    This allows us to see any current proofs with a pending decision that have a null deadline.

      kautuk_sahni
      Community Manager
      kautuk_sahniCommunity Manager
      Community Manager
      September 1, 2025

      @spencer_w just checking in! Were you able to get this resolved? If one of the replies above helped—whether it completely solved the issue or simply pointed you in the right direction—marking it as accepted can make it much easier for others with the same question to find a solution. And if you found a different way to fix it, sharing your approach would be a great contribution to the community. Your follow-up not only helps close the loop but also ensures others benefit from your experience. Thanks so much for being part of the conversation!

      Kautuk Sahni
      Terms & ConditionsAccessibility statement

      Loading footer...