This project is read-only.

Instantiation from and association fom with different classes

Nov 25, 2010 at 11:42 AM


I want to use a seperate instatiation form and a seperate association form, each form should use it's own class (InitConfigurationData & AssocConfigurationData).
But this seems to be not possible, isn't it?
If I use for both forms the same class it works. If I use different classes for each form it doesn't work.

Has anybody an idea?

Nov 26, 2010 at 4:04 PM

This was not allowed intentionally to allow an easy transition between association and initiation forms. This is also the pattern used by InfoPath forms.

I would recommend passing the same data set from association to initiation then finally to the workflow. You don’t need to expose all the information on each form.

Why do you need different classes?

Dec 1, 2010 at 7:55 AM

Hello and thanks for your answere.

I want to use two different classes, because the association data and the initiation data are completly different nature.
During the association I want to specify some groups which are notify during the workflow, for example. During the initiation the initiator shouldn't specify this.

Of course, I can accomplish this with one class. But I thought it would be cleaner to have two classes.