nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

How to get Attached document from workflow - CWS

Tural Salahov

Hello. i've a user authetntication and can get workflow assignments for the logged in user. but when i try to get "ApplicationData" it only has comments and atrributes, but no documents. so, don't know how to get attached document from workflow and download/open it. my code snippet is as following

WorkItemResult wr = fWorkflow.listWorkItemsEx(null);
List<WorkItem> wiList = wr.getWorkItems();
Iterator<WorkItem> itr2 = wiList.iterator();

while (itr2.hasNext())
{
WorkItem t = itr2.next();

List<ApplicationData> appData0 = fWorkflow.getWorkItemData(t.getProcessID(), t.getSubProcessID(), t.getID());

for(ApplicationData data : appData0)

{

System.out.println(data.getDescription());

}

Find more posts tagged with

Comments

Appu_Nair1

Perhaps you can understand my approach.WFDATA structures are hard to understand but in simple terms when the instance record is fetched position "0' is for attachments,it can be found by that calss name as well.Then everything on this Attchment is normal DocumentManagement operations

List<ApplicationData> wfPackageDetails= wflowClient.getProcessData(WF_ID, WF_ID);
       AttachmentData attData= new AttachmentData();
       attData=(AttachmentData) wfPackageDetails.get(0); //0 is always attachments also it is called Attachmentdata
       System.out.println("Attachment ID which is Docman Operations is"+attData.getContainerID());
       List<Node> childrenNoGrandChildren= docManClient.listNodes(attData.getContainerID(), true);
       //this is a loop of all firstlevel no recurse id's in your attachment volume so use smart methods to iterate that
       System.out.println(childrenNoGrandChildren.get(0).getID());
       System.out.println(wfPackageDetails);

My full source called Worklfow.java at https://communities.opentext.com/communities/cs.dll?func=ll&objId=10154004&objAction=download&viewType=1

Tural Salahov

Hello Appu,

Thank you very much for your reply. So, now it is

WorkItemResult wr = fWorkflow.listWorkItemsEx(null);
       List<WorkItem> wiList = wr.getWorkItems();
       System.out.println("workflow size: " + wiList.size());
       //Iterator<WorkItem> itr2 = wiList.iterator();

       for(WorkItem t: wiList)
       {
           List<ApplicationData> wfPackageDetails= fWorkflow.getProcessData(t.getProcessID(), t.getSubProcessID());
           AttachmentData attData= new AttachmentData();
           for(ApplicationData ad: wfPackageDetails)
           {
               System.out.println(ad.toString());
           }

But the thing is when authenticated user is not admin getProcessData gives an error of "You do not have enough permissions to view the process data"

Can i use admin's authentication to get processdata for the logged in user? Thanks

Appu_Nair1

Not sure if I understand everything that is being said but here should be a few helpful hints.

In properly maintained livelink installs/organizations nobody will ever part with the 'admin' user's password.It is like asking for the root's password in unix .So if you are developing in your own livelink where you know the admin's creds do not think that you will get that in another org.Especailly in medical and federal applications workflow audit is very highly insisted.It is also bad parctice all in all to play with a really powerful login.
Can you still get something for another user.Sure .It is called "impersonation". You will first login as a user who has "SA Privileges" in livelink.You are then as powerful as the user 'Admin'. Then you say "Impersonate user X" and the system will part with the info for that user.I beleive you have C# and java samples for that here right where they show you samples.If not search in my name,I think I have some C# sample showing impersonation, or Brad Ceballo ex OT great guy putting java samples.I base most of my java code on his.Use Advanced Search in this forum.
The correct workflow design is as soon as you have painted a map,you would create a group say "My Workflow Manager Group" and make that group the "Master Manager" and strip out "<Initiator />" out of most of the powerful things in the workflow that OT puts as default.In this case any user whether gui or cws who has access to that group can monitor the details of the map.

Good Luck

Guy_Pomerleau

Is it a web a pplication or a client-server apps. Tomcat or IIS? If web apps, did you activate the impersonate so the user credential could be pass?

Tural Salahov

Thanks for your answers. the thing is all i want to get is attached document in workflow task that is assigned to a user, which the user has permission to see. if the only way of getting attached document from workflow task (workitem in ws) is using getProcessData() why it throws "not enough permission to get process data".

and about the impersonation when i check the log i see that impersonateUser method doesn't get called. and i get error of "Insufficient permissions to perform this action"

Guy Pomerleau, it is client-server app on java, and server is tomcat, not web app.

thanks

Joerg_Wuerzer

To execute 'WorkflowService.GetProcessData' the logged on user requires administrative permissions on the workflow instance. Otherwise you have to execute 'WorkflowService.GetWorkItemData'. This method also returns an array of type 'ApplicationData' containing one element with the attachment folder id.

Regards Jörg

Tural Salahov

thanks Jörg

when i use getWorkItemData it only returns CommentData and AttributeData, not AttachMentData

List<ApplicationData> wfPackageDetails = fWorkflow.getWorkItemData(
                   workItem.getProcessID(), workItem.getSubProcessID(), workItem.getID());
           for (ApplicationData ad : wfPackageDetails)
           {
               System.out.println(ad.toString());
           }

Joerg_Wuerzer

What are the enabled packages in your workflow? This makes only sense if the attachments package isn't enabled in your workflow.