Skip to main content

Hi all,


today I move a K2 Workflow project from a vm to another vm. With my bitter disappointment I get the following error (see also the picture) when I try to open the process in the designer:


"String was not recognized as a valid DateTime"


see the picture here: http://picasaweb.google.com/lh/photo/6ns0xv5ErIx3ukIL8cxeRw?feat=directlink


After a long investigation, I find out that the user account on the new vm has "regional and Language Options" set on US Culture, instead the the account's user developed the workflow has this setting on IT culture. I have two questions about this behavior:



  • If I develop with a user with a culture A, and then I deploy my workflow project on my staging or production environment with another user having culture B, can I come upon this issue?
  • There is a best practice to follow related the account culture setting of user developer of the workflow?

Thanks in advance


 


 

It seems you are getting theses error in the dev environment, but I could tell that you may face theses issue in runtime environment as well :(

I did observe some design flaws in the APIs due to passing values as string (take a look at SmartObject properties...) with unmanageable culture between the host process and your application.

Say your application is using a culture like "sl-SL" and your k2 host is "en-US", passing a datetime (to string ...) as a property value in a smart object would throw for the same reason.

Take a look at this thread:

http://www.k2underground.com/forums/thread/26032.aspx 

I think we may ask for some renovation in the API on this side (did you see  SourceCode.Workflow.Client.ProcessInstance.Status1 that is "pretty fun")

HTH 

Reply


View our Community Site Map

Nintex Community Sitemap
Terms & ConditionsCookie settings