* fix after rebase * new release strategy for ng next Signed-off-by: eromano <eugenioromano16@gmail.com> * peer dep Signed-off-by: eromano <eugenioromano16@gmail.com> * Angular 14 fix unit test and storybook Signed-off-by: eromano <eugenioromano16@gmail.com> fix after rebase Signed-off-by: eromano <eugenioromano16@gmail.com> update pkg.json Signed-off-by: eromano <eugenioromano16@gmail.com> missing dep Signed-off-by: eromano <eugenioromano16@gmail.com> Fix mistake and missing code Dream....build only affected libs Add utility run commands * Use nx command to run affected tests * Fix nx test core fix content tests Run unit with watch false core test fixes reduce test warnings Fix process cloud unit Fix adf unit test Fix lint process cloud Disable lint next line Use right core path Fix insights unit fix linting insights Fix process-services unit fix the extensions test report fix test warnings Fix content unit Fix bunch of content unit * Produce an adf alpha of 14 * hopefully fixing the content * Push back the npm publish * Remove flaky unit * Fix linting * Make the branch as root * Get rid of angualar13 * Remove the travis depth * Fixing version for npm * Enabling cache for unit and build * Fix scss for core and paths Copy i18 and asset by using ng-packager Export the theming alias and fix path Use ng-package to copy assets process-services-cloud Use ng-package to copy assets process-services Use ng-package to copy assets content-services Use ng-package to copy assets insights * feat: fix api secondary entry point * fix storybook rebase * Move dist under dist/libs from lib/dist * Fix the webstyle * Use only necessary nrwl deps and improve lint * Fix unit for libs * Convert lint.sh to targets - improve performance * Use latest of angular * Align alfresco-js-api Signed-off-by: eromano <eugenioromano16@gmail.com> Co-authored-by: eromano <eugenioromano16@gmail.com> Co-authored-by: Mikolaj Serwicki <mikolaj.serwicki@hyland.com> Co-authored-by: Tomasz <tomasz.gnyp@hyland.com>
4.5 KiB
Title, Added, Status
Title | Added | Status |
---|---|---|
APS Alfresco Content Service | v2.0.0 | Active |
APS Alfresco Content Service
Gets Alfresco Repository folder content based on a Repository account configured in Alfresco Process Services (APS).
It is possible to configure multiple Alfresco Repository accounts in APS (i.e. multiple Alfresco Servers). This service can also be used to link Alfresco content as related content in APS. Content such as documents and other files can be attached to Process Instances and Task Instances as related content.
Note: At the moment you must provide the ActivitiAlfrescoContentService
class from your NgModule
for it to work:
@NgModule({
...
providers: [ActivitiAlfrescoContentService]
})
And also import it in the way shown below.
Importing
import { ActivitiAlfrescoContentService } from '@alfresco/adf-core';
export class SomePageComponent implements OnInit {
constructor(private contentService: ActivitiAlfrescoContentService) {
}
Methods
getAlfrescoNodes(accountId: string, folderId: string): Observable<ExternalContent>
Get all the nodes under passed in folder node ID (e.g. 3062d73b-fe47-4040-89d2-79efae63869c) for passed in Alfresco Repository account ID as configured in APS:
export class SomePageComponent implements OnInit {
ngOnInit() {
const alfRepoAccountId = 'alfresco-2';
const folderNodeId = '3062d73b-fe47-4040-89d2-79efae63869c';
this.contentService.getAlfrescoNodes(alfRepoAccountId, folderNodeId).subscribe( nodes => {
console.log('Nodes: ', nodes);
}, error => {
console.log('Error: ', error);
});
}
In the above sample code the alfRepoAccountId
points to an Alfresco Repository configuration in APS with ID alfresco-2
.
The folderNodeId
needs to identify a folder node ID in the Alfresco Repository identified by the alfRepoAccountId
.
The response contained in nodes
is an array with properties for each object like in this sample:
0:
folder: false
id: "2223d3c2-0709-4dd7-a79b-c45571901889;1.0"
simpleType: "pdf"
title: "JLAN_Server_Installation_Guide.pdf"
1:
folder: false
id: "900b4dc0-bfdc-4ec1-84dd-5f1f0a420066;1.0"
simpleType: "image"
title: "Screen Shot 2017-09-21 at 15.44.23.png"
2:
folder: true
id: "f7010382-7b4e-4a78-bb94-9de092439230"
simpleType: "folder"
title: "Event More Stuff"
linkAlfrescoNode(accountId: string, node: ExternalContent, siteId: string): Observable<ExternalContentLink>
Link Alfresco content as related content in APS by passing in Alfresco node identifying the content, the Share site that contains the content, and the Alfresco Repository account ID as configured in APS:
export class SomePageComponent implements OnInit {
ngOnInit() {
const alfRepoAccountId = 'alfresco-2';
const siteId = 'sample-workspace';
const externalContentNode = {
id: 'da196918-1324-4e97-9d26-d28f1837a0b6',
simpleType: 'content',
title: 'simple.txt',
folder: false
}
this.contentService.linkAlfrescoNode(alfRepoAccountId, externalContentNode, siteId).subscribe(link => {
console.log('Link: ', link);
}, error => {
console.log('Error: ', error);
});
}
In the above sample code the alfRepoAccountId
points to an Alfresco Repository configuration in APS with ID alfresco-2
.
The siteId
identifies an Alfresco Share site in the Alfresco Repository where the content to be linked resides.
You can get the ID for a Share site from the URL: http://localhost:8080/share/page/site/<siteId>
.
The externalContentNode
identifies the content that should be set up as temporary related content in APS. The
externalContentNode.id
points to an Alfresco node in the Share site specified with siteId
.
The response contained in link
looks like in this sample:
link:
contentAvailable: true
created: Tue Nov 07 2017 13:18:48 GMT+0000 (GMT) {}
createdBy: {id: 1, firstName: null, lastName: "Administrator", email: "admin@app.activiti.com"}
id: 6006
link:true
mimeType: null
name: "simple.txt"
previewStatus: "queued"
relatedContent: false
simpleType: "content"
source: "alfresco-2"
sourceId: "da196918-1324-4e97-9d26-d28f1837a0b6@sample-workspace"
thumbnailStatus: "queued"