Limitations
Following are some limitations you might encounter using the PTC Server connection:
• After upgrading either Arbortext Editor or your PTC Server, delete the cache directory defined in the WindchillAdapterHomeDir parameter of the userprefs.xml configuration file. Be sure to check in or upload any unsaved documents to the PTC Server before deleting the cache directory.
If you do not delete your cache directory before upgrading, the PTC Server connection displays the following warning the next time you try to connect to the PTC Server:
You last used the PTC Server Connection with an older version
of Arbortext Editor. Therefore, your cache will need to be cleared,
which will result in the loss of any unsaved documents. Do you
wish to clear your cache in order to connect to the PTC Server Connection?
Select OK to clear your cache and proceed with the connection. If any of your documents have not been checked in or uploaded to the PTC Server and you want to save the changes made to those documents, select Cancel. In this case, you will need to connect with an earlier version of Arbortext Editor and check in or upload your changes before using the upgraded version of Arbortext Editor to connect.
• If you change the system locale on either Arbortext Editor or your PTC Server, delete the cache directory defined in the WindchillAdapterHomeDir parameter of the userprefs.xml configuration file. Be sure to check in or upload any unsaved documents to the PTC Server before deleting the cache directory.
• The twowaymetadatarule tag in the document-type-specific burst configuration file only supports PTC Server global attributes and system attributes. A global attribute used in any metadata rule must have the same name as the reusable attribute it is related to.
• Any subtypes created under the wt.epm.EPMDocument parent class must have a non-null value in the Internal Name field. If this field has a null value, Arbortext Editor cannot connect to the PTC Server.
• Certain types of errors, especially during document bursting, might leave incomplete documents in the user workspace. You should remove those documents by cleaning the workspace.
• New objects in the user workspace that have not added to the PTC Server cannot be reliably handled by PTC Server connection operations. For example, when object reuse is enabled referencing a new object from a different workspace causes subsequent document bursting operation to fail.
• When a bursting error occurs during a > or > operation, the document open in Arbortext Editor is no longer valid. You cannot edit the document to correct any mistakes and attempt the bursting operation again. In this case, you must close the document and reopen it. If you have made significant edits to a document, you should consider doing a > operation to save a copy of the modified document to the file system before attempting the burst operation.
• Bursting of documents imported through the PTC Server HTML interface is not supported.
• In order for graphics to be referenced by XML document objects, they must be imported through the PTC Server connection or through the New Graphics Dynamic Document screen of the PTC Server HTML interface ( > > menu choice in the Workspaces user interface).
• Several characters are not allowed in object names and are replaced when the object is checked in to the PTC Server. The following characters are not allowed in object names:
◦ Left (‘) or right (’) single quotes and left (“) or right (”) double quotes are replaced with a regular quote (")
◦ An endash (–) or a emdash (—) is replaced with a regular dash (-)
◦ A ^ character is replaced with a space.
◦ Any character in the ASCII range between 128 and 159 is replaced with a space
• Performance is affected by the number of objects in a workspace.
• You can only check out the latest version of an object stored on a PTC Server.