www.skelta.com
Home      Members   Calendar   Who's On

Welcome Guest ( Login | Register )
      

Home » Skelta Workflow Net » Skelta Workflow Net » Workflow Execution » Problem with TimerTriggerAction culture


Problem with TimerTriggerAction cultureExpand / Collapse
Author
Message
Posted Monday, January 15, 2007
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: Skelta Workflow/BPM Net
Last Login: Thursday, February 01, 2007
Posts: 3, Visits: 15

I’ve been using the TimerTriggerAction control in a windows server in English into a web application with culture in Italian: the database user that I use has Italian language, my web application has this globalization setting in Web.config

<globalization requestEncoding="utf-8"

               responseEncoding="utf-8"

               culture="IT-it"

   uiCulture="IT-it"/>

and in Web.Config of SkeltaWebService I’ve been setting the same configuration too. 

When I’ve deployed my flow the control doesn’t work at all.  It seems that when it writes the estimated trigger time into the server (1 second in this case) the date is written in a format and read in another format which makes the control go into tilt; in consequence the action stays in a sleeping state forever.  In fact if I try the application on 12 Jan 2007 the action stays in a sleeping state, but if I try today (15 Jan 2007) the control works good.

Is this a bug or is it just a setting that I have to change?

Thanks

Post #72
Posted Monday, January 15, 2007
Supreme Being

Supreme BeingSupreme BeingSupreme BeingSupreme BeingSupreme BeingSupreme BeingSupreme BeingSupreme Being

Group: Forum Members
Last Login: Friday, February 22, 2008
Posts: 25, Visits: 61
Hi Serena,

Apart from specifying the UICulture in WebConfig file of ypur application,

You need to create a specific folder for the Italian culture under the application folder. Create the IT-it folder in the path shown below –

C:\Program Files\Skelta\Workflow.NET\WorkflowElements\Default\IT-it

Note: This path is only indicative and it corresponds to the default application folder of Skelta Workflow.NET. The path to this application folder needs to be specified in the <sourceelements></sourceelements> tag of the WorkflowNET.Config file for both the application and workflow. The IT-it folder can be created anywhere (e.g., C:\<application folder>\IT-it), provided the corresponding application folder path, i.e., C:\<application folder>, is specified in the <sourceelements> tag

Also attached the document for your reference.

 

Moderator

  Post Attachments 
Localizing Skelta Workflow NET.doc (92 views, 28.00 KB)

Post #73
Posted Thursday, February 01, 2007
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: Skelta Workflow/BPM Net
Last Login: Thursday, February 01, 2007
Posts: 3, Visits: 15
Hi Skelta02,

I've waited the 1st of February to retry the TimerTriggerAction: in fact it didn't work with dates that can be transposed (eg. 01/02/2007 - 02/01/2007).

The instruction that I found in the attachment works: I've no more problem with culture.

Thanks,

Serena. 

Post #74
« Prev Topic | Next Topic »


Reading This TopicExpand / Collapse
-
Active Users: 1 (1 guest, 0 members, 0 anonymous members)
No members currently viewing this topic.

All times are GMT -5:00, Time now is 1:49am

 
Execution: 0.125.11 queries.Compression Enabled.

Copyright © 2002 - 2007 Skelta Software. All rights reserved. Tel: 1 (703) 229-6732 | Email:sales@skelta.com
Skelta - A BPM Workflow Software Company