There is perhaps a way to do it, but I would point you to Adobe PS and/or support for guidance on this.  It uses an unpublished feature of the API and we had to receive special dispensation to use it.  (Not saying we're special, just don't want to publicly go against Adobe's standard position on thi...

Sure, it's the same, just in reverse and using a POST/PUT (depending on whether you're creating or updating): { "hours": [ "123", "456", "789", ... ] } where each of the entries in the array are the IDs of the hour object that you want associated to the billing record.

I think you have to use the Custom API Call module (at least, that's how we do it).  Here's an example pipeline that gets to just the deletion portion.  Note that it's simply about setting the hours value to an empty array.

Routers are sequential in processing, with priority order determined by the order the connections are made.

We do this type of thing all the time.  You have two paths, generally, for how to implement it.  Either way, you’re effectively creating a distributed job queue.One option is to use a data store to hold the information needed to process.  In your first job, add records to the DS and mark them as “pr...

Fusion’s programming model is one of “pass-by-value”, not directly “pass-by-reference”.  It also took me a bit to understand.In effect, each “set” or “get” reference is a unique and immutable copy of the data involved.  So doing any kind of “increment” operation requires updating the variable refere...

Wait, I re-read your message and think I now understand.  How about this?I'm attaching the blueprint for your reference/inspection.

Hi Lars,I'm trying to follow the actual ask, so apologies if I get something wrong.  I think you have a data store structured like this:Email AddressCategoryIf the Category is a value of xy, then you want to process those values, such as aggregating them together.So you'd want something like this:Sc...

It's pretty straightforward.  You can either use the Delete module or the Custom API module with a method of DELETE and a URL of bill/{id}.  Just make sure the billing record first has no hours associated to it and it's not in "invoiced" status.  So you may need to do some updates to the record PRIO...

Tools to help better manage scenario performance would be useful to know where to focus efforts on optimizing scenario configurations.  For example, given a scenario that calls three services, a heat map showing overall processing time of a given module could indicate that a module or set of modules...