Attribute tuning best practices for web applications

Click this icon on the toolbar to view and download the full PDF version of this guide.

This attribute tuning best practice guide is aimed at arming SS&C | Blue Prism® developers and testers with the skills to fix compatibility issues brought on by migration to modern Chromium browsers. It also serves as a standards guide for developers who are interested in what to avoid when developing new Blue Prism automations.

Best practice guides

Best practice guides are recommended standards that define specific functions, installation configurations, technical capabilities, and APIs, or other controlling standards. They reflect the collective knowledge gained by senior Blue Prism developers and architects over years of developing and implementing scalable, robust, resilient automations.

The purpose of best practice guides is to remove ambiguity by saying, "this is the standard recommendation for coding or configuring a Blue Prism process, action, or capability for best outcome". They should be viewed as a supplement to current documentation, not a replacement.

Best practices are not tied to a specific Blue Prism version or product extension (for example, browser plug-in).

Prerequisites

Best practice guides assume readers have mastered Blue Prism development and implementation to an advanced level.

For more information on Blue Prism fundamentals, please consult the following Blue Prism University courses:

  • Blue Prism Foundation
  • Blue Prism Advanced Consolidation Exercise (ACE)
  • Attribute Matching Guide
  • Blue Prism – Solution Design Overview
  • Object Design Guide
  • Browser Automation Guide

Assertions

Implementing successful attribute tuning is based on the following assumptions:

  • A web browser of some kind is being used.
  • Application Modeller is used to discover and define the element attributes used.