Skip to main content
Solved

Populating multi-choice enumeration via a Workflow

  • November 7, 2025
  • 5 replies
  • 92 views

Hello,

I'm struggling to populate a multi-choice Custom Enumeration attribute via Camunda Workflow in IFS Cloud.

 

I have a custom attribute (e.g., Cf_Factory) that is a multi-choice (multi-select) custom enumeration.

  • When adding a row using the UI, I can see (in the debug console) that the field expects an array like:
    Cf_Factory: ["CfEnum_London", "CfEnum_Manchester"]

  • When I try to create this row using Camunda Workflow, things break:

    • If I set a single value: execution.setVariable('Cf_Factory', 'CfEnum_London');, it works.

    • If I try to set multiple values, nothing works. I’ve tried multiple things via a Script Task: ArrayList, Spin, comma-separated (["CfEnum_London","CfEnum_Manchester"]), etc

Has anyone successfully set a multi-value (multi-enum) Custom Field via Camunda Workflow? Surely this must be a common task and usage for Workflows?

 

I am on IFS Cloud version 23R2.

 

Any advice or experience would be much appreciated!

Best answer by JoDe

@karale,

Back when I started first implementing the cloud version, I noticed this and notified IFS about this. But they see it as a missing feature, not as a bug, so even though the initial report date was in 2022 it hasn't gotten a solution yet. 

5 replies

  • Author
  • November 11, 2025

I’ve worked around this by having the workflow trigger a PL/SQL event action, which handles the data population through a standard CRUD Update call.

 

However, I’m curious whether this could be achieved directly through a Camunda IFS API call instead. If PL/SQL event actions are eventually being phased out in favor of Workflows, there should logically be a native way to perform this kind of update within the Camunda context itself. Has anyone explored or implemented such an approach?


Forum|alt.badge.img+11
  • Hero (Customer)
  • Answer
  • May 28, 2026

@karale,

Back when I started first implementing the cloud version, I noticed this and notified IFS about this. But they see it as a missing feature, not as a bug, so even though the initial report date was in 2022 it hasn't gotten a solution yet. 


  • Author
  • May 29, 2026

@karale,

Back when I started first implementing the cloud version, I noticed this and notified IFS about this. But they see it as a missing feature, not as a bug, so even though the initial report date was in 2022 it hasn't gotten a solution yet. 

Thanks for the information. Yeah, makes sense. I think it’s quite a critical “missing feature”, at least in our environment I can think of 5-10 use cases where we could convert PL/SQL Event Actions to Workflows if this was possible. Not to mention all new developments that we have to do in PL/SQL just because of this limitation. I’ve been trying to first implement everything via Workflows, then only resort to PL/SQL if really needed.

 

But seems like the scrapping of Execute Online SQL is not really happening in the near future, despite the warnings. Workflows still need a ton of new features before they can realistically replace the current PL/SQL scripts.


Forum|alt.badge.img+11
  • Hero (Customer)
  • May 29, 2026

@karale , Luckily it's not deprecated.

Our company was the early adopter of the workflow because at first it was documented PLSQL would be deprecated in 23R1, so during our implementation we had to redo a lot of our configurations only to find out we opened pandora's box. These days it's a lot more stable and logical then what we came from. But I absolutely agree, this is quite a critical function NOT to support with an engine like this.


  • Author
  • June 3, 2026

Since this seems to be technically impossible to do at the moment, I’ve converted this into an idea.