Is Operative transformation should consider a null end date as a time in the future

Matthew Clark 12 years ago updated by anonymous 9 years ago 6

The is operative transformation functions well when a start and end date are specified. However, if the end date is not specified, as is common in many systems with position information, an employee with a start date in the past is considered not operative. The transformation should be updated to consider a null end date DateTime.MaxValue or equivalent.

If this is common in a lot of systems, which ones? Will our clients be expecting the current behaviour. It seems odd that it hasn't been raised as an issue prior to now.


This functionality was added to the IsOperative.Inclusive transformation IDBXT306:Is Operative transformation. This should be incorporated into the one transformation and controlled via a check box on the UI.

The extended functionality of the transformation had resolved this issue, as well as adding local time handling (which needed to be corrected) and an inclusive check. The transformation has been extended and tested with these changes. Resolved for confirmation on next regression test.

Reopening. There is a unit test testing specifically that the end date missing means the entity is not operative. While the extended IsOperative removes this functionality, I'll add it as an option to the transformation

Readded the old behaviour as an option. By default, the Is Operative will consider a null end date valid, but this can be changed on the UI. Resolved.

This was fixed in the alpha. Issue closed.