Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Web Content Management with Documentum

You're reading from   Web Content Management with Documentum Setup, Design, Develop, and Deploy Documentum Applications

Arrow left icon
Product type Paperback
Published in Jun 2006
Publisher Packt
ISBN-13 9781904811091
Length 484 pages
Edition 1st Edition
Languages
Concepts
Arrow right icon
Toc

Table of Contents (33) Chapters Close

Web Content Management with Documentum
Credits
About the Author
Acknowledgements
1. Preface
1. Content and Documentum FREE CHAPTER 2. Documentum Essentials 3. Documentum Advanced Concepts 4. Web Content Management System 5. Setting Up the Documentum Suite 6. Creating Our First Docbase 7. Setting Up Publishing 8. Setting Up Documentum Application Builder 9. Setting Up Documentum Administrator and Web Publisher 10. Designing Documentum Applications 11. Designing and Creating Custom Object Types 12. Creating Lifecycles, Alias Sets, and Permission Sets 13. Working with Web Publisher Template Files 14. Creating Rules Files 15. Creating Presentation Files 16. Folder Mapping 17. Using Instruction Files 18. Automatic Property Extraction (APE) 19. Working with Workflows 20. Testing Custom Workflows 21. Publishing from Docbase Using SCS 22. Web Viewing Content Files 23. Using DFC 24. Configurations and Customizations Using WDK 25. Documentum Deployment 26. Using DQL and API Commands Frequently Asked Questions and Answers
New Features and Enhancements in Release 5.3

Chapter 18. Automatic Property Extraction (APE)

Automatic property extraction (or APE in short) is one of the most powerful and useful features provided by Documentum DFC. One of the most frequent business needs is to automatically set a document's attributes (properties) based on the values set by the content creator in the content template (XML file). Let us understand this through a very simple example.

Imagine a fictitious template that requires users to fill in an Article Title field in the XML template. The requirement is that the value entered by the content creator in this field should be automatically saved in the title attribute (property) of the document as well.

Let's say that the content creator provides the following value for Article Title: Major breakthrough in financial investments. The value is saved in the <ARTICLETITLE> XML element (for example) in the content file created by the user.

Through its Automatic Property Extraction feature (and if configured correctly...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime
Banner background image