Indicium Universal Task execution In Indicium Universal, executing seems to contain 2 steps;A staging step, in which a task's default and layout procedures are called, and the context of the parent subject is checked to see whether the user is authorized to execute the task.The URL for this task looks as such:http://<server>/indicium/(iam|sf)/<app_alias>/subject(id=1,idtwo=2,idthree=3)/task_execute_task/stageThe response of this request contains a Location header, in which a URL to the staged task is supplied with a GUID.Step 2, which is the actual execution of the task, is much simpler; we simply make a POST request to http:///indicium/(iam/sf)//staged_execute_task()/commit, which will execute the task on the resource specified when staging the task (subject with id 1, idtwo 2 and idthree 3) and returns a response. We implemented this in our external API based on what happens in the Universal GUI, where we had previously implemented Indicium Basic. However, we noticed a pretty severe downgrade in performan