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

3.7 Alias Set


An Alias Set, as the name suggests is a list of Aliases. Now what exactly is an Alias? An Alias in plain terms should be considered to be a placeholder for value. An Alias resolves to a particular value called the Alias value. Alias sets are stored as dm_alias_set objects in Docbase.

Let us take an example here, in order to clear up all confusions.

An organization's workflow needs to go through a sequence of reviewers before it can be finally approved and published over to the website. A content author creates the content and needs to send it to his or her content manager for review. After the initial review, it needs to be finally approved by an approver.

Now, for each individual content author, his or her manager and approver would be different. Should a separate workflow be created individually for each content author? Or should it be hard-coded with the actual names of all the content authors in the organization and their content managers and approvers? What would happen...

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