Video Screencast Help

Track Progress of a workflow in Process Manager

Created: 20 Feb 2013 • Updated: 21 Feb 2013 | 6 comments
This issue has been solved. See solution.

I have built a workflow that our HD uses to schedule a laptop migration. How do I go and see what step the project is on after the Tech schedules the job? I put in Set Process State/Status components but not sure how to see this data. Since the workflow requers the end user to acknowledge when they are ready to start the migration, I want to know if the task is still waiting for their input.

Operating Systems:

Comments 6 CommentsJump to latest comment

rhamner's picture

The Reporting components write to the Process Manager portal. When you view a process you'll see the status, comments, etc. written by the components.

noodleNT's picture

I am not seeing anything in there. Should the data saving mode be something other than project?

rhamner's picture

No, most time project is fine assuming the property below is still set to LBME.ReportingQueue. Is this a workflow project type? Are you running the workflow on the same server as Process Manager?

  1. Make sure you have a 'Global Logging Capture'  component. 
  2. On Workflow components, like Dialog Workflow, change 'Task Source Type' to 'Process Manager Task Source'. Make sure assignees actually exist in PM. 
  3. In Process Manager go to Reports tab and in Category on left click default. Click on action icon next to the Process Viewer report and choose Copy. Name it something like Process Viewer - All. Edit this new report and on data filters on left side in 'Process Management' section uncheck 'Assigned to Me' and 'Not Completed'. This will at least let you see the process if its not assigned to you or already complete.

Here's an example. Almost all the data on this page can be set through components in Reporting--Inline of toolbox.

rhamner's picture

Also, I forgot to mention, if you're just testing but not using an admin then use the Setup Process component to grant process view permissions to a group that you're in. Otherwise, you still wont see the process. In a production workflow you'd do this anyway.

noodleNT's picture

Ahh I was looking at the wrong thing in the portal! If I go to report you stated in step 3 I see my tasks!. I also set the permissions on the the SetupProcess component to the groups I wanted access to see this stuff. Is that something you have to do for ever workflow or is there a default config some place?

Also, how do I set the primary contact\assignee to the ticket? I start with a form start workflow, this is the Help Desk Tech doing the migration and setting up the new hardware. I use the process manager login component in the main dialog workflow. Once logged in they pick all the build and software settings they need for the new machine and if they are going to migrate data. This all gets saved to a global and then the process gets created and the imaging jobs get scheduled outside the dialog workflow. After that, any other notification that is needed is handled by the Quick Link Dialog compenents.

rhamner's picture

I also set the permissions on the the SetupProcess component to the groups I wanted access to see this stuff. Is that something you have to do for ever workflow or is there a default config some place?

This is something that you set up for each workflow. However, if you have a certain group that you want to be able to view all processes you can add the ProcessData.ViewAll permission to the group.

Primary Contact and Assignees are two different things in a workflow. Assignments happen on tasks, like when you have a Dialog Workflow component. You can set the assignment there or after the fact with components. Being a contact doesn't really mean much in a workflow by itself. I think it may give the contact access to the process but other than that any usage would be up to your application. Contacts can also be set by components.

If you're using a form start workflow then you probably wouldn't have any assignments (unless you have other Dialog Workflow components). In this case there's not really a task since the user is starting a completing the dialog in one step.