This release affects all 5.3 releases from 5.3 F000 through 5.3 M210
Generally, we’ll post the list of SPRs and enhancements added to a product release. However, this release affects all 5.3 releases from 5.3 F000 through 5.3 M210. As a result, the release notes document is 208 pages. If you want details, we highly recommend you log in to the support site and read the release notes (login required).
Point releases are free to all customers on active maintenance.
This is the last scheduled maintenance release of 5.3.
Individual SPR Counts
M210 (4), M200 (6), M190 (6), M180 (10), M170 (7), M160 (21), M150 (9), M140 (33), M130 (35), M120 (17), M110 (38), M100 (24), M90 (24), M80 (23), M70 (42), M60 (33), M50 (65), M40 (59), M30 (53), M20 (23), M10 (281!), New features added to F000.
Continue reading “Arbortext 5.3 M220 released”
Security Update Patch (SUP3) Available for Arbortext Content Manager and Windchill products
PTC has addressed several newly identified security vulnerabilities for supported versions of Arbortext Content Manger (aka Windchill). These vulnerabilities affect all current maintenance releases of all Windchill Solution Products including:
- Arbortext PDMLink
- Windchill ProjectLink
- Arbortext Content Manager
Best practices say to always install security patches promptly. For details, please visit Windchill Security Update page to download the appropriate patch. Please contact PTC Technical Support with any questions.
You can push information from Arbortext Content Manager (aka Windchill) information into an Arbortext XML document and vice versa.
You can push and pull information into and out of Arbortext Documents and Arbortext Content Manager (aka Windchill) metadata.
- You can push Arbortext Content Manager metadata information into an Arbortext XML document.
- You can pull Arbortext Content Manager metadata information out of an Arbortext XML document.
This feature makes document metadata actionable in Arbortext Content Manager for workflow automation and other tools, such as the twitter integration we showed using the Arbortext DITA application and Arbortext Content Manager at Gilbane Boston 2010.
In this tip, we show you a simple way to enable the feature that allows you to push information from Arbortext Content Manager into an Arbortext document.
Our example uses Arbortext 5.3M040 and Arbortext Content Manager 9.0.
Let’s get started:
- Start Arbortext Editor
- Go to the Object Menu and select Connect
- Enter your Windchill Username and Password
- Pick your workspace (The library containing your Burst Specifications1)
- Use the Object Browser window to navigate to the Doctypename Burst Specification file that will designate which XML attribute will house the Windchill Version attribute.
- Check Out the Doctypename Burst Specification File
- Modify the Doctypename Burst Specification File:
The Modifications to the Doctypename Burst Specification1 File are as follows:
- Pick an element which contains a metadata attribute suitable for storage of the Windchill version attribute. In this case, we have checked out the Dita Bookmap Burst Specification and have identified the “rev” attribute on the bookmap element as the attribute which will hold the Windchill version information.
- Once the element/attribute combination within the Burst Specification File has been identified the next step is to add a twowaymetadatarule to the dmsmetadata section within the Burst Specification.
- Add “rev” as the attrname
- Add “bookmap” as bndryelemname
- Add “WC_VERSION_ATTR as metadata
- Add “bookmap” as metadataelemname
- Leave sourcetype set to “text”
- After making these attribute entries to the twowaymetadatarule, check the doctypename Burst Specification back into Windchill and open a new or existing bookmap file from Windchill or the FileàNew Menu.
- Once you have opened your file, proceed by moving your cursor to the “bookmap” element and hit CTRL-D to open the modify attributes window.
- Modify the “rev” attribute and add a character to the “rev” attribute. It does not matter what character you add as long as you put something into the field. If the attribute field remains blank, the Windchill version attribute will not populate the “rev” attribute. The application is designed to populate the field only if the user places a character in the field.
- Click “OK” and then File->Save as Server Object
- The next time you check out the file or publish the file, the “rev” attribute within the “bookmap” element will contain the current Windchill maintained version attribute.
Was this tip helpful?
Post to the comments or send an email to let us know.
1We’ll be talking more about the bursting spec in a future article. Stay tuned!