Re: SUPPORT FOR DECLARATIVE TRANSITION CONSTRAINTS

From: Brian <brian_at_selzer-software.com>
Date: Sun, 19 Sep 2010 18:14:19 -0700 (PDT)
Message-ID: <0836e828-6c22-4728-9d9a-aa24068821a6_at_t3g2000vbb.googlegroups.com>



On Sep 19, 6:25 pm, paul c <toledobythe..._at_oohay.ac> wrote:
> On 18/09/2010 6:42 PM, Brian wrote:
> ...
>
> > Transition constraint #4:
> >    LBRDATE can't be different.
>
> >    Business rule implemented:
> >    - The date that a labor activity was performed does not change.
> > ...
>
> What can this possibly mean?  eg. different from what?  change from what?

This constraint is a firewall to protect supervisors from making stupid mistakes. The only way LBRDATE can be wrong is if the supervisor--not the employee--inserted an activity with the wrong date. Employees key information into barcode data collection terminals, and LBRDATE is set to the date the employee's shift started by the application that polls the terminals. Since the employee actually performed a labor activity on that date, it doesn't make sense for the supervisor to claim that it was performed on a different date. It does make sense for them to be able to fix their own screwups,  however. If they insert a labor activity with the wrong date, they have to delete it and insert another one. Received on Sun Sep 19 2010 - 20:14:19 CDT

Original text of this message