Tag Creation Job

The Tag Creation Job tracks batches of generated labels. It provides an interface to start a batch tag generation job, tracking progress & assets tagged. It also adds resilience, error-handling, and logging of job progress.

Tag Creation Job

• Template: The Label Template you wish to use for this job

• Data Source: The Data Source to use for this job.

• State: State of the job.

• Percent complete: Progress of the job

• Activities: Logging of job progress, errors, etc

Managing a Job

You can manage & track the stages of a Tag Creation Job from the form or list-view.

1. Creating a new job

   1. Choose the appropriate Template & Data Source for your job

   2. Click the Generate Tags (Background) button in the form header

   3. The job will change to a state of 'Starting' while it is kicked off. Once label creation has begun, the state will change to 'Processing' and the 'Percent complete' field will begin to update.

2. Monitoring a job

   1. During label creation, the 'Activity log' will show progress, errors, etc. In addition, the 'Percent complete' field will update. The Tagged Records related list will begin to populate as those tags are created.

3. Completing a job

   1. Upon completion, a PDF attachment will be added to the Tag Creation Job with the printable labels.

4. Cancelling a job

   1. At any time from the form or list view, you can choose to Cancel Job. This will, at the next available opportunity, stop processing the job.

5. Restarting a job

   1. From the form view, you can click the button to Reset Job to New. This will delete any Tagged Records, attachments, and child jobs, preparing the job the begin again.

   2. Clicking the Generate Tags (Background) button will start the job anew with the selected Template & Data Source.

Job Splitting & Error States

The resource requirements of a Tag Creation Job can vary widely according to:

1. The size of the Data Source

2. The complexity of the Label Template - Barcodes and, especially, QR Codes may require significant instance memory

The Tag Creation Job will attempt to manage sizing & errors during tag creation automatically. In the event of errors such as 'insufficient memory' or 'string too large', the Tag Creation Job will automatically split itself into 2, 4, 8, or more parts. In that case, the following will apply:

• The parent job will change to a state of 'Split Into Chunks'

• Child jobs will be visible in a related list on the parent job form

• The appropriate Tagged Records will appear in the related list on each child job

• The appropriate PDF attachment will appear on each child job

When split, each child job will proceed serially, and both the child & parent job 'Percent complete' fields will update appropriately.

Split Job Parent & Children Processing

System properties are available to adjust the parameters under which splitting may occur:

• x_yala_tagger.enable_job_chunks - Whether or not job splitting is allowed. If not allowed, then the Tag Creation Job will fail if it overruns system resources.

• x_yala_tagger.max_job_chunks - Maximum number of chunks (child jobs) allowed before the parent job will fail. If the number of child jobs grows too great, we recommend making your Data Source more specific so that the total records contained is more manageable.

• x_yala_pdf.maximum_html_chars - Maximum size of the HTML string for merged label template before the job automatically splits. The sizing of the instance determines how large this can scale. The default is sized for smaller instances. Barcode & QR code content is the primary cause of large string size.