Best Practices for Upgrading from TAS 4 to TAS 5

Upgrading from TAS 4 to TAS 5 is a complex process that requires careful preparation, client communication, and technical adjustments. Below are key best practices to ensure a smooth migration.

Effort and Preparation

Thorough preparation is essential – Active communication with the client is necessary, and new forms and designs should be introduced early to align expectations.

Multiple rounds of testing – At least four testing cycles are recommended to ensure a seamless migration.

Client involvement – The client must clearly define what needs to be displayed and what adjustments are critical for their workflow.

Actual effort may exceed estimates – Initial effort estimates often do not reflect the actual scope of work. It is important to anticipate that the real workload may be significantly higher than the original estimate (e.g., 20 MD planned, 60 MD actually required).

Key Areas Requiring Significant Adjustments

Form Variables

• Variable assignments must be restructured into well-defined sections due to new design constraints.
• The TAS 5 layout requires structured adjustments, and simply reusing the existing setup is not an option.

Case Overview (CO)

• If the new design is to be used, the entire CO must be rewritten using React components. The original HTML version remains backward compatible and can be retained.
• It is necessary to reconsider how data is structured and displayed.

Dynamic Conditions and WatchVars

• WatchVars usage is mandatory – In TAS 5, dynamic conditions are evaluated differently due to loading speed optimizations.
• What previously worked efficiently without WatchVars in TAS 4 now requires explicit WatchVars to avoid performance issues.

Example: Repeated evaluations of varReadOn can significantly slow down the system.

Dynamic Rows

• Behavior review and optimization are essential, especially for runCondOnChange.
• Scrollbar implementation – With larger data volumes, it is necessary to ensure smooth navigation.

Key Adjustments

Global Scripts

• Be cautious with duplicate global scripts (e.g., the commafy function may appear multiple times).
• TAS 5 combines React scripts with traditional scripts, which can lead to unexpected conflicts.

Language Mutations

• Language support should be verified – some languages may not be fully available in new React scripts, and missing languages may need to be added through consulting efforts.

Previously Hidden Issues

• Users tend to pay more attention to the system after an upgrade, which can reveal long-standing hidden issues.
• TAS 5 is more strict – Some elements that worked in TAS 4 may not pass validation in the new version.

Improvements and Recommendations

Design Consistency

• The new CO design is well received, but it is crucial to ensure that its visual appearance is consistent with task views.
• Clients frequently request that task layouts match CO.

Client Engagement

• Clients will not identify all issues on their own – they must be actively guided in defining their requirements.
• CO looks best with four columns.

Approach to Redesign

• Replicating the TAS 4 design is not possible – Accepting changes and adapting to the new concept is necessary.
• Early client involvement helps align expectations.
• It is recommended that a consultant first prepares a concept and then reviews it with the client.

Client Expectations

• Clients may assume that the upgrade will happen automatically without their input.
• They need to be informed that they must actively participate in configuring the new setup.

Managing Perception of Issues

• Communicating changes effectively is crucial – issues that would have occurred in TAS 4 should not be mistakenly attributed to the upgrade.
• Certain problems, such as organizational structure changes, may be incorrectly linked to the transition to TAS 5.
• Managing client expectations is essential to avoid misunderstandings. Clients often do not fully understand what to expect from the upgrade.

Final Recommendations

✅ Thorough preparation and communication are key to a successful migration.

✅ Following the technical documentation for the upgrade helps prevent issues.

✅ Redesign should be anticipated, especially for variables, CO, and dynamic conditions.

✅ Clients must be informed from the beginning about the changes and their impact.

By following these recommendations, it is possible to minimize issues, optimize performance, and ensure a smooth transition to TAS 5.