User guide
Quick Start Guide
Dashboard
Overviews
Case detail (Caseoverview)
Case - event
Tasks
Case notes
Documents
User settings
Favorites
Table component
FAQ
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)
Using validation functions
Differences between TAS4 and TAS5 - a complete overview
Best Practices for Upgrading from v4 to v5
Technical details
News / Important information
Scripts
Scripts in the platform are designed for reuse across various templates. These scripts are written as JavaScript or React.js functions and can be utilized for calculations, dynamic conditions, and case overviews.
Usage
Scripts can be used in both front-end and back-end contexts:
- Front-end: Used for case details (case overview) or dynamic conditions in templates.
- Back-end: Used for calculations within templates.
Activation Requirement
Before a script can be used, it must be marked as "active." Without this designation, its functions will not be available for execution.
Function Priority
If a function name matches another function that is directly used in the application (as described above), the function defined in this section takes precedence over the one in the "Scripts" section.
Best Practices for Reusability
To avoid redundancy and improve maintainability, scripts should be written for reuse across the platform. For example:
- Fetching exchange rates: A single script can be written to retrieve exchange rates from any bank or external platform instead of duplicating similar scripts across different templates.
- Shared calculations: Frequently used calculations should be centralized in reusable scripts.
Administrator Permissions
The Application Administrator (with the $Administrator role) has the authority to define dynamic tables within the platform.
By following these guidelines, scripts can be efficiently managed and leveraged across the entire platform to ensure consistency and scalability.
Updated
by Anna Gernát