How to update the task display name when the task is already created and not completed

RE: How to update the task display name when the task is already created and not completed

Mike Schmitt — Mon, 29 Apr 2024 19:56:58 GMT

[quote userid="2401" url="~/discussions/f/process/30917/how-to-update-the-task-display-name-when-the-task-is-already-created-and-not-completed/134460"]"Portal", don't ask don't tell[/quote]

(and count yourselves all the luckier for it...)

RE: How to update the task display name when the task is already created and not completed

Chris — Mon, 29 Apr 2024 19:49:39 GMT

[quote userid="50400" url="~/discussions/f/process/30917/how-to-update-the-task-display-name-when-the-task-is-already-created-and-not-completed/134459"]Were you able to discern anything that its being selected / unselected actually changes?[/quote]

I can't say I've seen any effects from this setting either way since those Portal days years ago, my gut says this is a leftover setting from that time and might/could be removed when Portal is officially removed from the product (it is still deprecated currently AFAIK? We just removed access to our Portal area recently). When I'm reviewing applications, I don't even check for this setting any more..

I also can't say that I've had any cases where I would not want the values in the interface updated automatically to match the process variables, so I'm not concerned with it from that point.. Any case where I would need to see an older value would be handled differently anyway.

For members here who aren't familiar with the singular version of "Portal", don't ask don't tell ;)

RE: How to update the task display name when the task is already created and not completed

Mike Schmitt — Mon, 29 Apr 2024 19:37:11 GMT

[quote userid="2401" url="~/discussions/f/process/30917/how-to-update-the-task-display-name-when-the-task-is-already-created-and-not-completed/134458"]but direct PVs now, shows the same result[/quote]

This one at least seems like expected behavior. I am (at least slightly) surprised that it's happening with your declared ACPs, however. OK, i guess not THAT surprised. But it makes me wonder whether that setting even has any remaining material effect? Were you able to discern anything that its being selected / unselected actually changes?

RE: How to update the task display name when the task is already created and not completed

Chris — Mon, 29 Apr 2024 19:34:10 GMT

[quote userid="50400" url="~/discussions/f/process/30917/how-to-update-the-task-display-name-when-the-task-is-already-created-and-not-completed/134457"]You didn't show how the value is being passed into the interface - is it being passed into an ACP then into the form, or straight through to the form as a directly-referenced PV? I assume these two will have potentially different behaviors keying off of the "refresh on re-open" setting. PV values I'd expect to always reflect the latest ones; ACPs I would expect (hope?) to retain their original task-instance value UNLESS that option is checked.[/quote]

Definitely a good point to check for differences there. Per the initial test above however, they are passed as ACPs:

Changing to PVs for the re-test:

Testing with the same method as above, but direct PVs now, shows the same result. Values on the interface are refreshed in the UI, without restarting the task, and without the "Refresh.." execution option selected..

Just to note, I'm running this test on my 23.3 environment.

RE: How to update the task display name when the task is already created and not completed

Mike Schmitt — Mon, 29 Apr 2024 19:18:05 GMT

[quote userid="2401" url="~/discussions/f/process/30917/how-to-update-the-task-display-name-when-the-task-is-already-created-and-not-completed/134455"]start this separate script task which updates all 1 values to 2 in the pv's:[/quote]

You didn't show how the value is being passed into the interface - is it being passed into an ACP then into the form, or straight through to the form as a directly-referenced PV? I assume these two will have potentially different behaviors keying off of the "refresh on re-open" setting. PV values I'd expect to always reflect the latest ones; ACPs I would expect (hope?) to retain their original task-instance value UNLESS that option is checked.

RE: How to update the task display name when the task is already created and not completed

Chris — Mon, 29 Apr 2024 18:11:57 GMT

To complicate this even further - I'm wondering if this setting is a leftover from the old "Portal" form days (*shudder*).. As recently, I routinely see input values being refreshed without this setting selected.. Current Documentation. Lets run another test..

Simple interface with a CDT and a Number input:

Refresh not checked:

Process started for debugging, task shows the initial values:

I then start this separate script task which updates all 1 values to 2 in the pv's:

Task is NOT restarted, but when it is reloaded on the front end, all values are all updated anyway:

RE: How to update the task display name when the task is already created and not completed

Mike Schmitt — Mon, 29 Apr 2024 17:34:39 GMT

Thanks, that matches my expectations (though, it woulda been nice...)

RE: How to update the task display name when the task is already created and not completed

Chris — Mon, 29 Apr 2024 17:25:32 GMT

[quote userid="50400" url="~/discussions/f/process/30917/how-to-update-the-task-display-name-when-the-task-is-already-created-and-not-completed/134351"]I'd love to hear whether someone tests this to see whether or not it affects the rendered task display name - I'd guess no, but i'm actually not completely sure.[/quote]

I can confirm this setting does not update the task name, restarting the task is the only way to re-evaluate the task name. Running a test to confirm:

pv!num set to 1, process started for debugging.

pv!num updated to 2, task name still references #1:

RE: How to update the task display name when the task is already created and not completed

Mike Schmitt — Fri, 26 Apr 2024 13:00:45 GMT

I'd love to hear whether someone tests this to see whether or not it affects the rendered task display name - I'd guess no, but i'm actually not completely sure.

RE: How to update the task display name when the task is already created and not completed

Harsh Kumar Agarwal — Fri, 26 Apr 2024 07:59:25 GMT

AFAIK what Mike already suggested is the only way but you can also give it a try to use "Refresh default values every time the task form is viewed" property of UIT.

RE: How to update the task display name when the task is already created and not completed

Chris — Thu, 25 Apr 2024 17:44:21 GMT

[quote userid="21489" url="~/discussions/f/process/30917/how-to-update-the-task-display-name-when-the-task-is-already-created-and-not-completed/134280"]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...[/quote]

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.

RE: How to update the task display name when the task is already created and not completed

Zach Goldsby — Thu, 25 Apr 2024 15:53:12 GMT

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...

RE: How to update the task display name when the task is already created and not completed

Jansi J — Fri, 15 Dec 2023 05:50:09 GMT

Hi Mike, thanks for your response.

Here the task will be assigned to user like approval task ,so the approver can just open the task n-number of times and he can just view and close it.

When he wish to approve/reject, he will do that, until then it will be in same approvers task list.

Yes I agree with you Mike, showing some 'refresh' button or link will work. But without configuring this, if it automatically works without user interaction, then it suits the best with my requirement.

RE: How to update the task display name when the task is already created and not completed

Mike Schmitt — Thu, 14 Dec 2023 19:07:23 GMT

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.