Book Image

The Oracle Universal Content Management Handbook

By : Dmitri Khanine
Book Image

The Oracle Universal Content Management Handbook

By: Dmitri Khanine

Overview of this book

Oracle UCM is a world-leading Enterprise Content Management platform. From Document Management, Web, Records, and more—Oracle has got all your business needs covered. Oracle UCM enables your organization to efficiently manage, store, preserve, and deliver content and documents. Written by Oracle ACE Dmitri Khanine, this book is a complete practical guide to building an ECM system and successfully configuring, administering, and operating it. It also shows you how to efficiently manage your organization's content and customize the UCM to fit your needs. This book wastes no time in getting you up and running and dives straight into the installation of the content server in Chapter 1. In the second chapter, you will master all the major controls and the admin interface. Metadata—a very important ingredient of any ECM—is thoroughly covered in Chapter 3. The book then moves on to the important tasks of securing your ECM system, configuring and managing workflows, and understanding and implementing virtual folders. The book also gives you an under-the-hood view of Stellent in Chapter 7. In the later chapters, you will learn how to migrate content like a pro and easily customize Oracle ECM. A bonus addition to the book is the final chapter, which is an easy-to-follow primer on web content management.
Table of Contents (21 chapters)
The Oracle Universal Content Management Handbook
Credits
Foreword
About the Author
About the Reviewer
Acknowledgement
Preface
Free Chapter
1
Getting Up and Running
Exploring Oracle UCM Product Offering
Index

Understanding the accounts component


Let's say, you only want accounting clerks to work with the current year's data and have read-only access to historic content. If you try to do this with role-based security the picture will get really ugly.

Now if you split your accounting into payable and receivable, it will get even messier. What are we going to do about it?

Role-based security that we just looked at is lock number one on the door. Sometimes you'd want a more detailed control than it can give you. We need more locks on that door!

If Debbie is in Accounts Receivable and tries to access any content in Accounting then our lock #1, the role-based security, will be open. But we need lock #2 to be closed when she accidentally tries to modify a historic record or a document in Accounts Payable.

Let's see how adding lock #2 helps us solve this problem.

How accounts are different

Accounts, our lock #2, are completely different from our lock #1—role-based security. As we've just seen, the role-based...