this page summarizes the data relating to the processing sessions carried out. Start time, end time and quantities made. Counters provide further details on work sessions:

ID: Session serial nmber

Job Template: Job Template used into the session

Start: Session starting time

End: Session ending time

Processed: Total number of document processed during the session

Completed: Total number of document completed during the session

Faulted: Total number of document rejected during the session

Jobs per hour: Number of documents per hour (average)

Avg Perso time: Global personalization time for a single document (average)

Avg Engrave time: laser engraving time for a single document (average)

A webhook is a mechanism that allows AIDA to communicate events and other relevant information to other software asynchronously using an HTTP request. A webhook is a mechanism for sending automated notifications or data updates from one system (the sender) to another system (the receiver). It works by establishing a callback URL in the receiver system, which the sender system can access. When a specific event or update occurs in the sender system, it sends an HTTP POST request containing relevant data to the specified URL. The receiver system, configured to listen for these incoming requests, receives the data and can perform actions or process it accordingly

The target webhook is nothing more than an endpoint exposed by the receiving software, which AIDA will use to send information. Webhooks are used in AIDA for real-time integration and communication between different applications or services, can be used in case of external application for smartcard or document chip personalization

EXAMPLE

http://ip_address.local:5000/webhook/route/

Where ip_adress.local is the IXLA system IP adress