Expand my Community achievements bar.

The Community Advisors application is now OPEN for the second class of 2024. Apply to become a part of this exclusive program!
SOLVED

Workfront AEM Integration using native connector

Avatar

Level 2

With Workfront native connector, AEM and Workfront can be integrated. It allows for creating a linked folder with AEM. The configuration in the native connector creates all the linked folder under a specific root folder. Few questions here:

1) Will AEM have issues with more than 1000 projects created in workfront with linked folder because of a typical recommendation of not having more than 1000 nodes under a hierarchical structure.

2) If the folders that need to be linked need to be created under a different structure every time, what is a possible way of doing it (is it only possible to do that via Workfront fusion to create a folder in AEM under the desired structure and link it to the project to have the final files delivered in that folder)?

 

TIA

1 Accepted Solution

Avatar

Correct answer by
Level 4

Hi @amijain 

 

  1. AEM should not have issues handling even more than 1000 projects created in Workfront. While it's true that in general it's recommended not to have more than 1000 nodes under a hierarchical structure in order to maintain optimal performance, AEM uses the Oak storage repository which is capable of handling large amounts of data. Oak is designed in such a way that it scales horizontally and provides efficient traversal of nodes. However, when you go beyond several thousand nodes, searching for specific nodes might require more time. Scheme of nodes organization should be probably adjusted to improve system performance.

  2. If the folders need to be created under a different structure every time, it may require a combination of Workfront Fusion and some customization within AEM. In this process, Workfront Fusion can be used to trigger the creation of a new folder within AEM. Once the new folder is created, a post-processing script within AEM could be used to move the folder to the desired structure. A custom AEM workflow could also be used here.

Hope this helps.

 

Thanks,

Venkat

View solution in original post

2 Replies

Avatar

Correct answer by
Level 4

Hi @amijain 

 

  1. AEM should not have issues handling even more than 1000 projects created in Workfront. While it's true that in general it's recommended not to have more than 1000 nodes under a hierarchical structure in order to maintain optimal performance, AEM uses the Oak storage repository which is capable of handling large amounts of data. Oak is designed in such a way that it scales horizontally and provides efficient traversal of nodes. However, when you go beyond several thousand nodes, searching for specific nodes might require more time. Scheme of nodes organization should be probably adjusted to improve system performance.

  2. If the folders need to be created under a different structure every time, it may require a combination of Workfront Fusion and some customization within AEM. In this process, Workfront Fusion can be used to trigger the creation of a new folder within AEM. Once the new folder is created, a post-processing script within AEM could be used to move the folder to the desired structure. A custom AEM workflow could also be used here.

Hope this helps.

 

Thanks,

Venkat

Avatar

Level 2

Hi @Jvenkat ,
We have a similar scenario where we are trying to create folder structure using native connector. Couple of challenges we face -
1) Calculated fields in Workfront cannot be used for configuring the folder structure in the connector.
2) If we have the linked folder configuration in template level, we see the folder structure can be seen in all projects created using the same template.
For example, if portfolio/program/year/projname is the structure we configured in the template level and these are dynamic values, I see project1 folder in project2 and vice versa. Is there any way to make it exclusive to the project? Meaning it will not display project2 folder in project1.

Thanks,
Rahul