Use Indentifier ID in task payload

[catalin]

Hello there,

Currently in the created task “Overview” tab.
The Entity Identifier is set by us using the Entity Schema.

What if we would like to use the “Identifier” generated by Alumio for that specific task?
Like when sending an order, or latest update entity we would have a link to Alumios task.
As current, there is no way to access that information trough a transformer.
The only other topic related to this is

getTasks for specific routes using Alumio API

Hi Alumio Team, Good day! We want to link the errored task from Alumio to our system so we can check the failed tasks for specific routes. I checked the API documentation and it seems that this is not possible at the moment but not sure if you have a workaround for this. Here’s what we want to do: We want to get the tasks for specific routes through API however, there are only 2 endpoints available on your API docs. -getTasks - get all the task but this will apply to all routes. -getTask - …

That would mean to do a workaround request inside Alumio to get our task data by the Entity Identifier.

Is currently possible to get the “Identifier” id when running a task?
Could also be considered as a feature requests.
Thank you!

[Alumio_Bot]

You can create your own id by combining several fields from your payload.
Or selecting an existing id within the payload, for Alumio to use.

With the entity schema’s.
By filling the identifier path.

Entity Schemas in Alumio

Table of contents Introduction Creating and maintaining entity schemas Automatically validate incoming data Video guide Introduction Entity schemas define the structure, validation rules, and identifiable information of data. By default, all data flowing through your integrations are assigned to the default entity type. In this case, no structure, validation, or identifiable fields are present. Your Alumio environment will come with a set of standard entity schemas which offer pre-set stru…

[catalin]

Hi @Alumio_Bot ,

Thanks for the answer.

We have already set up for that specific Route a Entity Schema, as you can see, there are 3 fields set for identification.
We are looking for a better way to get the current generated unique “Identifier” by Alumio, inside the payload and use it when POST-ing data outside of Alumio.
Like in the example :

We would like to use the “Identifier” to add id to an URL field when sending the payload, or pass to whole url.
Here are 2 examples of how we would use them:

{
"url":"https://admin.alumio.com/boom/tasks/queue/&{alumio_generated_identifier}"
"url_2":"&{link_to_task}"
}

[Alumio_Bot]

Hmm yes that is slightly different,
The @Alumio_support team will have a look.

[Gugi]

Hi @catalin

Could you please let us know whether it is blocking your integration?

[catalin]

Hi @Gugi ,

Our client that uses this logic would benefit a lot from it in the long run, if this request could be implemented in the near feature.
Currently, we can manage without sending the task URL trough the payload, but it would improve quality of life for debugging immensely.

[Gugi]

Hi @catalin,

Thank you for your answer. We passed the request on to the team for further discussion. A story has been added to our backlog to implement it. However, we cannot provide you with any estimation at the moment. We will let you know once we have any updates.

In addition, you can subscribe to our Release Notes to check once the feature has been released in the future.

Thank you very much for your feedback! Please let us know if you have any other feedback.

[Gugi]

Hi @catalin,

We would like to inform you that the task identifier is now available with the syntax @{scope.task} anywhere in the outgoing configuration.

You can use a Value Setter with @{scope.task} as the value, and it will get you the identifier of the task.

Please give it a try and let us know if that works.

[catalin]

Hi Gugi,
Working great.

Is this already on Live environments, didn’t see anything yet in the release notes?

[Gugi]

Hi Catalin,

Good to hear that it works great.

Yes, it should be available since Alumio version 3.62.0.

Thank you for bringing this to our attention. Going forward, we’ll take extra steps to ensure all relevant details are included to keep you fully informed.

We appreciate your understanding and your help in making our communications better.