Edit

Version 10.2.7.3

Release date

June 14, 2023

Enterprise Edition v.10.2.7.3 requires a complete installation over the existing v.10.2.7.2. Refer to our Setup guide for detailed instructions.

New features

• Version 10.2.7.3 of Intelligent Automation Cloud Enterprise introduces integration with Pendo Analytics, a leading product digital adoption platform. Pendo is added into all components: Digital Workers, Control Tower, and WorkSpace, and runs both in on-premise and Cloud Product versions.

  This new integration is all about your user experience, and here’s how it will benefit you:

  • Simplified onboarding: Pendo guides help new users quickly understand the Product’s key features and functionalities, leading to a faster and more effective onboarding process.
  • Easy feedback sharing: share your thoughts and experiences easily using Pendo’s in-app feedback mechanism. This will allow us to better understand your needs, expectations, and experiences and help continuously improve our services.
  • Interactive help and support: provides instant access to interactive help content and tutorials.
  • Personalized user experience: Pendo’s insights allow us to personalize and improve your product experience by understanding how you use our Product, which features are the most valuable, and where we can improve.

  Pendo also follows industry-standard security practices and complies with all relevant privacy laws and regulations, such as GDPR and CCPA, so all your data and processes stay on the safe side.

• For integration purposes, several user roles were added to Keycloak (pendo.apiKey, pendo.account.id, pendo.visitor.id, pendo.visitor.wf_roles). The new roles are used in cookies and access tokens.

Bug fixes

• Fixed the issue with the HAProxy configuration for the BEP Agent machine with running REST API Connector. When the auto-scaling was enabled, and the node with the running connector-api service was stopped, the service restarted on an available agent. However, the configuration IP for the service still pointed to the old node. That affected the correct operation of REST API. Now the routing to a new connector node is switched correctly.