Renaming existing Tasks

Is this a one-time thing? Or do you want the ability to rename tasks at will?

@redae Added to the above, where would you like to carry out the update? To the Appian Task or the Appian Task plus a column in the DB table that maintains Tasks information?

Actually we try to rename tasks in batch. it's an exception right now but these kind of typo can happen in the future. Having the ability to refactor or rename will be great.

@sikhivahans : just the Appian Tasks. Displayed task name to user matter the most

Not aware of any other approach other than using the 'Set Task Display Name' Shared Component at http://bit.ly/2eqSwTr. So ideally you should be getting the required tasks(or get the required tasks from the process id and task name by using any of the plugins available in the Forum) in the first place and then trigger a process for each task that derives the latest name to be used based on business conditions and then set the name of the task by using the plugin at http://bit.ly/2eqSwTr.

As I am neither sure about the number of tasks you would want to reset nor the complexity of the expression that drives the desired task name, I would suggest basic measures such as batch processing, execution engine balancing etc to be taken care of.

In case if the expression to derive the task name for each task is too simple, maybe, you can even skip the MNI by using the parallel flows as mentioned at http://bit.ly/2dkN7QI which will keep the process much more simple.

Thanks @sikhivahans for your feedback. I didn't know about this specific shared components

@redae No worries. Another suggestion I would like to make is, if possible, try to refrain from using the changeable data(for instance, the data from integration) in process or task names as this needs a batch process or similar sort of mechanism to maintain synch. It might be worth depending on an identifier, or a reference (generated out of identifier and has a common format across the entities) which won't change(when compared to an attribute such as name) and then show the user the other information in the Headers of the Forms/Record Dashboards.

As per my experience, it's a pain and time-consuming to write a process which will maintain a synch as it could potentially end up being over-engineered provided if the complexity(in terms of processing) is too high.

@sikhivahans : good point indeed ! thx