webtop workflow reporting problem

Hi all,

I'm a junior Documentum and I've been asked to create a workflow. the workflow has been validated and installed.

it consists of 5 steps beeing executed by 3 different users(randomly dispatched among the steps),

the problem is the following, when I want to run the workflow through the workflow reporting(logged in with superuser), I can see the different steps, the user who must do the activities BUT I cannot forward(the button is disabled) the activities.(in fact, only one could be forwarded, the other ones could not)

in the other hand, if I log with the different users/performers(in the good order)I can forward and finish the workflow ...

I'm using the documentum 6.5 developer edition.

is there a bug in the webtop workflow reporting or is there an other issue like security or rights?

have a nice day,

Michael.

Find more posts tagged with

Comments

DCTM_Guru

Workflow activities are normally forwarded through Inbox. Are you seeing this behavior in the Inbox as well? Workflow reporting is really to visually depict where the workflow package is with respect to the overall process.

Michael_Planamente

Hi,

Logging with the different users runs correctly, i see the activities in the respective users/performers inboxes and I can "play" with the reject/forward...

As you said, workflow reporting should give the ability to see the different steps of the process and see the currently acquired state AND should also give the ability to "run" each flow's steps if you are logged with the flow owner/initiator.

my problem is that everithing behave as expected except the possibility to run the flow from the worflow reporting(logged as the WF owner/initiator). to run the steps from the workflow reporting, open it, and double click one step, you will have the ability to reject, forward, chose the next step to be executed. that functionality is notworking in my case;

thank you,

Michael.

DCTM_Guru

This might be a bug. As stated in my previous post, workflow activities are normally performed within Inbox, so this use case has been thoroughly tested. What you describe is not typical use case, so it may not have been tested.