We've expanded the grouping mechanic within eLogii to allow customers to group multiple Tasks into as one based on pre-set conditions. If conditions are met, all Tasks that meet the criteria will be added as items within the first Task in the sequence that meets the conditions, along with that Task which will be added as an item. This means that if you have 3 Tasks that meet the conditions, all 3 will be added as items to the first Task within the sequence.

You can find this feature in Configuration ⇒ Task CSV Import.

These global settings can be adjusted on each import, so in case you need to change the conditions for another import and override them temporarily, you are able to do so within the Task Import screen.

Additionally, you are able to tell eLogii if it needs to sum any of the Dimension fields. If left blank, then the system will regard the first value as the default value.

In case the Tasks you want to group have items of their own, you are also able to join those items without losing them. The Join items toggle will join items from all Tasks in a group with items for a single group Task. Otherwise, each of the Tasks in a group is represented as an item.

Conditions can be anything you want them to be, and feel free to check our API documentation for reference on condition names.

If you're not too technical, rest assured as it’s straightforward to determine how to write such parameters of the API payload (result) just by looking for the object within the API DOC. For example, let's say we want to use the delivery UID as one of our condition, but we're not sure how we should call the condition - to figure this out, Get the parent object (location) -> Change each curly bracket leading to the target property to a full stop (e.g., location { UID} means location.UID) -> Get the child - target property (UID). Based on this, we now know that the name of our condition should be location.UID.

If you still don't understand how to check the API docs for condition names, feel free to contact our customer support at support@elogii.com, and our technical support will tell you the condition names you need to input based on your use case.

An example use case for this would be if you wish to have Tasks with the same Customer Name and Postcode grouped as one Task, but you want to avoid this for Tasks with the same postcode, and different Customer Names. This is the sheet we're working with:

In this example, we can determine that the Customer Name is defined as the delivery location name, and the postcode is the delivery location postcode. Based on this, we know that both of these are tied to the Task location, and that how we're going to define our conditions.

With these rules, we told eLogii to group all Tasks that have the came Customer Name and postcode, but to not apply that rule to Tasks with different Customer Names and the same Postcode, as they don't meet these conditions.

eLogii will upload our 4 Tasks as 3, and one of our Tasks will have 2 items.