Ability to set a dynamic array for task input (and ideally also for output).

[Ragheed.Jaboori]

Chorus is not able to send a dynamic JSON array (that contains the object keys to delete). The length of the array is defined at design time, so in runtime there is no apparent way to populate an array with a dynamic number of object keys to delete. That is, there is no dynamic array capability within Chorus which presents a challenge for batch Chorus objects deletion.

[Clararaj]

We are working on implementing Data Objects for 26.1 in Design Studio - From where are you trying to Delete the work objects ? Are you requesting change in the API for DID ? 

[xie_surbiton]

Hi Clara,

We were actually trying to integrate DID API with Chorus. One of the steps is to populate the driver table /api/v1/tracks/{{tracking_id}}, where the payload takes an array of object IDs:

{

    "status": "STAGED",

    "objects": [

...

    ]

}

Whilst this is not an issue on Postman, in Chorus Design Studio the size of an array seems to be defined in design time:

We did try to define a custom data type in WW8U999S - an array of string, the structure looks like: <field><field name="objectids"><field dataType="string" name="objectid"/></field></field>

Then we tried:
* create an array variable of this custom WW8U999S data type

* populate this array

* pass this array variable to that DID API endpoint /api/v1/tracks/{{tracking_id}} on Chorus Design Studio

But in runtime it's an empty array got sent to the DID API, so this attempt/approach didn't succeed.

So we were hoping the ability to populate an array on Design Studio with a dynamic size.

You mentioned that Data Objects for 26.1 is being implemented, I wonder if that will address what we're facing above?

Many thanks!

[Clararaj]

We are implementing Data Objects with 26.1 - yes. However, the ask here is to be able to pass a Data Object to an API via Integration Service. We have a backlog EPIC to address this - https://blueprism.aha.io/features/BPMD-40

However, we will be able to address this only after Data Objects - so most probably looks like a subsequent EPIC to be worked on after Data Objects. 

I will add your use case to the EPIC.