Whenever inline functions just render their content usually it's because an error occured within them. Instead of showing an error message they're just show themselves as text.

You could try the following. Create a "convert value" action for both of your dates and add the Culture into it:

Doing this with both dates and adding the same culture should bring the date into the same date format and should make them comparable. If it doesn't work with the russian culture info maybe it helps to bring both dates into US format.

Best regards

Enrico

Hi Enrico! Thank you for reply

I tried to add Convert value action.

When I run workflow under account with English LCID, both dates are converted to en-us culture and compared as expected:

The same thing under user with Russian LCID, both dates are converted to ru-ru culture (as i specified in action configuration) and all's good:

However, when workflow trying to convert date to culture that different from initiator's regional setting, it gives me an error, both with russian and english LCID.

Trying to convert to en-us culture under initiator with russian locale:

Error parsing value. Value '13.10.1988 0:00' is not compatible with the selected output variable type Date Time.

Trying to convert to ru-ru culture under initiator with english locale:

Error parsing value. Value '10/13/1988 12:00 AM' is not compatible with the selected output variable type Date Time.

So, I don't have a unified culture to convert to..

Am i need to specify Date format while converting?

I tried to do something like that:

and got SQL date converted to ru-ru culture:

Now I see the only workaround is to "Run as workflow owner" when owner is account with permanent regional settings, but it's not a solution )

Hmm, a tricky one.

Date Format won't help you here. All it does is to check the format you enter in Date Format and check if your date matches the given format. If it's not it won't be recognized.

If you use Run as workflow owner just for the converting / comparison actions, wouldn't that solve the problem? All other actions could run as initiator.

You could also try to create a User defined action that does all the conversion and if needed have it run in workflow owners context. It could send the result of the comparison back to your workflow that afterwards keeps running with normal initiators context. Would that be an option?

Otherwise I only could think of using any kind of PowerShell action or a web service to do the locale conversion and compare the dates.

Best regards

Enrico

Heh, I don't want to reopen all my workflows to check this checkbox "run as owner" ) And I will need to republish all workflows under isolated account, where no-one couldn't change regional settings..

And I still can't understand, is it bug or expected behaviour..?

If it is a bug, maybe better to contact Nintex Support, how you think?

Agreed. They might have faced this issue before and maybe able to help in this.

If they get back with something helpful, you could update this thread to let others know there is a solution.

FYI, Nintex Support confirmed that they are reproduced the issue, so this is a bug, not feature )

I'm waiting for resolution from support and will give feedback to this thread later.

I received a reply from Support Team that currently the functionality of "fn-FormatDate" will only work with the default setting of "My Language And Region > Always follow web settings" is being checked.
Therefore, the user business requirement to uncheck this setting will not be supported and categorized as a feature request.

Probably, I will leave a feature request at User Voice. For now, this topic can be closed as unresolved )