🚀 Pitstop Profile Problem Solvers 🚀

Previously, configuring variable sets in PDF Profiles required complex manual editing of XML files or switching between Simple and Advanced modes.
This update replaces those modes with a single, intuitive interface.

Administrators can now upload an existing .evs variable set or paste the variable-mapping JSON directly into the editor.
When you save, Infigo automatically validates the structure and generates the .evs file required by the PDF Profile.

This streamlines setup, reduces XML errors, and makes it much easier to manage variable mapping between products and PDF Profiles.

What’s included

• New Edit XML Source toggle for advanced users

• Support for uploading an .evs file directly

• Ability to paste JSON mapping data into the editor

• Automatic generation of a valid .evs file on save

• Built-in validation for uploaded or pasted data

• Cleaner, single-page workflow for variable-set management

Key settings

• Edit XML Source:
  Enables direct editing or pasting of JSON/EVS content.

• Upload EVS File:
  Lets you import an existing variable-set file from your computer.

• JSON Mapping Area:
  Paste JSON directly; the system will convert and generate the .evs file automatically.

• Save & Validate:
  Runs internal checks to ensure the structure is valid before applying changes.

Use cases

• Simplify configuration: Non-technical admins can now set up variable sets without XML knowledge.

• Reuse templates: Upload existing .evs files from another profile or environment.

• Speed up development: Copy JSON directly from external tools or documentation to instantly generate .evs files.

• Reduce human error: Automatic validation ensures all variable data is properly formatted.

Step-by-step implementation

Step 1 – Open or create a PDF Profile

1. Go to Admin → PDF Profiles.

2. Select an existing profile or click Add new.

Step 2 – Access the variable-set section

1. Scroll to the Variable Set / Job Ticket area.

2. Locate the Edit XML Source toggle.

3. Switch the toggle on if you want to view or paste mapping data manually.

Step 3 – Choose your preferred input method

Option 1 – Upload a file:

1. Click Upload EVS File.

2. Select an existing .evs file from your local drive.

3. The system validates and loads it automatically.

Option 2 – Paste JSON data:

1. In the source editor, paste your JSON variable mapping.

2. Click Save — Infigo will validate the content and automatically generate the corresponding .evs file.

Step 4 – Save and validate

1. Click Save.

2. The system runs validation to confirm the structure and generate or update the .evs file.

3. Check for any validation or conversion messages at the top of the screen.

Step 5 – Test your profile

1. Assign the PDF Profile to a product.

2. Generate a test output file.

3. Confirm that all variable data maps correctly into the resulting PDF.

Tips & best practice

• Keep a backup of your original .evs files before editing.

• Use the Edit XML Source toggle sparingly — only when pasting or reviewing mapping data.

• Always test generated .evs outputs on a sample product before production use.

• When moving profiles between environments, export the .evs for consistency.

Previously, PitStop XML reports could only display English or Latin-based characters, meaning localized messages from pre-flight or profile checks were not always readable.

This enhancement introduces automatic translation support for PitStop XML output — including full Hebrew character support.
When enabled, the system translates the XML text content into the configured language so reports remain clear and usable for non-English operators and clients.

What’s included

• New XML Translation Support option added to PDF Profile Settings

• Ability to translate all XML report content, including non-Latin scripts (e.g., Hebrew)

• Automatic character-encoding handling to prevent corrupted text

• Integration with external translation services via API key

Key settings

• XML Translation Support
  Located in Admin → PDF Profiles → Profile Settings.
  Enables automatic translation for PitStop XML report text.

• API Key
  Required if you use an external translation service.
  Enter this in the same settings area to authorize translations.

• Language Selection
  Controlled by your storefront’s default language or configured per profile.

Use cases

• International production environments: Ensures operators in non-English markets can review PitStop errors and pre-flight messages in their native language.

• Client-facing reports: Present pre-flight feedback in the same language as the customer’s storefront.

• Localization testing: Validate that generated PitStop XML files retain full readability for right-to-left scripts such as Hebrew.

Step-by-step implementation

Step 1 – Access PDF Profile Settings

1. Go to Admin → PDF Profiles.

2. Select the profile you want to modify and click Edit.

3. Locate the Profile Settings section.

Step 2 – Enable XML translation

1. Find the XML Translation Support toggle.

2. Enable the setting to activate translation for PitStop XML reports.

Step 3 – Enter your API key (if required)

1. If you are using an external translation service, locate the API Key field.

2. Enter the key provided by your translation service or administrator.

3. Save changes.

Step 4 – Verify translation

1. Generate a new PitStop XML report using the modified profile.

2. Open the report and confirm that all text, including Hebrew characters, appears translated and readable.

3. Validate that no encoding errors or missing symbols are present.

Step 5 – Test with multiple languages (optional)

• Switch your storefront’s language to another supported option (e.g. French, German, Hebrew).

• Run another test to confirm correct translation output for each language configuration.

Tips & best practice

• Always test new translations in a staging environment before enabling them in production.

• Keep your API key secure — avoid sharing or embedding it in scripts.

• Confirm that the PitStop profile name and XML encoding remain UTF-8 to preserve character integrity.

• When generating client-facing reports, ensure the storefront and PitStop report language align for consistency.