V9 SR 2 Date Time Field Criteria

Hi,

I am trying put in a criteria for the "Earliest" property in date time field. The condition didn't resolve the date, so I calculated the date in another field, and assigned that field to the earliest condition. However, here is the problem, this seems to work fine for the first folder I open, subsequent folders resolve this to "Never" Date, which displays as

"Dec 9999". I am displaying the calculated field and it displays a perfect date, so I don't know where is the problem.

Earliest condition works fine for "ProcessContext.CurrentTime" fields but for the date I calculate.

Anybody experience this?

Thanks for your help!!

Find more posts tagged with

BPM

Comments

Paul Lawrence

How are you calculating your date? I believe that a system date is not necessarily compatible with a Metastorm date.

Saritha_Somasundaram

The assignment is

DateTimeField = CalculateDateTime(NBRFollowUpCriteria1.GreaterThanInception, DateTimeUnits.Days, DateTimeDirection.After, DateTime.CurrentDate)

I am displaying this calculated date time field in another date field on the same form, that comes out perfectly fine, so I don't know why it doesn't work in the earliest condition.

Jerome_Pearce

We have had some very similar situations, mainly to do with calculated values in the earliest and lasted peroperties of date fields. We have no idea what the Dec 9999 was we came across it a few times and were really baffled.

We thought it was something to do withtime zones in our particular installation, as we have had some serious problems with calculated date values and time zone adjustments, but we are not sure.

Jerome_Pearce

ssomasundaram wrote:

The assignment is

DateTimeField = CalculateDateTime(NBRFollowUpCriteria1.GreaterThanInception, DateTimeUnits.Days, DateTimeDirection.After, DateTime.CurrentDate)

I am displaying this calculated date time field in another date field on the same form, that comes out perfectly fine, so I don't know why it doesn't work in the earliest condition.

Try using ProcessContext.CurrentTime rather than DateTime.CurrentDate perhaps?

Is Metastorm.Runtime.Types.DateTime.CurrentDate documented or supported, does anyone know? Also Metastorm.Runtime.Types.DateTime.Never?

Saritha_Somasundaram

Hi Jerome,

Thanks for the response, will try that.

But here is the thing, I thought the calculated field on form load might be an issue. But the variable is assigned a calculated value before this form even loads and it displays perfectly fine in the same form, however the wonderful "DateTime" Earliest criteria recongizes it one time and then resolves to NEVER(). This is soo unpredictable. Thanks for your help!

I have an open ticket with our helpdesk, if I hear anything I will keep you all posted.