Custom WDK components for specific activities

Dear all,

I have some manual activities in a workflow that must be defined using custom wdk components.

Is it possible to customize taskspace in order to intercept invoke custom wdk components that will handle specific manual activities ?

What I was looking for is some sort of interceptor to fire the component call according to the activity and process name.

I mean a sort of logic like this :

if(activityName = 'ActivityA' and processName = 'SimpleProcess' ) {

use customComponentA

} else if(activityName = 'ActivityB' and processName = 'SimpleProcess' ) {

use customComponentB

} else {

use taskspace default behaviour

}

Find more posts tagged with

Comments

kcrkarthik

What does customComponentA and customComponentB do? Do they have any screens where user needs to perform some activity or fill some information?

Here are some steps.

1) Create the wdk components and the action

2) Register that with the task space application (by adding the action id to plain actions xml and then creating Action configuration in the Taskspace application)

3) In forms builder, for the Task form, include the Invoke Button. This button allows you to select the Action from a specific taskspace application.

-karthik

lmarini

What does customComponentA and customComponentB do? Do they have any screens where user needs to perform some activity or fill some information?

WDK Components will have to perform both operations.

Here are some steps.1) Create the wdk components and the action2) Register that with the task space application (by adding the action id to plain actions xml and then creating Action configuration in the Taskspace application)3) In forms builder, for the Task form, include the Invoke Button. This button allows you to select the Action from a specific taskspace application.-karthik

We have an inbox component designed to render all task of a specific user. We would like to render the custom components from the inbox component instead calling a task template to do that. A task template will be called in the "else" branch, so just if the action is not named 'ActivityA' or 'ActivityB'.

kcrkarthik

I could only understand half. Post pictures of what the screen should look like and the flow.

"WDK Components will have to perform both operations." -> what is that you are trying to achieve by WDK component that cannot be done using Forms?

Assuming that you designed all the components (including inbox) using Forms Builder's Task List taskspace component form, I'd suggest to create 3 separate Task forms. One for ActivityA-SimpleProcess, other for ActivityB-SimpleProcess and the 3rd one for all other tasks.

And, what do you mean by "use taskspace default behaviour"?

lmarini

Sorry,

I probably made some confusion exposing the problem.

I currently have several tasks, each of them uses a Task Template to be managed, the problems comes when you have to do something that is not supported by Forms Builder like complex interface design. In our case using a Task Template is not an option, a wdk component to present the task with related functionality is a solution for that.

With taskspace default behaviour I mean the out of the box action/task template association that I would have to inherit.

I am currently working on a customization on this action definition to do what I mean.

</action>

</scope>

But I am looking for some other way to do this.

kcrkarthik

It is the LaunchTaskManager action class that is resposible for launching the appropriate component when you open the inbox item.

lmarini

I will define criterions to switch to the specific component, the LaunchTaskManager action will not be used to do so but will remain the default behaviour if all criterions fails.

I think this not is the best approach to solve this issue because controls to be executed will increase as lons as I have new custom task view to show.

Thanks for your help.