Product ideas | Community
Skip to main content

Filter by idea status

10000 Ideas

watermsuNew Participant

Workfront Documents Project vs Task (Story)New

There are two ‘Documents’ places that we use to save documents on Workfront: Project and Task   Saving files in Task – Documents: In our project team, people get assigned to subtasks in tasks. It's easier for the team to go and see what the relevant files are within Task-Documents. However, when we save files and create subfolders in Task-Documents, the related “Project” Documents don’t have the same folder structure that’s in Task. For example, if we save files A, B, C and organize the files in subfolders in Task, then when we go to its Project, files A, B, C are just saved in Project Documents as loose files, not in any subfolders. We have a lot of different tasks in one project, and it makes difficult to know which files are for which tasks unless someone goes into Project Documents and create subfolders and organize files manually. Or people need to go different tasks and try to find the files they need. Often times we have multiple tasks for one work item (i.e., one task for creating website content, another task for content edit/approval, and another task for website build/production, etc.). Either way, I don’t find this is efficient.   If we save files in Project – Documents: people go into Workfront and see the subtasks they are assigned to, then they have to get out of the Task and go one level up to find files from Project – Documents. I am not sure if this is ideal either.   My goal here is that we save files to Task Documents, then when we go to Project Documents, we can filter the files based on the tasks related to the files. I played around with filter/grouping in WF and I could figure out how to group based on tasks, but document list with tasks looks too busy; I can’t figure out the best way for this. I feel like there must be a way to organize documents in Project without manually creating subfolders.   I want to make sure that we have organized folder structure for each project/work so that when we try to find something even years later we can still go in and find what we need, and people know where to look. Ideally, even someone who didn’t get involved with the project, they should be able to find the files when they try to achieve it.   Please let me know what you think.   Thanks! Sunny Waterman

tushaar_srivastava
tushaar_srivastavaNew Participant

Bulk Publish/Unpublish/Delete nodes based on uploaded CSV.Approved

Request for Feature Enhancement (RFE) Summary: CSV Import Tool which perfom Publish, unpublish, delete, Move actions on given paths in csv  Use-case: Generally in any project we have multiple nodes [Pages, Assets, Renditions...] that need to be Publish/Unpublish/Delete, and example n number of nodes are not in use and cause huge impact on environment performance and we need to unpublish those and then delete it, it could be n number of assets, pages [which used for testing or duplicates etc]. and let say the number could be in 1000+. so in that case we have to write groovy script, servlet, scheduler or worflow etc, to read the path of nodes from particular CSV and do operation like publish, unpublish, and delete using replicator API or in anyway. and writing this code need lot of optimization based on environment behaviour [e.g : making it sync or async]. Instead of this approach if we could have a generic solution where the product have a CSV importer tool which will read the path of nodes from CSV and perform actions like delete, unpulish, publish.  Current/Experienced Behavior: Currently I have 30,000+ Assets which are duplicate, and the path of those assets are stored into a CSV file by the QA, Stakeholder team and I need to remove those incluing their properties which holds their renditions path  since it is duplicate, before deleting I need to unpublish those nodes. Improved/Expected Behavior: a tool which which read the path of nodes from CSV and perfom actions like Publiish, Unpublish and Delete.  Environment Details (AEM version/service pack, any other specifics if applicable): AEM6.5 and above. Customer-name/Organization name: Generic Screenshot (if applicable):   Code package (if applicable): reference post : https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/aem6-5-unpublish-and-removing-bulk-assets-using-path-from-csv/m-p/562255#M139958https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/aem6-5-servlet-to-unpublish-and-removing-bulk-assets-using-path/td-p/562621https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/aem6-5-read-multiple-properties-from-a-node-and-perform-action/td-p/564264