To count items in a data store based on a condition (ex: Field = "some value"), a Fusion user has to setup a structure similar to the above:Initialize a counter to 0Search the whole data store based on the conditionGet counter referencesIncrement the counter by one each timeThis is required because...

We routinely have to do grouping when making API calls.  That can be over several thousand objects, grouped into bunches of only 50.  It's inefficient to deal with it using the existing mechanisms, such as aggregating to a list and then doing complex slicing with a Repeater.  It would be much more r...

If you "clone" a module that has input filters, the input filters are dropped.  But if you "copy" and "paste" a module, the input filters are brought over.  It's the weirdest little idiosyncrasy.  "Clone" doesn't feel like a "clone" if some aspect of it gets missed in the cloning process.(Certainly ...

Description -When making edits to a scenario, we're finding the process of tracking down all usages of a reference to be cumbersome.  Our current process is to download the blueprint, open in a separate editor, and Ctrl-F to find the one(s) desired. It would be preferable to stay in the Fusion UI bu...

Description -Adobe Workfront allows for setting up complex webhook trigger conditions, including "OR" comparison.  This allows for triggering webhooks for cases like "Field 1 OR Field 2 Changed". The "Watch Event" module in Fusion, however, only allows for "AND" conditions. This results in cases whe...

William, Thank you, and I understand that for that specific condition, such a trick might work.  But it (1) requires familiarity with data structure trickery and (2) is fairly constrained to the types of expressions where you're comparing everything to one thing like that.  If instead of true I were...

Description -The Adobe Workfront custom API module (or any other Workfront API module) is often used to query various API endpoints.  That module doesn't appear to have any built-in mechanisms for handling a retry when a 429 (API rate limit exceeded) occurs, though this is a fairly standard and comm...

Description - Workfront API responses do not appear to return any kind of awareness of rate limits/available query capacity, yet will error with a HTTP 429 status code when we exceed that rate limit.  Ideally, we should know from a prior query how much capacity remains so that we can tweak any sleep...

Description - Person A is editing a scenario.  Person B starts editing that same scenario. Person A saves the scenario with changes.  Person B then saves the scenario with changes. Person A's changes are lost.  Person B was unaware that Person A was (1) actively editing and (2) had saved. This is a ...

Description - All objCode/search queries support $$FIRST and $$LIMIT parameters for pagination.  However, these fail to account properly for lastUpdateDate_Sort=asc where an object may be updated DURING the execution of a scenario, hence the order of entries can be changed in between each separate p...