Hello,

One thing I've run into a few times is a situation in which some field I'm using to try and rename a document in the repository contains an (unexpected) illegal character. For example, someone copied and pasted values onto a form submission which brought in tab characters and threw a wrench in everything, or in another instance an external application query returned a value that included a bullet point with a tab.

Storing these as string values in entry or form fields is no problem and the fields handle them just fine, however, it causes massive headaches for entry renaming. As I came across these different characters, I continually added new token formatting and such to strip out the illegal characters and prevent them from terminating my workflow.

However, it recently got me thinking it would be great if we could just tell the renaming activity (optionally) to force-sanitize the name.

For example, include a checkbox that will allow Workflow automatically strip out any illegal characters to "sanitize" the value, possibly with a drop down to give it a replacement option such as a space, dash, or underscore.

Instead of terminating, it could then just report a warning to let us know that it had to strip out characters, but it would still use the "valid" portion of the name to rename the document without disrupting the workflow altogether.

I know we can clean up the names on our side with the token editing and such, but I think it would be a huge time saver if I could just tell Workflow to "force" the change instead of having to check for every potentially invalid characters whenever renaming activities are used in critical workflows.