You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ofbiz.apache.org by "David E. Jones (JIRA)" <ji...@apache.org> on 2009/10/21 21:04:59 UTC

[jira] Commented: (OFBIZ-3071) assigning security group to a party without validations

    [ https://issues.apache.org/jira/browse/OFBIZ-3071?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12768372#action_12768372 ] 

David E. Jones commented on OFBIZ-3071:
---------------------------------------

There are good reasons sometimes to have records with overlapping dates. The pattern generally used (hopefully always used!) for finding a unique record is to filter out all records where the current date is outside the record's date range, and also sort by the fromDate (most recent, ie highest, first).

There are some nice things you can do with that, like setting up a temporary override that will become active with the fromDate comes up and will automatically revert to the previous record once the thruDate is crossed.

> assigning security group to a party without validations
> -------------------------------------------------------
>
>                 Key: OFBIZ-3071
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-3071
>             Project: OFBiz
>          Issue Type: Bug
>            Reporter: Abdullah Shaikh
>            Priority: Minor
>         Attachments: OFBIZ-3071_assigning security group to a party without validations.patch
>
>
> When adding user login to Security Group, the fromDate & thruDate input fields are not mandatory, if not specified the fromDate is set to current timestamop and thruDate is entered in database as null, which means the user login is assigned that Security Group forever, but when if the same Security Group is added, it again adds it, but instead it should check that if the thruDate is null in the already entered record then shouldn't add new record.
> If incase the thruDate is specified during the creation of 1st record then while adding the 2nd record for the same Security Group, it should check if the thruDate of previous record is before the fromDate of the new record, this check also doesn't happen.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.