How To Get Queue Items Based On Output Data Field

[ppr (Peter Preuss)]

@ashokkarale
Let us share some info as we had implemented a similar case in the past

Options:

• Get Queue Items
  • do some initial filterings
• ORC Rest API
  • do some filterings and include an initial check on OutputData containing the MoveAt key

In both cases a postprocessing (essential / LINQ /…) will do the details)

With the Rest API we do have options for advanced filtering. But the Output property will cause a failure when involved in filtering and other items do not have. Unfortunately, the AND operator checks all filter conditions (same topic as we do have the AndAlso operator in VB)

Strategies (General)

• Only items with the status successful can have an output. So we can use this status as a filter option
• others, your case specifics maybe can be mapped on the creation date
• order when

Strategies ( REST )

• filter on the status and the existence of MovedAt within the OutputData provided JSON string
• order when possible (see below part paging)
• reduce the data with the select option when possible

Paging (Get Queue Items)

Need an example to loop Get Queue items activity after reaching 100 and should check all the items in Queue

@maddy99 Variables: [grafik] Flow: [grafik] Properties: [grafik] After Paging all retrieved QueueItems are stored on ListQueueItems Also have a look on the Orchestrator API

Paging (REST)

• we retrieve within a first call the count
• in subsequent calls we used skip/take in relation to the previous retrieved count

Summary:

In our case, we decided on the rest API as we were able to use it more flexibly. Before the implementation, we prototyped our ideas with the help of swagger