Trados Studio
Trados Enterprise
Trados Team
Trados GroupShare
Trados Business Manager
Passolo
MultiTerm
RWS AppStore
Connectors
Beta Groups
Managed Translation
MultiTrans
TMS
WorldServer
Language Weaver
Language Weaver Connectors
Language Weaver Edge
Tridion Docs
Tridion Sites
LiveContent S1000D
XPP
Language Developers
Tridion Docs Developers
Community Help
RWS User Experience
Internal Trados Ideas Community
Mercury
RWS Community Internal Group
RWS Training & Certification
Style Guides
RWS Campus
RWS Enterprise Technology Partners
Trados Approved Trainers
ETUG (European Trados User Group) Public Information
Nordic Tridion Docs User Group
Tridion West Coast User Group
Trados Studio Ideas
Trados GroupShare Ideas
Trados Team Ideas
Trados Team Terminology Ideas
Trados Enterprise Ideas
Trados Business Manager Ideas
MultiTerm Ideas
Passolo Ideas
RWS Appstore Ideas
Tridion Docs Ideas
Tridion Sites Ideas
Language Weaver Ideas
Language Weaver Edge Ideas
Managed Translation - Enterprise Ideas
TMS Ideas
WorldServer Ideas
LiveContent S1000D Ideas
Contenta S1000D
XPP Ideas
Events & Webinars
To RWS Support
Detecting language please wait for.......
It is possible for users to be notified through Studio of an updated plugin that is made available on the SDL Appstore. In order for this to work effectively it is important that all developers who list their plugins on the Store follow a particular convention. The reason for needing an agreed convention is that there is a strong connection between the pluginpackage.manifest information and the plugin plugin record from the Store. In order to have a better user experience (read: for this to work!) on the AppStore website we have put in place some conventions, which will be described bellow.
Is important that the Description from the manifest file is meaningful. This will be seen in the plugin manager and will be used as we continue to develop the integration of the AppStore into Studio.
The plugin name from the manifest file should match the name of the plugin from the AppStore. Aside from the obvious inconsistency the notifications will not work if this doesn't match.
Pluginpackage.manifest.xml
AppStore web site
This change will also make it easier for users to identify the app names in the plugin manager which is important when it comes to knowing which apps to remove.
Because there are multiple versions of Studio available, the plugin version must be different for each Version of Studio otherwise we cannot determine which one to use. This applies to the version numbering before the Studio version in brackets which is simply text added when you submit the plugin to the AppStore. So in the AppStore the user sees something like this when downloading their apps.
The Studio version name in brackets helps the user to identify the version they want when downloading from the AppStore manually. The plugin manifest should only contain the semantic versioning convention described below.:
No extra special characters should be added in the App Record. The version number itself should follow a semantic versioning specification as described below:
This means the following would be unnacceptable for example:
1.02.4.1
They should be:
1.0.0.02.4.1.0
This may not be the convention used by everyone but in order to ensure the best possible experience for users this is the convention to be followed. It will mean that users will be notified correctly when there is an update available to a plugin that is currently being used in Studio, for example: