Skip to content

Validation for BOProps #42

@jeff2001

Description

@jeff2001

Redmine Bug #1577

I have frequently run into this problem
See Bug #1576 In Talbot Lims
If edit a sample whose expiry date was valid but is now not valid get error

What is essentially happening here is that there is a rule
ExpiryDate > Today.
This is cool and important if you are changing Expiry date i.e if expiry date is actually edited but is not relevant to viewing historical data.

What we need to do is have some control over these rules.
e.g. apply only to new objects, apply to edited objects, apply regardless of state of the object?

brett

Updated by Brett Powell almost 3 years ago
I have worked around this in LIMS by adding a custom BO Rule (I...).
This works but is a bit bitchy mainly because testability now does not generate valid values?
AARG.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions