Skip to main content
Solved

Multi-row task execution on indicium

  • September 16, 2021
  • 2 replies
  • 111 views

Forum|alt.badge.img+15

Hi,

I'm trying to understand the multi task execution via Indicium (Universal):

https://docs.thinkwisesoftware.com/docs/indicium/multi-row_tasks.html

I’ve managed to get it working:

POST /sf/appl/subject(key)/task_dummy/stage

Returns a new location where you can add rows. For each row you call:

POST /sf/appl/subject(key)/staged_task_dummy(id)/add_context

and finally 

POST /sf/appl/subject(key)/task_dummy(id)/commit

However, the add_context step can be depending on the size quite an amount of http calls. This is exact what I would like to prevent with multirow task execution.

Is it somehow to run a multirow task in a single http call, or at a maximum of three? I've tried to run the task without staging, but that gives an error in Indicium:

 Cannot change the value of the property 'multi_row' of 'task_dummy'.The application model prohibits editing this property.

I think this is caused by the fact that the input parameter multi_row is hidden.

I can think of an alternative with an API exposed subroutine, but I was wondering if this was possible out of the box.

Best answer by Vincent Doppenberg

Hello René,

The API currently does not support this. If you would like to see a feature like this, I recommend creating an idea for it, so people can vote on it.

View original
Did this topic help you find an answer to your question?
This topic has been closed for replies.

2 replies

Forum|alt.badge.img+4

Hello René,

The API currently does not support this. If you would like to see a feature like this, I recommend creating an idea for it, so people can vote on it.


Forum|alt.badge.img+15
  • Author
  • Superhero
  • 196 replies
  • October 1, 2021

Hi Vincent, Thanks for the update. 

There is a workaround for this by creating a subroutine with xml/json input and expose it as an API method. Creating an idea for this has no chance I think, it's a quite rare situation I think which don't get much votes, and as there are a lot of ideas and only a few are implemented.

However from a performance point of view I'm a bit worried about the Universal GUI, if it's fast enough if it's doing large amount of http calls when executing a task for multiple rows. I don't know where this is going.


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings