Verify

How to Confirm the Status of the Graphics Inspection

This article is specific to the integration between VerifyAPI and Esko Automation Engine.


Concept

When you run a graphics inspection via VerifyAPI, there is a parameter in the results metadata (JSON or XML) that states if the inspection was able to find a match and compare the Master and Sample files, or if this match failed:

  • graphicsFilesNotComparable

    • false means that the inspection found a graphics match and ran successfully

    • true means that the algorithm wasn’t able to match the master and sample files to run the inspection. When this happens, the PDF report will show 0 results, “No Differences Found”.


How to update your Esko AE workflow to account for this parameter

CleanShot 2026-01-28 at 09.15.03@2x-20260128-142241.png

Step 1: Retrieve the graphics match parameter from the inspection results metadata

CleanShot 2026-01-28 at 09.24.24@2x-20260128-142452.png
  • Workflow Parameter: GraphicsNotComparable

  • New Value: jsonpath:$.tasks[0].inspectionResult.graphicsFilesNotComparable


Step 2: Add a new router to evaluate the graphics match parameter

CleanShot 2026-01-28 at 09.26.54@2x-20260128-142806.png

Step 3: Configure the workflow state then the inspection match fails

CleanShot 2026-01-28 at 09.28.58@2x-20260128-142916.png

This is just a demonstration of how the error state can be configured; you can reroute the workflow to any task/state that suits your processes.