Question About Process Input Table

bkonia

The documentation for the "Start Process" form operation states the following:

"If the object defined as the process input is different from the owner of the form, you must specify the input in the “Value” column of the “Process Input Table”. Click on the appropriate cell in the “Value” column and enter the process input as the reference attribute of the form owner."

However, the process input table doesn't have a "Value" column. It has a column "A" and a column "B". What do these columns represent? It seems like the system automatically sets column "A" and overwrites whatever the user enters into this column. Also, the process input table contains multiple rows. Why is this? The documentation is really unclear in this section.

pixerp

I'm also interested for some explanations on the same subject.

Thanks

aware_support

The names of the columns are wrong and we will fix them. The first column indicates the name of the object that the process expects as input - these are the same objects you use when you define input for a process. Multiple rows are there because a process may take several objects as input.

The second column indicates a particular instance of a business object that will be used as process input. In many cases this will be the same as the name of the process input. However, in certain cases you may indicate a reference as input. For example, let's say you are defining the form of the object Person and you start the process that takes Person as input. This is what you will use:

Process Input Value
Person Person

Let's say now that you start a process that takes an Account object as a parameter and this account is actually referenced from the object Person -Person.Account. You must specify the value as reference to the account since you are defining the form of the Person (so everything must start with Person):

Process Input Value
Account Person.Account

pixerp

Thanks for the explanation. I understand now some error msg I got.

I know how difficult it is to write a good documentation and can appreciate the effort done with your user's guide.

But I'd like to make one suggestion : adopt the Cookbook style, i.e.

. an image of the screen
. descriptions of each field in short sentences
. examples
. tips & tricks

That would also allow hyperlinking the configurator with the relevant documentation page.

Maybe that could be complimentary to the user's guide...