User guide
Quick Start Guide
Case notes
Table component
FAQ
Search
Dashboard
Deleted Documents and Access Log
Solving a task
AI Assistant
Manuals
Substitution and Vacation
Suspending, resuming, archiving and deleting a case
Case variables, history and graph
Basic Terms
Uploading Documents, Folders and Revisions
News
Favorites
Navigating the interface
Dashboard widgets
Case Detail
News/Announcements in Team assistant
Case list
Logging In and Out
Account Settings
Task List
Mobile app settings
Reports and Charts
Searching and Listing Documents
Handing Over, Taking Over and Tasks to Pull
Bulk Tasks
Printing a Case
Creating and Editing an Overview
What Is TAS
Form Fields
Tablet Interface and NFC
Overviews
Creating a New Case
Case Events
Case Permissions
Subscribing to an overview by email
Administrator Guide
Platform guide
Administration
Crons
Parallel cron - PostponedTaskCron
Crons
CleanupCron
MsGraphCheckUnprocessedMailsCron - Checking Unprocessed Emails
Crons
Authentication and Synchronization
SMTP OAuth authentication
LDAP, SAML, Entra ID and NFC: Settings
Configuring authentication modules
Authentication
Organizační struktura
Vault
DMS attributes
Service Operations
Mobile App Setup for Your Environment
Scheme
XML Process Import
HR agenda and agenda handover
Logs
Archiving
Scripts
Sequences
System Status
News Management
Migrations
Configuration
Plugins
Email Queue
Service Console
AI monitoring
Shared Files
Settings
Email Processing
CSP Headers
CSV Files
Scheduled Tasks
Processing Queues
Maintenance
Administration Menu
Licenses
Dynamic Tables
Usage Statistics
Access Token Settings & Session Expiration
Visual Identity
Template
Prints
Tasks
Task calculations
Automatic task completion and cancellation
Email Task and Notifications
Task types
Smart Event task
Instructions, Sections and Testing a Task
General task settings and solver
Multi-instance
Planning: start, branching and due date
Dynamic conditions: builder
Variable assignment and sections
Variables
Class diagram, object state import and alias candidates
Document list
Text and Multiline text
Checkbox
Number
Variables: overview and common settings
Lists (texts, numbers, dates)
Dynamic Rows
Date
Dynamic list
Sequence
Dynamic Table
Shredding Process
Template graph
Template Tab
Template List
Importing, Exporting and Copying a Template
Template Headers
Case statuses
Roles
Self-hosted administration
Connecting to a different database
Diagnosing services
Hyper-V: Isolated NAT Network with Port Forwarding
Users
Translations
NFC Integration
Events and Rules
AXIOS API
Plans
Axios with Vault
Users
Axios with SSL Certificate
User Detail
Calculations & Functions
Form condition
Other dynamic conditions
Optimization of API calls on dynamic conditions
Filtering in a dynamic sheet using dynamic conditions
Dynamic Conditions: Script
Dynamic Rows: Script
Calculations
Dynamic Tables
Printing and File Generation
Documents in Calculations — Complete Guide
Printing and File Generation in Calculations
DOCX document creation
Other Calculations
How and when calculations run
Calculations API reference: the lib library
Calculations API reference: variables and case
Global Scripts and React Scripts
AI and Code Checking in Editors
Integrations
MS Graph
MS Graph - cron configuration
MS Graph v2 (from v5.7.102)
MS Graph - preparing the mailbox
MS Graph (email)
ISDOC.PDF
DocuSign
TAS call module - TAS 2 TAS (process creation via API)
DB View
DocuSign and electronic signatures
ERP and other integrations
Smart Events for Integrations
TAS Forms
TAS Forms
Activating the module on the environment
TAS Forms - secret creation guide for Docker Swarm
Advanced Features & Tips
Filtering in a dynamic sheet using a URL parameter (static)
Optimizing Overviews with a Large Number of Cases
AI Features
API Documentation
Product
Technical Changelog
Business Changelog
Version Upgrade Guide
Upgrade to v5.21
Upgrade to v5.19
Upgrade to TAS 5.19 - Key Changes and Removed Features
Upgrading TAS 5.17 to 5.19 – Technical Part (DevOps)
Upgrate to v5.17
Upgrade to TAS 5.17 - Key Changes and Removed Features
Asset Migration from FE to Backend (5.17 Upgrade) — DevOps
Upgrading to v5.7
Lodash upgrade v4.17.x (>v5.5)
Main changes and deprecated features (v5.3 > v5.7)
Highlighting variables in Read-only status (>v5.7.58)
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
Differences between TAS4 and TAS5 - a complete overview
Best Practices for Upgrading from v4 to v5
Using validation functions
Technical details
Server prerequisites
Security and Data Protection
Security
TAS Operations Runbook
Technological architecture
News / Important information
Microsoft Disabling Basic Auth for SMTP
End of EWS support and transition to Microsoft Graph
Adjustment in EWS after MS Exchange update (29.04.2025)
Security notices
Getting Started
- All Categories /
- Product
- Version Upgrade Guide
- Upgrate to v5.17 /
- Asset Migration from FE to Backend (5.17 Upgrade) — DevOps
Asset Migration from FE to Backend (5.17 Upgrade) — DevOps
This guide describes how to migrate assets from the old layout used in TAS 5.7 to the new backend layout introduced in version 5.17. The procedure also applies to newer versions that use the same backend asset structure — this change has historically been communicated under the 5.17 label.
Prerequisites
- The backend in version 5.7 is stopped — during the migration the source directory is only read, but any writes must be prevented.
- A backup of the original
frontend/assetsfolder exists (disk snapshot, tarball, storage snapshot — depending on the practices of the environment). rsync(recommended) or alternativelycpis available on the server.- You have access to a user with write permissions to
backend/assets(typicallydkr-tasor root).
Target structure
In version 5.7, files were stored in the frontend storage. Since version 5.17, the backend storage is used with the following structure (paths inside the container):
/app/tas/storage/assets/manuals
/app/tas/storage/assets/logos
/app/tas/storage/assets/visual-identity
/app/tas/storage/assets/images
/app/tas/storage/assets/documents
/app/tas/storage/assets/ai-content
Mapping of old and new folders
|
Old location (5.7) |
New location (5.17+) |
Note |
|
|
|
Move the contents of |
|
|
|
Move the entire contents, including any subfolders (e.g. |
|
|
|
Does not belong in |
|
|
|
Move the entire contents. |
|
did not exist |
|
Create as an empty folder. |
|
did not exist |
|
Create as an empty folder. |
_schemaLogos_ folder to manuals. It belongs exclusively in visual-identity. If it ends up in both locations, the content will be duplicated.documents is populated individually based on the customer's decision. For a standard migration, create it as an empty folder. ai-content did not exist in version 5.7 — always create it as an empty folder.Example paths
This guide assumes the common stack layout:
/srv/tas/stack/stack_name/deployment/instance/stack_name/storage/frontend/assets
/srv/tas/stack/stack_name/deployment/instance/stack_name/storage/backend/assets
Replace stack_name with the actual name of the stack in your environment.
Migration procedure (rsync)
The recommended variant using rsync — it preserves the structure better and makes it easy to exclude _schemaLogos_ from uploads.
1. Prepare the target structure
cd /srv/tas/stack/stack_name/deployment/instance/stack_name/storage/backend/assets
mkdir -p manuals
mkdir -p logos
mkdir -p visual-identity
mkdir -p images
mkdir -p documents
mkdir -p ai-content
2. Transfer the content from the frontend storage
Run the commands from the directory:
/srv/tas/stack/stack_name/deployment/instance/stack_name/storage/backend/assets
rsync -a --exclude '_schemaLogos_/' ../../frontend/assets/uploads/ ./manuals/
rsync -a ../../frontend/assets/logos/ ./logos/
rsync -a ../../frontend/assets/uploads/_schemaLogos_/ ./visual-identity/
rsync -a ../../frontend/assets/images/ ./images/
mkdir -p ./documents
mkdir -p ./ai-content
Variant without rsync (cp)
If rsync is not available on the server, you can use cp -a. This variant requires explicitly removing _schemaLogos_ from manuals so that the same content does not end up in two places.
cd /srv/tas/stack/stack_name/deployment/instance/stack_name/storage/backend/assets
mkdir -p manuals logos visual-identity images documents ai-content
cp -a ../../frontend/assets/uploads/. ./manuals/
rm -rf ./manuals/_schemaLogos_
cp -a ../../frontend/assets/logos/. ./logos/
cp -a ../../frontend/assets/uploads/_schemaLogos_/. ./visual-identity/
cp -a ../../frontend/assets/images/. ./images/
../../frontend/assets/uploads/. (with a dot at the end) copies the contents of the folder, including hidden files, rather than the folder itself.Post-migration check
Once finished, verify that the target folders exist and that their contents match the expected mapping:
cd /srv/tas/stack/stack_name/deployment/instance/stack_name/storage/backend/assets
find manuals -maxdepth 2 -type d | head
find logos -maxdepth 2 -type d | head
find visual-identity -maxdepth 2 -type d | head
find images -maxdepth 2 -type d | head
ls -la documents
ls -la ai-content
Focus mainly on the following:
manualsdoes not contain_schemaLogos_.visual-identitycontains the original contents of_schemaLogos_.logoscontains the original logos and any subfolders (e.g._org_).imagescontains the old files fromfrontend/assets/images.documentsexists and is empty, unless the customer specified otherwise.ai-contentexists and is empty.
Permissions
Finally, set the owner of the target folders and their contents. In the TAS environment, the required user is typically dkr-tas:
chown -R dkr-tas:dkr-tas /srv/tas/stack/stack_name/deployment/instance/stack_name/storage/backend/assets
chown -R dkr-tas ...) if ownership on the server is managed without an explicit group.Mapping summary
manuals <- uploads without _schemaLogos_
logos <- logos
visual-identity <- _schemaLogos_
images <- images
documents <- new empty folder
ai-content <- new empty folder
Next steps
After a successful migration and setting the permissions, start the backend image in version 5.17+ and verify that the assets load correctly (manuals, logos, visual identity, images in cases).
Updated
by Frantisek Brych