IMPORTANT MESSAGE: We are still experiencing some difficulties that will affect your ability work with the RWS AppStore. Our IT team is working to resolve this but for now you may not be able to download or upload apps through the RWS AppStore. We apologise for the inconvenience and will update the community when we have a resolution in place. In the meantime you can take advantage of the Private AppStore if you are using Trados Studio 2021 or 2022.
Under Community Review

This is under community review to gather feedback and examples while seeing if there's more interest in this idea.

In terms of read-only fields, how would you or others imagine setting the permissions across the BluePrint for a given Schema?

And would such settings apply at an embedded schema level and/or at the individual field level?

Would there be a use case where an embedded Schema (or its fields) would need different read-only settings based on the Schema its used in?

Read-only fields per Group

Ability to apply security to a field, and read-only to a field for a group of editors.  This would allow us to make more content manageable in the GUI, and would help in translation scenarios where we want to give a translator access to the text content, but not the ability to change the taxonomy keywords for the item.

Also, in the case of products, only a product manager could change the SKU of an item, but nothing else in the Component.

  • In terms of read-only fields, how would you or others imagine setting the permissions across the BluePrint for a given Schema?
      I would imagine setting them in a similar way as edit permissions on a folder (read, write...).  A MVP (Minimally Viable Product) would allow it only on the parent level, just like the XMLName....

    And would such settings apply at an embedded schema level and/or at the individual field level?
      I would assume that the settings only apply to value-fields, such as text, date, component link, etc.  If the fieldtype is embedded, then the permissions would not apply....because we would not have the feature (yet) to apply permissions for a group (embedded set) of fields.... (again, thinking MVP...)

    Would there be a use case where an embedded Schema (or its fields) would need different read-only settings based on the Schema its used in?
      There might, but I would accept that the settings are field-based, no matter what parent it might be embedded inside...to keep things simple....and remember, we are going from not have any ability to apply read-only settings to fields....in the beginning I guess it would be used some, but going forward we could add fields into the Schema to be used only by developers...and then that would allow us to design our solutions better....for example, we could also have a 'css' field in a Component to inject local CSS...and that would have read-only rights except for developers....