Get task from a task URL

I second Stefan's question above - why do you need this?. In general it isn't possible to determine which task ID corresponds to a URL for security reasons, since if a user had a task ID, it's possible they could then use it programatically to try and cancel or reassign the task. You can use the a!urlForTask to go from the ID to the URL, but it isn't possible to do the opposite.

Hi,

It may be useful if you want to monitor the use of a specific task, in order to calibrate automated tests.

I tried to do so using the tomcat-access.log, but as arjunvs mentionned it, it is not possible by using the URL containing the task ID.

Is there another way to do so ?

Best regards,

Jean-Jacques

I do not understand what "monitor the use of a specific task, in order to calibrate automated tests" is.

I need to repeat my initial question: What do you want to achieve?

Yeah if you want to monitor a specific task, presumably that means that you know the ID of that task, right? Also if you need more information about certain tasks, using task reports to get relevant information is usually your best bet: docs.appian.com/.../Task_Report_Tutorial.html

Our testing team want to calibrate the testing scenario of our application currently in production, to simulate a growth of user.
To do so, they need to reproduce the behaviour of a user, so the approach is to try extracting from the data produce by Appian (log, monitoring), the number of times a task is performed during a typical day run.
As we know the number of user connected to the application during the day, we will be able to estimate the average number of time a user performs a task during a day.
Then our testing team will be able to build a realistic testing scenario, and will be able to level up the number of user, to see at what point the application can support a growth of users.

For the moment, as the testing team have based their work on the URL called by the web browser, they can only see URL dedicated to the call of a task (as the URL specified by arjunvs).
So the question is : can we determine which task is call with the URL, or is there another way to do what we need ?
I hope it's clear now.

Our testing team want to calibrate the testing scenario of our application currently in production, to simulate a growth of user.
To do so, they need to reproduce the behaviour of a user, so the approach is to try extracting from the data produce by Appian (log, monitoring), the number of times a task is performed during a typical day run.
As we know the number of user connected to the application during the day, we will be able to estimate the average number of time a user performs a task during a day.
Then our testing team will be able to build a realistic testing scenario, and will be able to level up the number of user, to see at what point the application can support a growth of users.

For the moment, as the testing team have based their work on the URL called by the web browser, they can only see URL dedicated to the call of a task (as the URL specified by arjunvs).
So the question is : can we determine which task is call with the URL, or is there another way to do what we need ?
I hope it's clear now.

Hmmm, I feel like using process reporting seems a lot easier than trying to track tasks via the URL. Could you create a process report and query it to identify how many processes are executed each day?

Also keep in min that many customers capture this information by writing to the database after a user completes a task, and then queries the database to determine trends or analysis of how many tasks are completed.

I think either of those approaches would be much easier than trying to track data via task URLs.

Thanks a lot for your response !
I'll try these ways !