inteligr8/alfresco-ng2-components

Fork 0

mirror of https://github.com/Alfresco/alfresco-ng2-components.git synced 2025-05-12 17:04:57 +00:00

Eugenio Romano eec87c12d3 remove template old reference in documentation (#2421 )

2017-10-04 10:51:06 +01:00

41 KiB

Raw Blame History

Document List component

Displays the documents from a repository.

Basic Usage
- Properties
- Events
Details
Advanced usage and customization
See also

Basic Usage

<adf-document-list
    #documentList
    [currentFolderId]="'-my-'"
    [contextMenuActions]="true"
    [contentActions]="true">
</adf-document-list>

Properties

The properties currentFolderId, folderNode and node are the entry initialization properties of the document list. They cannot be used together, choose the one that suites more your use case.

Name	Type	Default	Description
selectionMode	string	'single'	Row selection mode. Can be none, `single` or `multiple`. For `multiple` mode you can use Cmd (macOS) or Ctrl (Win) modifier key to toggle selection for multiple rows.
selection	Array	[]	Contains selected nodes
rowStyle	string		The inline style to apply to every row, see NgStyle docs for more details and usage examples
rowStyleClass	string		The CSS class to apply to every row
currentFolderId	string	null	The ID of the folder node to display or a reserved string alias for special sources (see Data Sources)
folderNode	MinimalNodeEntryEntity	null	Currently displayed folder node
permissionsStyle	PermissionStyleModel[]	null	with this array you can define different styles depending on the permission of the user on that node. The PermissionStyleModel allows you to select also if you want to apply the style only on the file or folder nodes. PermissionStyleModel.permission accepts the following values Permissions see more.
paginationStrategy	PaginationStrategy	PaginationStrategy.Finite	The pagination type to be shown, can be Finite or Infinite
node	NodePaging	null	Document list will show all the nodes contained in the NodePaging entity
navigate	boolean	true	Toggles navigation to folder content or file preview
loading	boolean	false	Toggles the loading state and animated spinners for the component. Used in combination with `navigate=false` to perform custom navigation and loading state indication.
navigationMode	string (click,dblclick)	dblclick	User interaction for folder navigation or file preview
thumbnails	boolean	false	Show document thumbnails rather than icons
multiselect	boolean	false	Toggles multiselect mode
contentActions	boolean	false	Toggles content actions for each row
contentActionsPosition	string (left\|right)	right	Position of the content actions dropdown menu.
contextMenuActions	boolean	false	Toggles context menus for each row
enablePagination	boolean	true	Shows pagination
rowFilter	`RowFilter`		Custom row filter, see more.
imageResolver	`ImageResolver`		Custom image resolver, see more.
allowDropFiles	boolean	false	Toggle file drop support for rows (see ng2-alfresco-core/UploadDirective for more details)
sorting	string[]		Defines default sorting. The format is an array of 2 strings `[key, direction]` i.e. `['name', 'desc']` or `['name', 'asc']`. Set this value only if you want to override default sorting detected by the component based on columns.
locationFormat	string	'/'	The default route for all the location-based columns (if declared).
supportedPageSizes	number[]	[5, 10, 15, 20]	Supported page sizes for the pagination component. You can also use application configuration file to set it as a global setting using `document-list.supportedPageSizes` key.

Events

Name	Description
nodeClick	emitted when user clicks a list node
nodeDblClick	emitted when user double-clicks list node
folderChange	emitted once current display folder has changed
preview	emitted when user acts upon files with either single or double click (depends on `navigation-mode`), recommended for Viewer components integration
permissionError	emitted when user is attempting to create a folder via action menu without having the permission to do it
ready	emitted when the documentList is ready and loads all the elements

Details

DOM Events

Below are the DOM events the DocumentList component emits. All of them are bubbling, meaning you can handle them in any component up the parent hierarchy, even if DocumentList is wrapped by another component(s).

Name	Description
node-click	Raised when user clicks the node
node-dblclick	Raised when user double-clicks the node
node-select	Raised when user selects a node
node-unselect	Raised when user unselects a node

Every event is represented by a CustomEvent instance, having at least the following properties as part of the Event.detail property value:

{
    sender: DocumentListComponent,
    node: MinimalNodeEntity
}

Please refer to the DataTable documentation to find details about additional DOM events the DocumentList component bubbles up from the DataTable.

Below is a basic example of handling DOM events in the parent elements.

<div (node-click)="onNodeClicked($event)" 
(node-dblclick)="onNodeDblClicked($event)">
    <div>
        <adf-upload-drag-area ...>
             <adf-document-list ...>
                ...
             </adf-document-list>
        </adf-upload-drag-area>
    </div>
</div>

Pagination strategy

The Document List by default supports 2 type of pagination, the finite and the infinite pagination.

With the finite pagination you got a normal pagination ui with information about the result's count, pages, and stepper arrows. On every pagination event the results will replace the previous list.
With the infinite pagination there is only a "Load more" button at the end of your document list, and on every click (pagination event), the new results will be appended to the previous list.

Data Sources

For the Document List data sources you can use one of the following options:

Node ID

The unique identifier of the Node. Gets automatically updated when you perform navigation to other folders.

Repository aliases

You can use one of the well-known reserved aliases:

-root-
-shared-
-my-

DocumentList aliases

The DocumentList component also provides support for the following reserved aliases you can use:

-trashcan-,
-sharedlinks-
-sites-
-favorites-
-recent-

Note that due to specific origin of the data the sources above do not support navigation. You may want handling single and double clicks yourself to perform navigation to other sources.

DocumentList component supports default presets for all the custom sources mentioned earlier. If you don't provide any custom column definition utilizing "data-columns" component, then a default preset will be automatically used at runtime.

Some of the presets use the Location columns that allow you to navigate to the parent folder of the node, for instance navigating from the "Favorite" node to the folder containing it. There's a possibility to set the default location format using "locationFormat" property, to avoid re-defining entire columns layout.

The default column layout for non-reserved views is:

Icon
Name
Size
Modified (date)
Modified by

Trashcan

<adf-document-list
    currentFolderId="-trashcan-"
    locationFormat="/files">
</adf-document-list>

Default layout:

Icon
Name
Location
Size
Deleted
Deleted by

Shared Links

<adf-document-list
    currentFolderId="-sharedlinks-"
    locationFormat="/files">
</adf-document-list>

Default layout:

Icon
Name
Location
Size
Modified
Modified by
Shared by

Sites

<adf-document-list
    currentFolderId="-sites-">
</adf-document-list>

Default layout:

Icon
Title
Status

Favorites

<adf-document-list
    currentFolderId="-favorites-"
    locationFormat="/files">
</adf-document-list>

Default layout:

Icon
Name
Location
Size
Modified
Modified by

Recent Files

<adf-document-list
    currentFolderId="-recent-"
    locationFormat="/files">
</adf-document-list>

Default layout:

Icon
Name
Location

Setting default folder

You can set current folder path by assigning a value for currentFolderId property. It can be either one of the well-known locations as -root-, -shared- or -my- or a node ID (guid).

There may be scenarios when it is needed to set default path based on relative string value rather than node ID. For example when folder name or path is static but its underlying ID is not (i.e. created manually by admin). In this case you can use alfresco-js-api to get node details based on its relative path.

Let's try setting default folder to /Sites/swsdp/documentLibrary without knowing it's ID beforehand. For the sake of simplicity example below shows only main points you may need to pay attention to:

import { ChangeDetectorRef } from '@angular/core';
import { AlfrescoApiService } from 'ng2-alfresco-core';

export class FilesComponent implements OnInit {

    currentFolderId: string = '-my-';

    constructor(private apiService: AlfrescoApiService,
                private changeDetector: ChangeDetectorRef) {
        // ...
    }

    ngOnInit() {
        let nodes: any = this.apiService.getInstance().nodes;
        nodes.getNodeInfo('-root-', {
            includeSource: true,
            include: ['path', 'properties'],
            relativePath: '/Sites/swsdp/documentLibrary'
        })
        .then(node => {
            console.log(node);
            this.currentFolderId = node.id;
            this.changeDetector.detectChanges();
        });
    }
}

We've added console.log(node) for the getNodeInfo callback just for study and debug purposes. It helps examining other valuable information you can have access to if needed:

Important note: for this particular scenario you must also trigger changeDetector.detectChanges() as in the example above.

Custom icons for selected rows

You can use the "class" property of the DataColumn component to apply your custom css.

As an example, this feature can be used to change the look and feel of the icon for the selected rows.

Let's start by assigning an "image-table-cell" class to the thumbnail column:

<adf-document-list ...>
    <data-columns>
        
        <data-column
            key="$thumbnail"
            type="image"
            [sortable]="false"
            class="image-table-cell">
        </data-column>
        
        ...
    </data-columns>
</adf-document-list>

Now your application can define custom styles to change the content of the column based on some other conditions, like selection state:

adf-document-list >>> adf-datatable tr.is-selected .image-table-cell {
    position: relative;
}

adf-document-list >>> adf-datatable tr.is-selected .image-table-cell::before {
    content: "\E876"; /* "done" */
    font-family: "Material Icons";
    font-size: 24px;
    line-height: 32px;
    text-align: center;
    color: white;
    position: absolute;
    width: 32px;
    height: 32px;
    top: 50%;
    left: 50%;
    margin-top: -16px;
    margin-left: -14px;
    border-radius: 100%;
    background: #00bcd4;
}

Once your application starts you should see the following icon for each selected row:

Calling DocumentList api directly

Typically you will be binding DocumentList properties to your application/component class properties:

<adf-document-list 
    [currentFolderId]="myStartFolder">
</adf-document-list>

with the underlying class being implemented similar to the following one:

@Component(...)
export class MyAppComponent {

    myStartFolder: string = '-my-';
    
}

However there may be scenarios that require you direct access to DocumentList apis. You can get reference to the DocumentList instance by means of Angular Component Interaction API. See more details in Parent calls a ViewChild section of the official docs.

Here's an example of getting reference:

<adf-document-list 
    #documentList
    [currentFolderId]="myStartFolder">
</adf-document-list>

Note the #documentList ID we've just added to be able referencing this component later on.

import { ViewChild, AfterViewInit } from '@angular/core';
import { DocumentListComponent } from 'ng2-alfresco-documentlist';

@Component({...})
export class MyAppComponent implements AfterViewInit {

    myStartFolder: string = '-my-';
    
    @ViewChild(DocumentListComponent)
    documentList: DocumentListComponent;

    ngAfterViewInit() {
        console.log(this.documentList);
    }
}

Example above should produce the following browser console output:

Now you are able to access DocumentList properties or to call methods directly.

// print currently displayed folder node object to console
console.log(documentList.folderNode);

Important note:
It is important accessing child components at least at the AfterViewInit state. Any UI click (buttons, links, etc.) event handlers are absolutely fine. This cannot be ngOnInit event though. You can get more details in Component lifecycle hooks article.

Custom columns

It is possible to reorder, extend or completely redefine data columns displayed by the component. By default special $thumbnail and displayName columns are rendered.

A custom set of columns can look like the following:

<adf-document-list ...>
    <data-columns>
        <data-column key="$thumbnail" type="image"></data-column>
        <data-column
            title="Name" 
            key="name" 
            sortable="true"
            class="full-width ellipsis-cell">
        </data-column>
        <data-column
            title="Created By" 
            key="createdByUser.displayName"
            sortable="true"
            class="desktop-only">
        </data-column>
        <data-column
            title="Created On" 
            key="createdAt" 
            type="date" 
            format="medium"
            sortable="true"
            class="desktop-only">
        </data-column>
    </data-columns>
</adf-document-list>

You can also use HTML-based schema declaration used by DataTable, TaskList and other components:

<adf-datatable [data]="data" ...>
    <data-columns>
        <data-column type="image" key="icon" [sortable]="false"></data-column>
        <data-column key="id" title="Id"></data-column>
        <data-column key="createdOn" title="Created"></data-column>
        <data-column key="name" title="Name" class="full-width name-column"></data-column>
        <data-column key="createdBy.name" title="Created By"></data-column>
    </data-columns>
</adf-datatable>

You can also add tooltips, automatic column title translation and other features. See the DataColumn component page for more information about specifying and customizing columns.

Underlying node object

DocumentList component assigns an instance of MinimalNode type (alfresco-js-api) as a data context of each row.

export interface MinimalNode {
    id: string;
    parentId: string;
    name: string;
    nodeType: string;
    isFolder: boolean;
    isFile: boolean;
    modifiedAt: Date;
    modifiedByUser: UserInfo;
    createdAt: Date;
    createdByUser: UserInfo;
    content: ContentInfo;
    path: PathInfoEntity;
    properties: NodeProperties;
}

See more details in alfresco-js-api repository.

Binding to nested properties is also supported. You can define a column key as a property path similar to the following:

createdByUser.displayName

Here's a short example:

<adf-document-list ...>
    <data-columns>
        <data-column key="$thumbnail" type="image"></data-column>
        <data-column title="Name" key="name" class="full-width ellipsis-cell"></data-column>
        <data-column
            title="Created By" 
            key="createdByUser.displayName">
        </data-column>
    </data-columns>
</adf-document-list>

Date Column

For date column type the DatePipe formatting is used. For a full list of available format values please refer to DatePipe documentation.

ADF also supports additional timeAgo value for the format property. That triggers the date values to be rendered using popular "Time from now" format.

Location Column

This column is used to display a clickable location link pointing to the parent path of the node.

You are going to use it with custom navigation or when displaying content from the sources like:

Sites
Shared Links
Recent Files
Favorites
Trashcan

or any other location that needs nagivating to the node parent folder easily.

Note that the parent node is evaluated automatically, the generated link will be pointing to URL based on the format property value with the node id value appended:

/<format>/:id

For example:

<data-column
    key="path"
    type="location"
    format="/files"
    title="Location">
</data-column>

All links rendered in the column above will have an address mapped to /files:

/files/node-1-id
/files/node-2-id
...

Column Template

It is possible to provide custom column/cell template that may contain other Angular components or HTML elements:

Every cell in the DataTable component is bound to the dynamic data context containing the following properties:

Name	Type	Description
data	DataTableAdapter	Data adapter instance.
row	DataRow	Current data row instance.
col	DataColumn	Current data column instance.

You can use all three properties to gain full access to underlying data from within your custom templates. In order to wire HTML templates with the data context you will need defining a variable that is bound to $implicit like shown below:

<ng-template let-context="$implicit">
    <!-- template body -->
</ng-template>

The format of naming is let-VARIABLE_NAME="$implicit" where VARIABLE_NAME is the name of the variable you want to bind template data context to.

Getting a cell value from the underlying DataTableAdapter:

context.data.getValue(entry.row, entry.col);

You can retrieve all property values for underlying node, including nested properties (via property paths):

context.row.getValue('name')
context.row.getValue('createdByUser.displayName')

You may want using row api to get raw value access.

<data-column title="Name" key="name" sortable="true" class="full-width ellipsis-cell">
    <ng-template let-context="$implicit">
        <span>Hi! {{context.row.getValue('createdByUser.displayName')}}</span>
        <span>Hi! {{context.row.getValue('name')}}</span>
    </ng-template>
</data-column>

Use data api to get values with post-processing, like datetime/icon conversion._

In the Example below we will prepend Hi! to each file and folder name in the list:

<data-column title="Name" key="name" sortable="true" class="full-width ellipsis-cell">
    <ng-template let-entry="$implicit">
        <span>Hi! {{entry.data.getValue(entry.row, entry.col)}}</span>
    </ng-template>
</data-column>

In the Example below we will add the ng2-alfresco-tag component is integrate in the document list.

<data-column
    title="{{'DOCUMENT_LIST.COLUMNS.TAG' | translate}}"
    key="id"
    sortable="true"
    class="full-width ellipsis-cell">
    <ng-template let-entry="$implicit">
        <adf-tag-node-list  [nodeId]="entry.data.getValue(entry.row, entry.col)"></adf-tag-node-list>
    </ng-template>
</data-column>

Actions

Properties:

Name	Type	Description
`target`	string	"document" or "folder"
`title`	string	The title of the action as shown in the menu
`handler`	string	System type actions. Can be "delete", "download", "copy" or "move"
`permission`	string	The name of the permission

Events:

Name	Handler	Description
`execute`	All	Emitted when user clicks on the action. For combined handlers see below
`permissionEvent`	All	Emitted when a permission error happens
`success`	copy, move, delete	Emitted on successful action with the success string message
`error`	copy, move	Emitted on unsuccessful action with the error event

DocumentList supports declarative actions for Documents and Folders. Each action can be bound to either default out-of-the-box handler, to a custom behaviour or to both. You can define both folder and document actions at the same time.

<adf-document-list ...>
    <content-actions>

        <!-- system handler -->
        <content-action
            icon="content_copy"
            target="document"
            title="copy"
            permission="update"
            [disableWithNoPermission]="true"
            handler="copy">
        </content-action>

        <!-- custom handler -->
        <content-action
            target="document"
            title="Custom action"
            (execute)="myCustomAction1($event)">
        </content-action>

        <!-- combined handler -->
        <content-action
            target="document"
            title="Delete with additional custom callback"
            handler="delete"
            permission="delete"
            (execute)="myCustomActionAfterDelete($event)">
        </content-action>

    </content-actions>
</adf-document-list>

export class MyView {
    // ...

    myCustomAction1(event) {
        let entry = event.value.entry;
        alert(`Custom document action for ${entry.name}`);
    }

    myCustomActionAfterDelete(event) {
        let entry = event.value.entry;
        alert(`Custom callback after delete system action for ${entry.name}`);
    }
}

All document actions are rendered as a dropdown menu as on the picture below:

Default action handlers

The following action handlers are provided out-of-box:

Download (document)
Copy (document, folder)
Move (document, folder)
Delete (document, folder)

All system handler names are case-insensitive, handler="download" and handler="DOWNLOAD" will trigger the same download action.

Delete - System handler combined with custom handler

If you specify both handler="delete" and your custom (execute)="myCustomActionAfterDelete($event)", your callback will be invoked after a successful delete happened. A successful delete operation happens if there is neither permission error, nor other network related error for the delete operation request. For handling permission errors see the section below.

Delete - Show notification message with no permission

You can show a notification error when the user doesn't have the right permission to perform the action. The ContentActionComponent provides the event permissionEvent that is raised when the permission specified in the permission property is missing You can subscribe to this event from your component and use the NotificationService to show a message.

<adf-document-list ...>
    <content-actions>

        <content-action
            target="document"
            title="Delete"
            permission="delete"
            (permissionEvent)="onPermissionsFailed($event)"
            handler="delete">
        </content-action>

    </content-actions>
</adf-document-list>

export class MyComponent {

    onPermissionsFailed(event: any) {
        this.notificationService.openSnackMessage(`you don't have the ${event.permission} permission to ${event.action} the ${event.type} `, 4000);
    }

}

Delete - Disable button checking the permission

You can easily disable a button when the user doesn't own the permission to perform the action related to the button. The ContentActionComponent provides the property permission that must contain the permission to check and a property disableWithNoPermission that can be true if you want to see the button disabled.

<adf-document-list ...>
    <content-actions>

        <content-action
            target="document"
            title="Delete"
            permission="delete"
            disableWithNoPermission="true"
            handler="delete">
        </content-action>

    </content-actions>
</adf-document-list>

Download

Initiates download of the corresponding document file.

<adf-document-list ...>
    <content-actions>

        <content-action
            target="document"
            title="Download"
            handler="download">
        </content-action>

    </content-actions>
</adf-document-list>

Copy and move

Shows the destination chooser dialog for copy and move actions. By default the destination chooser lists all the folders of the subject item's parent (except the selected item which is about to be copied/moved if it was a folder itself also).

<adf-document-list ...>
    <content-actions>

        <content-action
            icon="content_copy"
            target="document"
            title="copy"
            permission="update"
            [disableWithNoPermission]="true"
            (error)="onContentActionError($event)"
            (success)="onContentActionSuccess($event)"
            (permissionEvent)="onPermissionsFailed($event)"
            handler="copy">
        </content-action>

        <content-action
            icon="redo"
            target="folder"
            title="move"
            permission="update"
            [disableWithNoPermission]="true"
            (error)="onContentActionError($event)"
            (success)="onContentActionSuccess($event)"
            (permissionEvent)="onPermissionsFailed($event)"
            handler="move">
        </content-action>

    </content-actions>
</adf-document-list>

Error, Permission and success callback

Defining error, permission and success callbacks are pretty much the same as doing it for the delete permission handling.

The error handler callback gets the error object which was raised
The success callback's only parameter is the translatable success message string (could be used for showing in snackbar for example)
The permissionEvent callback is the same as described above with the delete action

Folder actions

Folder actions have the same declaration as document actions except target="folder" attribute value. You can define system, custom or combined handlers as well just as with the document actions.

<adf-document-list ...>
    <content-actions>

        <!-- system handler -->
        <content-action
            target="folder"
            title="Default folder action 1"
            handler="system1">
        </content-action>

        <!-- custom handler -->
        <content-action
            target="folder"
            title="Custom folder action"
            (execute)="myFolderAction1($event)">
        </content-action>

        <!-- combined handler -->
        <content-action
            target="folder"
            title="Delete with additional custom callback"
            handler="delete"
            (execute)="myCustomActionAfterDelete($event)">
        </content-action>

    </content-actions>
</adf-document-list>

export class MyView {
    // ...

    myFolderAction1(event) {
        let entry = event.value.entry;
        alert(`Custom folder action for ${entry.name}`);
    }

    myCustomActionAfterDelete(event) {
        let entry = event.value.entry;
        alert(`Custom callback after delete system action for ${entry.name}`);
    }
}

DocumentList also provides integration for 'Context Menu Service' from the ng2-alfresco-core library.

You can automatically turn all menu actions (for the files and folders) into context menu items like shown below:

Enabling context menu is very simple:

@Component({
    selector: 'my-view',
    template: `
        <adf-document-list>...</adf-document-list>
        <context-menu-holder></context-menu-holder>
    `
})
export class MyView {
}

This enables context menu items for documents and folders.

By default DocumentList component uses 'double-click' mode for navigation. That means user will see the contents of the folder by double-clicking its name or icon (similar to Google Drive behaviour). However it is possible switching to other modes, like single-click navigation for example.

The following navigation modes are supported:

click
dblclick

The following example switches navigation to single clicks:

<adf-document-list 
    [navigationMode]="'click'">
</adf-document-list>

Advanced usage and customization

Custom row filter

You can create a custom row filter implementation that returns true if row should be displayed or false to hide it. Typical row filter implementation is a function that receives ShareDataRow as parameter:

myFilter(row: ShareDataRow): boolean {
    return true;
}

Note that for the sake of simplicity the example code below was reduced to the main points of interest only.

View1.component.html

<adf-document-list 
    [rowFilter]="folderFilter">
</adf-document-list>

View1.component.ts

import { RowFilter, ShareDataRow } from 'ng2-alfresco-documentlist';

export class View1 {

    folderFilter: RowFilter;

    constructor() {
    
        // This filter will make document list show only folders
        
        this.folderFilter = (row: ShareDataRow) => {
            let node = row.node.entry;
            
            if (node && node.isFolder) {
                return true;
            }
            
            return false;
        };
    }
}

Custom image resolver

You can create a custom image resolver implementation and take full control over how folder/file icons and thumbnails are resolved and what document list should display.

Image resolvers are executed only for columns of the image type.

Typical image resolver implementation is a function that receives DataRow and DataColumn as parameters:

myImageResolver(row: DataRow, col: DataColumn): string {
    return '/path/to/image';
}

Your function can return null or false values to fallback to default image resolving behavior.

Note that for the sake of simplicity the example code below was reduced to the main points of interest only.

View1.component.html

<adf-document-list 
    [imageResolver]="folderImageResolver">
    
    <content-columns>
        <content-column key="name" type="image"></content-column>
    </content-columns>
    
    
</adf-document-list>

View1.component.ts

import { DataColumn, DataRow } from 'ng2-alfresco-datatable';
import { ImageResolver } from 'ng2-alfresco-documentlist';

export class View1 {

    folderImageResolver: ImageResolver;
    
    constructor() {
        
        // Customize folder icons, leave file icons untouched
        
        this.folderImageResolver = (row: DataRow, col: DataColumn) => {
            let isFolder = <boolean> row.getValue('isFolder');
            if (isFolder) {
                
                // (optional) You may want dynamically getting the column value
                let name = row.getValue(col.key);
                
                // Format image url
                return `http://<my custom path to folder icon>/${name}`;
            }
            
            // For the rest of the cases just fallback to default behaviour.
            return null;
        };
        
    }

}

Hiding columns on small screens

You can hide columns on small screens by means of custom CSS rules:

@media all and (max-width: 768px) {

    alfresco-document-list >>> th.desktop-only .cell-value {
        display: none;
    }

    alfresco-document-list >>> td.desktop-only .cell-value {
        display: none;
    }
}

Now you can declare columns and assign desktop-only class where needed:

<adf-document-list ...>
    <content-columns>
        
        <!-- always visible columns -->
        
        <content-column key="$thumbnail" type="image"></content-column>
        <content-column 
                title="Name" 
                key="name" 
                class="full-width ellipsis-cell">
        </content-column>
        
        <!-- desktop-only columns -->
        
        <content-column
                title="Created by"
                key="createdByUser.displayName"
                class="desktop-only">
        </content-column>
        <content-column
                title="Created on"
                key="createdAt"
                type="date"
                format="medium"
                class="desktop-only">
        </content-column>
    </content-columns>
</adf-document-list>

Desktop View

Mobile View

Custom row permissions style

You can customize the style of the row based on the permissions. The property to use is permissionsStyle[]:PermissionStyleModel[]. The permissionsStyle array can define different styles depending on the permission of the user on that node.

PermissionStyleModel

Property	Description
isFile/isFolder	allow you to select if you want apply the style to file/folder nodes
permission	is an enum value Permissions
css	the name of the class to add

Examples

If you want to change the style on rows where the user can create content:

let permissionsStyle: PermissionStyleModel[] = [];

this.permissionsStyle.push(new PermissionStyleModel('document-list__create', PermissionsEnum.CREATE));

<adf-document-list [permissionsStyle]="permissionsStyle">
</adf-document-list>

adf-document-list >>> adf-datatable tr.document-list__create {
    background: green !important;
}

If you want to change the style on the folders where the user doesn't have the permission to update:


let permissionsStyle: PermissionStyleModel[] = [];

this.permissionsStyle.push(new PermissionStyleModel('document-list__disable', PermissionsEnum.NOT_CREATE, false, true));

<adf-document-list [permissionsStyle]="permissionsStyle">
</adf-document-list>

adf-document-list >>> adf-datatable tr.document-list__disable {
    background: red !important;
}

Custom 'empty folder' template

By default DocumentList provides the following content for the empty folder:

This can be changed by means of the custom html template:

<adf-document-list ...>
    <empty-folder-content>
        <ng-template>
            <h1>Sorry, no content here</h1>
        </ng-template>
    </empty-folder-content>
</adf-document-list>

That will give the following output:

Customizing default actions

It is possible extending or replacing the list of available system actions for documents and folders. Actions for the documents and folders can be accessed via the following services:

DocumentActionsService, document action menu and quick document actions
FolderActionsService, folder action menu and quick folder actions

Example below demonstrates how a new action handler can be registered with the DocumentActionsService.

<adf-document-list ...>
    <content-actions>

        <content-action
            target="document"
            title="My action"
            handler="my-handler">
        </content-action>

    </content-actions>
</adf-document-list>

You register custom handler called my-handler that will be executing myDocumentActionHandler function each time upon being invoked.

import { DocumentActionsService } from 'ng2-alfresco-documentlist';

export class MyView {

    constructor(documentActions: DocumentActionsService) {
        documentActions.setHandler(
            'my-handler',
            this.myDocumentActionHandler.bind(this)
        );
    }

    myDocumentActionHandler(obj: any) {
        window.alert('my custom action handler');
    }
}

The same approach allows changing the way out-of-box action handlers behave. Registering custom action with the name download replaces default one:

export class MyView {

    constructor(documentActions: DocumentActionsService) {
        documentActions.setHandler(
            'download',
            this.customDownloadBehavior.bind(this)
        );
    }

    customDownloadBehavior(obj: any) {
        window.alert('my custom download behavior');
    }
}

Typically you may want populating all your custom actions at the application root level or by means of custom application service.

41 KiB

Raw Blame History

Document List component

Basic Usage

Properties

Events

Details

DOM Events

Data Sources

Node ID

Repository aliases

DocumentList aliases

Setting default folder

Custom icons for selected rows

Calling DocumentList api directly

Custom columns

Underlying node object

Date Column

Location Column

Column Template

Actions

Menu actions

Default action handlers

Delete - System handler combined with custom handler

Delete - Show notification message with no permission

Delete - Disable button checking the permission

Download

Copy and move

Error, Permission and success callback

Folder actions

Context Menu

Navigation mode

Advanced usage and customization

Custom row filter

Custom image resolver

Hiding columns on small screens

Custom row permissions style

Examples

Custom 'empty folder' template

Customizing default actions

See also

41 KiB Raw Blame History

Document List component

Basic Usage

Properties

Events

Details

DOM Events

Pagination strategy

Data Sources

Node ID

Repository aliases

DocumentList aliases

Setting default folder

Custom icons for selected rows

Calling DocumentList api directly

Custom columns

Underlying node object

Date Column

Location Column

Column Template

Actions

Menu actions

Default action handlers

Delete - System handler combined with custom handler

Delete - Show notification message with no permission

Delete - Disable button checking the permission

Download

Copy and move

Error, Permission and success callback

Folder actions

Context Menu

Navigation mode

Advanced usage and customization

Custom row filter

Custom image resolver

Hiding columns on small screens

Custom row permissions style

Examples

Custom 'empty folder' template

Customizing default actions

See also

41 KiB

Raw Blame History