What kind of "additional parameters" do you have in mind? You can probably use global (non-local) variables to achieve this, but a well-defined use case will be easier for the discussion. For a sample of the non-local variables, see the below post.
https://jazz.net/forum/questions/217064/rtc-601-make-required-attribute-depending-of-the-previous-values

0ur scenario is that we need to temporarily bypass Required Attributes For Condition and Read-Only Attributes For Condition checking when programmatically updating / creating a work item.  We currently do this by setting an "internal work item attribute" to true.  We then reset the internal attribute back to false in a work item operation participant via an additional work item save.  While using an internal attribute does work, it has following issues:

(1) The additional work item save causes unnecessary / unexpected emails to be sent to the work item subscribers.  This is a critical issue for our users.
(2) The additional work item save causes significant performance overhead.
(3) Additional logic is required in our operation advisors / participants to properly handle the addition work item save.

We are looking to address these issues, especially the first one, by using work item additional save parameters, rather than an internal attribute, to indicate that Required Attributes For Condition and Read-Only Attributes For Condition checking should be temporarily bypassed.

I don't fully understand what "additional work item save" is, as I haven't done much advisor development using the RTC SDK. But as you indicated that you use JavaScript condition scripts, will it be beneficial to just return "false" at the beginning of the condition script, when seeing a particular variable (my choice is a JavaScript global variable) is set?

Don, when you save a work item with the client or server API, you can provide "Additional Save Parameter" - basically strings. There are some built in ones e.g. to create back-links. Another way to use them is to allow automation to cope with recursion. E.g. in an automation, you could save a work item which triggers the same follow up action again. You can use an additional save parameter to communicate the reason for the save to other participants e.g. to avoid to trigger any more subsequent saves.

Don, can you point me to information on RTC's use/support of JavaScript global variables?  Specifically, I need to know if a JavaScript global variable can be set in a standalone Java application using the RTC SDK to access RTC and subsequently read in a JavaScript used by the Required Attributes For Condition and Read-Only Attributes For Condition preconditions.