Understanding the Device Usage version 1.10 configuration data for e‑Task 5, e‑Task 4 and e‑Task 3 printers
Learn about the device usage version for e‑Task 5, e‑Task 4 and e‑Task 3 printers.
|
Setting |
Description |
|---|---|
|
Site ID |
The site ID that the printer uses for reports. If this setting is not specified, then the default site code in LDD is used. |
|
Server Type |
Determines the server type that the usage data is being reported to. Possible values
|
|
Server URL |
The text shown on the login screen. If this setting is not specified, then the default text is used. This setting is the URL used to send data to the server. Use the following format for the LDD Server Type value: Where is the host name or IP address of the LDD load balancer server. |
|
Track Copy |
When enabled, copy jobs on the printer are tracked. We recommend this method for tracking copies when Print Release quotas are not used. If quotas are enabled, then LDD tracks copy jobs and the Track Copy setting must not be enabled. Note: During the Copy or Copy Cancel workflow, the Track Copy and Track Copy Cancel settings must not be enabled at the same time on a printer. Enabling these settings together causes duplicate entries in the PR_STATS report.
|
|
Track Copy Cancel |
When enabled, canceled copy jobs on the printer are tracked. We recommend this method to track regular copies and when quotas are enabled when using LDD. Only the actual pages printed are tracked when using this setting. Canceled copy jobs are sent immediately to the server for a real‑time user quota update. Note: During the Copy or Copy Cancel workflow, the Track Copy and Track Copy Cancel settings must not be enabled at the same time on a printer. Enabling these settings together causes duplicate entries in the PR_STATS report.
|
|
Track Email |
When enabled, emails sent from the printer are tracked. If LDD Print Release is used, then the From field shows the email address of the logged in user, and the Track Email setting must not be enabled. |
|
Track Fax Send |
When enabled, faxes sent from the printer are tracked. We recommend this method for tracking fax jobs. If Print Release (Fax + Profile) is used, then the Track Fax Send setting must not be enabled. |
|
Track Fax Receive |
When enabled, faxes sent to the printer are tracked. |
|
Track FTP |
When enabled, FTP scans sent from the printer are tracked. |
|
Track Print |
When enabled, print jobs from the printer are tracked. When you use LDD Print Release, we recommend this method to track only print jobs that are not sent using Print Release. Make sure that the Ignore Print Jobs From setting is enabled. |
|
Ignore Print Jobs From |
A comma-separated list of IP addresses that does not generate print tracking data. When using LDD Print Release, we recommend this method to avoid duplicate tracking entries when sending jobs using Print Release. If Track Print is enabled, then this list must include all the LDD application server addresses. Including LDD servers to this list results in duplicate tracking entries. |
|
Track Internal Print |
When enabled, print jobs such as fax confirmations, email confirmations, and menu settings are tracked. The report does not include user-initiated print jobs. |
|
Track Other Scans |
When enabled, jobs that generate a scan job are tracked. The report includes any other eSF application or LDD profile that is not part of the Print Release package. |
|
Include Profile Name in Data |
When enabled, the profile name that initiated the workflow or scan job is tracked. Note: We recommend enabling this setting only when necessary.
|
Job submission options for LDD
|
Setting |
Description |
|---|---|
|
Client ID |
The client credentials that are obtained from the identity service provider used with the client ID. |
|
Client Secret |
The client credentials that are obtained from the identity service provider used with the client secret. |
|
SSL Certificate |
The certificate used for secure connection. |
|
Job Submission Interface |
Determines the Web Service call version to use for sending job reports. The default value is Version 1. |
|
Report Sending Mode |
Determines how the application sends reports. Possible values
The default value is Send Immediately. |
|
Send by Batch: Maximum Records for Every Batch |
Determines the number of tracked records the application collects before sending the reports by batch. The default value is , but the supported range of value is from to . |
|
Maximum Wait Time to Form a Batch (in Minutes) |
The length of time before the application sends the report by batch. The default value is , but the supported range of value is from to . Note: Specifying disables this setting.
|
|
Send By Batch: Resend Delay (in seconds) |
The length of time before the application sends the report by batch. The default values are . |
|
Send By Schedule: Maximum Records for Every Batch |
Determines the number of tracked records the application collects before sending the reports by schedule. The default value is , but the supported range of value is from to . |
|
Send by Schedule: Resend Delay (in Seconds) |
The length of time before the application sends the report by schedule. The default values are . |
|
Report Sending Interval |
The interval for sending tracked jobs by batch. Possible values
The default value is Minutes. |
|
Minutes |
Determines when to send reports in minutes. The default value is , but the supported range of value is from to . |
|
Daily |
Determines when to send reports within the day. Use the (HH:MM) time format. To add separate times, use commas. |
|
Day of the Week |
Determines when to send reports by selecting a day of the week. The default value is Sunday. |
|
Time of Day (in 24-hour format) |
Determines when to send reports during the selected day of the week. Use the (HH:MM) time format. To add separate times, use commas. |