- Install, Upgrade, and Maintenance
- Targetprocess System Requirements
- FAQs about migration from IBM to AWS
- How to switch from Targetprocess On-Site to Targetprocess On-Demand
- How to move Targetprocess from one server to another
- Error after migrating the database from SQL Server 2005 to a newer version
- Share View with external users in On-Premise environment
In 3.7.7, we've made some changes to our mashups.
First, we've changed the directory structure for mashups. If you added your mashups using the Mashup Manager inside TP, you shouldn‘t notice any differences. However, if some mashups had been put directly to the JavascriptMashups
folder, the administrator will have to manually move all such mashups to the JavascriptMashupsCommon folder. If you have some mashups that explicitly use relative paths to other files (../../some-icons.svg), you may have to update these paths.
Second, we’ve deprecated require function, that means some of your mashups have to be updated.
For the custom mashups you created you should use addDependency instead: e.g., if you had something like require(['jQuery', 'Underscore'], callbackFunction), you can change it to tau.mashups.addDependency('jQuery').addDependency('Underscore').addMashup(function($, _)) { ... }
If you face any issues with mashups that you installed from our Mashup Library, you should just update them to their latest version.
- Click "Check for updates" at the right side of Mashups library
- Delete the mashup
- Install the mashup from the library
You may want to pay attention to the following mashups if you are using them: Board Fullscreen Mode, Nested Boards, Recent Activity, CF Constraints, Quick Add Several Work Items
If your server is not connected to internet, see /guide/installation/mashup-manager-no-internet
Still have a question?
We're here to help! Just contact our friendly support team