AWI IPCE Data Transmission and GDPR Relevance - Automic Automation.

Products

• CA Automic Workload Automation - Automation Engine
• Automic Automation
• Automic SaaS

Issue/Introduction

This article clarifies the data transmission behavior of the Automic Web Interface (AWI) regarding the IPCE (In-Product Content Experience) components in version 24.4 and above.

It provides a data catalogue for telemetry and analytics to address GDPR compliance inquiries.

Symptoms 

End-user browsers send requests to *.ipce.broadcom.com (e.g., ipce.min.js). Organizations with closed networks or strict GDPR requirements need to understand what data is transmitted and if PII is stored.

Environment

• Automic Automation 24.4.x
• Automic Automation 26.0.x
• Automic Web Interface (AWI)

Cause

How-To.

Resolution

The behavior of the IPCE component is controlled by three primary properties in awi.ipce.properties:

• ipce.enabled:
  • Value: true: Enables the help panel and documentation bot.
  • Value: false: Disables all IPCE-related features; no telemetry or analytics calls are made.
• ipce.telemetry.enabled:
  • Value: true: Sends product usage and license metrics. This is functionally equivalent to the standard Automation Engine (AE) Telemetry but is initiated via the browser.
  • Data Collected: Licensed metrics, version information, and basic usage counts.
• ipce.analytics.enabled:
  • Value: true: Sends anonymized UI context data to provide relevant help content based on where the user is in the AWI.
  • Data Collected: UI location (Perspectives), menu actions, and interface context.

GDPR and PII Considerations:

1. PII Collection: No Personally Identifiable Information (PII) such as user names, cookies, or sensitive business data is included in the application payload.
2. IP Addresses and User Agents: While standard HTTP request metadata (IP address/User Agent) is processed transiently by the routing infrastructure (e.g., Akamai/Broadcom edge nodes) to deliver the content, this data is not stored, logged, or correlated with the telemetry/analytics payload.
3. Data Masking: All collected metrics are anonymized. Sensitive strings are masked using #### if they appear in any context-sharing logs.

For version 24.4 users, the telemetry details documented for version 26.0 remain applicable.

Additional Information

• Automic Automation Telemetry Documentation
• For further inquiries regarding data privacy, see Contact Broadcom Support.