Introduction
Everything in Alumio is divided into distinct tasks. Tasks that provide information about what's running, how long it'll take to process, and the status of the tasks. While processing the task queue, it is done chronologically. Each task is associated with a single route. So, while one route can come with several tasks, each task can only be associated with a single specific route. This article will throw some light on the functionalities of the Tasks Page and how you can utilize them efficiently.
Tabs On The Tasks Page Of Alumio
As you open the Tasks page of Alumio, there is an overview of the tasks. There are distinct tabs on the top that help to define each task such as Identifier, Entity schema, Entity identifier, Status, Route, Created at, Updated at, and Actions.
Identifier: It denotes the task name within Alumio.
Entity schema: It defines the kind of identifiers that you see in the entity identifiers.
If you have them defined, the Entity schema will reflect the defined identifiers.
If it is absent, the Entity schema will be reflected as null.
If the data is short enough, it will show up as the complete data.
If it is not defined and the data is too long, the Entity schema will create a hash format and then reflect that hash over there.
Status: The Status reflects the status of the listed tasks (failed/skipped/finished/new)
Route: It shows the route in a clickable format. If you click on it, you will be redirected to the route details page.
Created at: As the name suggests, it reflects the time at which a specific task was created.
Updated at: As the name suggests, it reflects the time at which a specific task was updated.
Actions: It allows the Alumio users to do some actions such as retry or skip. For instance, if a task is new, you can choose to skip that task.
Buttons Present On The Tasks Page Of Alumio
There are a range of useful buttons in the Tasks page of Alumio that offer a varied range of functionalities such as Route, Status, Created At, Updated At, and Add Filter +.
Route: If you click on the Route button, a drop-down menu will appear listing the available routes. In addition to that, a search bar will also appear that allows you to search for the intended route.
Upon selecting a Route and clicking on Apply, only the tasks related to that specific Route will be listed in the overview. For instance, if you select a Route named Customers from Odoo to SAP, the tasks relevant to the route will be listed.
Status: The Status button allows you to select a certain set of tasks based on task status such as New, Processing, Finished, Failed, Skipped, and Retry.
For instance, if you select Failed, the list of all the tasks designated as failed will show up.
Created At: It allows you to list the task/tasks created at a specific time.
Updated At: It allows you to list the task/tasks updated at a specific time.
Add Filter +: The Add Filter + button allows you to search for tasks based on Identifier, Entity Schema, and Entity Identifier.
For example, you can select the Entity Identifier and search for only those that have a “10” (let’s say) in there. It will list only those tasks that have a 10 in them.
Tracing Tasks And Data Becomes A Cakewalk!
Using the Task Page buttons, you can check what kind of data is coming through, at what time, and what is their status. The wide range of filter options makes it pretty easy for anyone.
You can also go through the lists page after page (or lists) easily at the top-right corner.
There is also a Columns button present which can be utilized to select or deselect certain columns (tabs of the Task Page) as per requirement.
If you want to visualize individual tasks, you can do that easily by clicking on the Identifier of the task (clickable and mentioned in blue). As you click on a task’s Identifier, the Overview will come up first. You can also check the Entity Data (which can be copied) and use it elsewhere as per requirement (for example, in an entity transformer).
In addition to that, you can also check the Import Messages (how is it coming to the system, data filtering, etc) and Export Messages (how the task was sent out, errors in the task, specific filters, etc). They are very specific in nature based on the API system it is communicating with. If there is an error, you can also check the error details (400, 401, 404) in the messages and work on it even without having an in-depth knowledge of Alumio or integration processes.
Stay tuned for more articles that will aid you in being a pro with Alumio!