Document Property Exchange |
|
Configuration in Agile e6 | |
Properties of Office files can be exchanged with the Office
Suite in Agile e6. The following figures show the corresponding configuration list in Agile e6, highlighting the properties for Subject ('SUBJECT') and Title ('TITLE') in a Word document: |
|
![]() |
|
Multi-lingual Properties? | |
As shown in the figure above, the property 'SUBJECT' is mapped
to a normal (single-language) attribute, while 'TITLE' is mapped to the
attribute 'T_DOC_DAT.DOC_NAME', which is a multi-lingual attribute. Mapping a property to a multi-lingual attribute is technically correct, but has a significant drawback: properties in Office files are single-language! This means that the property in the Office file will be updated with the content in the corresponding attribute in Agile e6 for the current language. |
|
Corresponding Scenario: 1. Creating an Office File (in English).
2. Updating the corresponding Document (in German).
|
|
Conclusion: As shown in this scenario the consequences are obvious: properties in
Office files, which are mapped to multi-lingual attributes, may be updated
with text in a different language. This can make the property unusable
for many employees in the organization.
If the Office Suite is configured in compliance with these recommendations,
and if the standard language for properties in Office files is, e.g. English
(or another language only containing Latin1 characters), then Office files
written in languages such as Japanese or Chinese can also be checked-in
and checked-out without a problem. |
|
Exchange of UTF-8 Properties |
|
Corresponding Scenario: 1. Creating an Office File (e.g. in Japanese).
2. Display Document in the Web Client or the Java Client. |
|
![]() |
The Web Client will interpret the UTF-8 syntax and display the Title attribute correctly. In these clients it is also possible to update the content or to search in the attribute. |
![]() |
Please remember that Subject ('T_DOC_DAT.SUBJECT') is a single-lingual attribute - as a consequence, the content of this attribute is lost! Remember that properties with non-Latin1 characters must be mapped to multi-lingual attributes in Agile e6. |