Process model

Hi muhammedf7064 , It actually depends upon what you want to achieve. If required either of the choices can be used. As part of best practices, we should always try to use as minimum as possible. Avoid using unnecessary process variables.

It will be great if you can try to minimize the count of local variables as much as we can. but it totally depends on the requirement.

Hi,

To exchange data between an interface and a process you need a variable for each rule input. That means you need 5 process variables. 

As has been mentioned already it really depends on what your requirements are. Some fundamentals might help here:

• rule inputs in use interface objects are not variables in their own right. They are "pointers" to variables
• interface objects used in User Input Tasks in process models reference process model variables directly but they don't have to - they can reference them indirectly (that is a value is copied from a pv! into an ac! and thus made available to the mapped ri!) - or you can derive/fetch values directly into an ac! without ever having to populate from/to a pv!

5

For best practice , No of Process Variables in Process Model should be same as No of Rule Inputs in Interface.
So, For this case 5 is Correct Answer.(considering Best Practice)

But you can have more as well according to the requirements.

This question really bugs me, because the only possible correct answer is "There's no way to actually know". Some rule inputs may be completely optional, and irrelevant in certain process contexts; some might expect a hardcoded value to be passed in, and therefore would never map to any particular PV.

Additionally, the idea it asserts of "process variables required in the user input task" is nonsensical - there is no such direct tie.  PVs will usually be assigned into and/or assigned the output of ACP variables, and also PVs can be passed directly into a rule input (when that PV won't be changed at all by the output of the task), but neither of these things is quite the same as "process variable required in the task".

If a question is phrased such that knowing more about the subject / thinking more about it makes it HARDER to answer, then it's a BAD QUESTION.

I agree. Questions that include "best practices" and "required" are probably bad questions altogether.

hey muhammed,
5 is the correct answer

When dissecting that question even more, none of the answers is correct, because there are no process variables inside a user input task.

"process variables are required in the process model's user input task"

Or we just close this thread ...