Process model hit by dropdown value

RE: Process model hit by dropdown value

Chris — Mon, 07 Nov 2022 16:04:57 GMT

Sorry that was a joke, where we sometimes (myself included) will code out examples after making some assumptions on requirements without necessarily knowing the full picture.

Call it years of dealing with partial (at best) requirements 🙃

RE: Process model hit by dropdown value

ujjwalr0002 — Mon, 07 Nov 2022 16:02:07 GMT

I didn't get you

RE: Process model hit by dropdown value

Chris — Mon, 07 Nov 2022 15:59:22 GMT

Code first, ask questions later! 😂

RE: Process model hit by dropdown value

ujjwalr0002 — Mon, 07 Nov 2022 15:56:47 GMT

Exactly now we need help of the author 😅

RE: Process model hit by dropdown value

Mike Schmitt — Mon, 07 Nov 2022 15:54:09 GMT

The problem is, OP didn't provide nearly enough detail for us to draw any conclusions about what UX they're attempting to design here. You may be right and Stewart may be right or all of us may be completely off-base and there's no way to tell 😞

RE: Process model hit by dropdown value

ujjwalr0002 — Mon, 07 Nov 2022 15:50:01 GMT

Yes we can do that I focused on the below line as she wants to perform some action just after the selection I mean call a process synchronously

[quote userid="89970" url="~/discussions/f/process/26463/process-model-hit-by-dropdown-value"]hit process model through dropdown[/quote]

RE: Process model hit by dropdown value

Mike Schmitt — Mon, 07 Nov 2022 15:46:00 GMT

I worry that the previous replies here are, perhaps, "putting the cart before the horse", i.e. reading details into the request that it might not necessarily be asking.

Can you clarify a bit what exactly you intend by "hit process model through dropdown value"? For example, if you want a user to be able to select a dropdown in one interface, then submit the form, then subsequently in that process flow, choose a subprocess depending on what value was chosen, that's fairly easy, and basically considered as "classic functionality" - you'd just have an XOR gateway choosing the process flow to execute based on what value had been provided by the user.

If you mean something else, something more complicated or something more reliant on newer functionality, then you'll need to provide considerably more detail behind what you're thinking of trying to accomplish, than a single phrase.

RE: Process model hit by dropdown value

Chris — Mon, 07 Nov 2022 15:38:43 GMT

As Stewart mentions, you can certainly start a process asynchronously via the dropdown's saveInto, such as:

a!localVariables(
  local!options: {"Red","Blue","Green"},
  local!selection,
  local!processStarted,
  
  a!dropdownField(
    label: "Dropdown",
    placeholder: "-- Select --",
    choiceLabels: local!options,
    choiceValues: local!options,
    value: local!selection,
    saveInto: {
      local!selection,
      if(
        local!selection="Green",
        a!startProcess(
          processModel: cons!YOUR_PM_HERE,
          onSuccess: a!save(local!processStarted,true),
          onError: a!save(local!processStarted,false)
        ),
        {}
      )
    }
  )
)

RE: Process model hit by dropdown value

Stewart Burchell — Mon, 07 Nov 2022 14:57:56 GMT

Well...that's not quite true. You can start a process - albeit asynchronously - from within any saveInto:{} construct in the UI. The process will be started in the background so the user will not, for example, be presented with a modal UI or interact immediately with that process.

RE: Process model hit by dropdown value

ujjwalr0002 — Mon, 07 Nov 2022 12:48:49 GMT

Hi, no we can not EDIT: synchronously start a process on dropdown selection.

Check this link Ways to start a process model in Appian