Working with Content Models | Alfresco Developer Guide

Sign In Start Free Trial

Book Overview & Buying
Table Of Contents
Feedback & Rating

Alfresco Developer Guide

4 (7)

Alfresco Developer Guide

4 (7)

Overview of this book

Alfresco Developer Guide

Alfresco Developer Guide

Credits

Credits

About the Author

About the Author

About the Reviewers

About the Reviewers

Preface

Preface

Free Chapter

The Alfresco Platform

The Alfresco Platform

Alfresco in the Real World

Example Used throughout This Book

Alfresco Architecture

Customizing Alfresco

Dusting Off Your Toolbox

Understanding Alfresco's Editions

Summary

Getting Started with Alfresco

Getting Started with Alfresco

Obtaining the SDK

Setting up the SDK in Eclipse

Extending Alfresco

Packaging and Deploying Customizations

Troubleshooting

Starting Over

Summary

Working with Content Models

Working with Content Models

Defining SomeCo's Content Model

Step-by-Step: Relating Types with Associations

Step-by-Step: Adding Aspects to the Content Model

Step-by-Step: Finishing up the Model

Modeling Summary

Modeling Best Practices

Configuring the UI

Working with Content Programmatically

Summary

Handling Content Automatically with Actions, Behaviors, Transformers, and Extractors

Handling Content Automatically with Actions, Behaviors, Transformers, and Extractors

Encapsulating Content Operations in Actions

Binding Logic to Custom Types with Behaviors

Extracting Metadata from Files

Transforming Content from One Format to Another

Summary

Customizing the Web Client User Interface

Customizing the Web Client User Interface

Knowing When to Customize Alfresco's Web Client and When to Write Your Own

Adding New Menu Items with UI Actions

Writing Action Evaluators to Show/Hide UI Actions

Changing How the Web Client Renders Data with Custom Component Renderers

Creating Custom Dialogs

Creating Custom Wizards

Customizing Web Client JSP Pages

Summary

Exposing Content through a RESTful API with Web Scripts

Exposing Content through a RESTful API with Web Scripts

Introducing the Web Script Framework

Planning the SomeCo Whitepapers and Ratings API

Retrieving Data with Web Scripts

Writing Java-Backed Web Scripts

Wiring a Web Script to UI Widgets

Handling Form Data

Customizing the Web Client with Web Scripts

Advanced Web Scripts

Summary

Advanced Workflow

Advanced Workflow

What is a Workflow?

Creating Process Definitions

Using the jBPM Graphical Process Designer

Wiring a Process to the Alfresco UI

Assigning Tasks to Users and Groups

Adding Logic to Workflows with Actions and Process Variables

Using the Workflow API

Using Timers

Debugging Workflows

Comparing Alfresco Workflow Options

Summary

Web Content Management

Web Content Management

Understanding the Difference between Alfresco DM and Alfresco WCM

Obtaining Alfresco WCM

Creating Web Projects

Creating Web Forms

Deploying Content

Performing Post-Deployment Processing

Modifying and Creating WCM Workflows

Working with the AVM API

Using the AVM Console

Summary

Security

Security

Authenticating and Synchronizing with LDAP

Setting Up Single Sign-On (SSO)

Working with Security Services

Summary

API Reference and Examples

API Reference and Examples

Foundation API Public Services

Lucene Queries

JavaScript

API Examples

Alfresco Configuration Reference

Alfresco Configuration Reference

Actions

Web Client Config Elements

Action Groups

Metadata Extractors

Transformers

Graphical View of the Alfresco Content Model

Index

Index

Customer Reviews

4 (7)

5 star

71.4%

4 star

0

3 star

0

2 star

14.3%

1 star

14.3%

Step-by-Step: Finishing up the Model

Let's finish up the model by doing two things: First, the remaining departments need content types added to them. Second, there is an out of the box aspect that needs to be applied to all the content. It's called generalclassifiable. It allows content to be categorized. SomeCo wants all of its content to be classifiable as soon as it hits the repository. To make that happen, you need to define the aspect as mandatory. Because SomeCo wants it across the board, you can do it on the root type sc:doc, and have it trickle down to all of SomeCo's types.

To add the remaining departmental content types as well as make the generalclassifiable aspect mandatory, follow these steps:

Edit the scModel.xml file.

Add the the following types:

    <type name="sc:hrDoc">
     <title>Someco HR Document</title>
     <parent>sc:doc</parent>
    </type>

    <type name="sc:salesDoc">
     <title>Someco Sales Document</title&gt...

Search

Your notes and bookmarks