User guide
Quick Start Guide
Dashboard
Overviews
Case detail (Caseoverview)
Case - event
Tasks
Case notes
Documents
User settings
Favorites
Table component
FAQ
Mobile app settings
Administrator Guide
Platform guide
Administration
Crons
Authentication and Synchronization
Mobile App Setup for Your Environment
Scheme
Dynamic tables
Archiving
Scripts
Service console
Scheduled Tasks
HR Agenda
Sequences
CSP Headers
Logs
Access Token Settings & Session Expiration
Template
Roles
Planning
Users
Organizational structure
Events
Translations
AXIOS API
Calculations & Functions
Integrations
TAS Forms
TAS Forms
Activating the module on the environment
TAS Forms - secret creation guide for Docker Swarm
Advanced Features & Tips
Partners
Product
Business Changelog
Technical Changelog
Version Upgrade Guide
Upgrading to 5.9
Upgrading to 5.3
Dynamic conditions migration
PDF printing adjustment
Editing Task Description vs Task Instructions
Transpiling forEach to a for loop
Rendering HTML on Caseoverview
Upgrading to 5.7
Lodash upgrade v4.17.x (>v5.5)
Main changes and deprecated features (v5.3 > v5.7)
Highlighting variables in Read-only status
Using validation functions
Differences between TAS4 and TAS5 - a complete overview
Best Practices for Upgrading from v4 to v5
Technical details
News / Important information
- All Categories /
- Product
- Version Upgrade Guide
- Upgrading to 5.7 /
- Highlighting variables in Read-only status
Highlighting variables in Read-only status
To make the form clearer for users, variables in the Read-only state are now visually distinguished by highlighting .
- The background color matches the main color of the Team assistant (TAS) environment.
- 50% opacity is used, so the color remains subtle and does not interfere with work.
- Underlining is automatically applied to all variables with R (Read-only) permission
The purpose of this adjustment
Improve user orientation in forms - users can see at a glance which values they can edit and which are only for preview.
Example of use

The "Approved Amount" variable is set to Read-only after final approval. It is now lightly shaded in the form view to make it clear that it cannot be edited.
Special rule for scripts
If you are inserting scripts or dynamically generated content into a variable that should have its own background color , you must wrap it in a <div> element with the className "script" .
<div className="script"> {/* vlastní obsah nebo skript */} </div>This ensures that the background color remains visually consistent and does not overwhelm the appearance of the form.<div className="script"> {/* vlastní obsah nebo skript */} </div>
Updated
by Anna Gernát