bunchukokoy wrote:
What I mean Sir is the chore, not TI, he can't edit the parameters from the Process included in this particular chore. Because, what they want is that they will upload using the chore, not direct to process included in it. (
they're choosy 
)
I don't believe that you can do that; it'll run with the chore defaults, which AFAIK can't be intercepted. However rather than using a chore, there's nothing to stop you from giving them access to a master process which has all of the relevant parameters, and which uses ExecuteProcess functions to call the remaining processes. The effect is essentially the same. If you only give them access to the "master" process they won't even know that the other ones are there. Then you tell them to execute that process, rather than executing a chore. It probably won't make any difference to an end user; they won't know the difference between a chore and a process anyway. To them all it is is "the thing that I was told to run".
A second alternative is to leave it as a chore, but instead of getting them to enter values into the parameter box, get them to enter them into a control cube ahead of time. The processes can then pick up the entries from the control cube rather than from the parameters dialog.
Frankly I think that option 1 is the better one since with option 2 it would be too easy for a user to forget to set the parameters before they run the chore.
