Hi All,
I have a scenario where Appian task is already created with the task display name, for example as 'Task abc with amount $100".
Now when the user opens the task form, the amount will be recalculated in local variables and and are updated in database using Store Procedure execution function in local variables .
So, every time when the form loads, the amount will get refreshed and updated in Database as well.
Now my issue is ,when the amount is refreshed, the task display name should also get refresh,
for example if the amount is refreshed from $100 to $200 , then task display name should be 'Task abc with amount $200".
Note: The amount in task will get refreshed at the time of form loads, without any user interaction inside the form.
Please help me to achieve this.
Thanks in Advance.
Discussion posts and replies are publicly visible
Task names are evaluated at assignment time and (AFAIK) not evaluated again at all. The best I suspect you'll be able to do here (though other users might have some other tricks), is to give the user a "refresh" control (button, link, etc) that secretly submits the task and loops back to it again, creating a new instance with a refreshed evaluated name. That would require 1 user click at a minimum, but as I said I don't expect you'll get a way that has zero clicks.
Can you tell us a bit more about your use case for wanting the Task Display Name to change? Generally speaking, the user won't really see it after they've opened the task, unless they abandon the task again without submitting. That's possible, of course, but seems like a bit of a corner case.
I have a similar use case where the user is able to clone an existing record, which generates a new task for editing. The "Request Title" field is included in the task display name, and also editable by the user in the task. There is a case where the user would edit the Request Title and then save the task as a draft. When the user returns to their task list, the task display name is not refreshed with the updated Request Title. This is confusing to the users.
As you suggested, I could suppress the ootb "Save Draft" button, and create a custom submit button that loops back to the same task. That might be the way to go...
Zach Goldsby said:As you suggested, I could suppress the ootb "Save Draft" button, and create a custom submit button that loops back to the same task. That might be the way to go...
Yes, this is the only way to update the task name at this time (restart the task). As Mike notes, we typically use this method of a custom "Save & Close" type button that submits the task, loops back to itself so the task name can be re-evaluated.