[jira] Created: (OFBIZ-1661) Improve usability of Reporting Structure Screen

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
9 messages Options
Reply | Threaded
Open this post in threaded view
|

[jira] Created: (OFBIZ-1661) Improve usability of Reporting Structure Screen

Nicolas Malin (Jira)
Improve usability of Reporting Structure Screen
-----------------------------------------------

                 Key: OFBIZ-1661
                 URL: https://issues.apache.org/jira/browse/OFBIZ-1661
             Project: OFBiz
          Issue Type: Improvement
          Components: humanres
            Reporter: Anil K Patel
            Priority: Minor


The list should show data in two lists,
1) List of positions this position reports to.
2) List of positions this position manages.

Add a constraint that a record can have value in one of the two fields.

A position cannot report to and manage same position during a point in time.

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

Reply | Threaded
Open this post in threaded view
|

[jira] Commented: (OFBIZ-1661) Improve usability of Reporting Structure Screen

Nicolas Malin (Jira)

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

Mridul Pathak commented on OFBIZ-1661:
--------------------------------------

In the "EmplPositionReportingStruct" entity, according to the buisiness logic:

1) "emplPositionIdManagedBy (field)" reports to the "emplPositionIdReportingTo (field)"  or we can say the "emplPositionIdReportingTo (field)"  manages the "emplPositionIdManagedBy (field)".
2) "primaryFlag (field)" determines if emplPosition under "emplPositionIdReportingTo (field)" is the primary manger of "emplPositionIdManagedBy (field)" or not.  In this way it is possible to identiry to which position any position will ultimately report.
3) "fromDate" and "thruDate" determines the validity of a Reporting Structure.

> Improve usability of Reporting Structure Screen
> -----------------------------------------------
>
>                 Key: OFBIZ-1661
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-1661
>             Project: OFBiz
>          Issue Type: Improvement
>          Components: humanres
>            Reporter: Anil K Patel
>            Priority: Minor
>
> The list should show data in two lists,
> 1) List of positions this position reports to.
> 2) List of positions this position manages.
> Add a constraint that a record can have value in one of the two fields.
> A position cannot report to and manage same position during a point in time.

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

Reply | Threaded
Open this post in threaded view
|

[jira] Commented: (OFBIZ-1661) Improve usability of Reporting Structure Screen

Nicolas Malin (Jira)
In reply to this post by Nicolas Malin (Jira)

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

Mridul Pathak commented on OFBIZ-1661:
--------------------------------------

Here is how the screen can go for Reporting Structure:

1) emplPositionId will be passed in the query string to this screen.
2) Show the list of positions (emplPositionIdReportingTo) this emplPositionId (emplPositionIdManagedBy) reports to, i.e. find all valid records in "EmplPositionReportingStruct" where emplPositionIdManagedBy = parameters.emplPositionId.
3) Add form which enables user to add a position (emplPositionIdReportingTo) to which parameters.emplPositionId (emplPositionIdManagedBy) reports to.  emplPositionIdManagedBy = parameters.emplPositionId (hidden).
4) Show the list of positions (emplPositionIdManagedBy) which reports to this emplPositionId (emplPositionIdReportingTo), i.e. find all valid records in "EmplPositionReportingStruct" where emplPositionIdReportingTo = parameters.emplPositionId.
5) Add form which enables user to add a position (emplPositionIdManagedBy) which will report to the parameters.emplPositionId (emplPositionIdReportingTo).  emplPositionIdReportingTo = parameters.emplPositionId (hidden).

> Improve usability of Reporting Structure Screen
> -----------------------------------------------
>
>                 Key: OFBIZ-1661
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-1661
>             Project: OFBiz
>          Issue Type: Improvement
>          Components: humanres
>            Reporter: Anil K Patel
>            Priority: Minor
>
> The list should show data in two lists,
> 1) List of positions this position reports to.
> 2) List of positions this position manages.
> Add a constraint that a record can have value in one of the two fields.
> A position cannot report to and manage same position during a point in time.

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

Reply | Threaded
Open this post in threaded view
|

[jira] Commented: (OFBIZ-1661) Improve usability of Reporting Structure Screen

Nicolas Malin (Jira)
In reply to this post by Nicolas Malin (Jira)

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

Mridul Pathak commented on OFBIZ-1661:
--------------------------------------

Improve "createEmplPositionReportingStruct" service to check for the codintion that emplPositionIdReportingTo must not be equal to emplPositionIdManagedBy.  If this condition fails return error.

> Improve usability of Reporting Structure Screen
> -----------------------------------------------
>
>                 Key: OFBIZ-1661
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-1661
>             Project: OFBiz
>          Issue Type: Improvement
>          Components: humanres
>            Reporter: Anil K Patel
>            Priority: Minor
>
> The list should show data in two lists,
> 1) List of positions this position reports to.
> 2) List of positions this position manages.
> Add a constraint that a record can have value in one of the two fields.
> A position cannot report to and manage same position during a point in time.

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

Reply | Threaded
Open this post in threaded view
|

[jira] Issue Comment Edited: (OFBIZ-1661) Improve usability of Reporting Structure Screen

Nicolas Malin (Jira)
In reply to this post by Nicolas Malin (Jira)

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

mridul.pathak edited comment on OFBIZ-1661 at 3/16/08 11:17 PM:
----------------------------------------------------------------

In the "EmplPositionReportingStruct" entity, according to the buisiness logic:

1) "emplPositionIdManagedBy (field)" reports to the "emplPositionIdReportingTo (field)"  or we can say the "emplPositionIdReportingTo (field)"  manages the "emplPositionIdManagedBy (field)".
2) "primaryFlag (field)" determines if emplPosition under "emplPositionIdReportingTo (field)" is the primary manger of "emplPositionIdManagedBy (field)" or not.  In this way it is possible to identify to which position any position will ultimately report.
3) "fromDate" and "thruDate" determines the validity of a Reporting Structure.

      was (Author: mridul.pathak):
    In the "EmplPositionReportingStruct" entity, according to the buisiness logic:

1) "emplPositionIdManagedBy (field)" reports to the "emplPositionIdReportingTo (field)"  or we can say the "emplPositionIdReportingTo (field)"  manages the "emplPositionIdManagedBy (field)".
2) "primaryFlag (field)" determines if emplPosition under "emplPositionIdReportingTo (field)" is the primary manger of "emplPositionIdManagedBy (field)" or not.  In this way it is possible to identiry to which position any position will ultimately report.
3) "fromDate" and "thruDate" determines the validity of a Reporting Structure.
 

> Improve usability of Reporting Structure Screen
> -----------------------------------------------
>
>                 Key: OFBIZ-1661
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-1661
>             Project: OFBiz
>          Issue Type: Improvement
>          Components: humanres
>            Reporter: Anil K Patel
>            Priority: Minor
>
> The list should show data in two lists,
> 1) List of positions this position reports to.
> 2) List of positions this position manages.
> Add a constraint that a record can have value in one of the two fields.
> A position cannot report to and manage same position during a point in time.

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

Reply | Threaded
Open this post in threaded view
|

[jira] Assigned: (OFBIZ-1661) Improve usability of Reporting Structure Screen

Nicolas Malin (Jira)
In reply to this post by Nicolas Malin (Jira)

     [ https://issues.apache.org/jira/browse/OFBIZ-1661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Anil K Patel reassigned OFBIZ-1661:
-----------------------------------

    Assignee: Anil K Patel

> Improve usability of Reporting Structure Screen
> -----------------------------------------------
>
>                 Key: OFBIZ-1661
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-1661
>             Project: OFBiz
>          Issue Type: Improvement
>          Components: humanres
>            Reporter: Anil K Patel
>            Assignee: Anil K Patel
>            Priority: Minor
>
> The list should show data in two lists,
> 1) List of positions this position reports to.
> 2) List of positions this position manages.
> Add a constraint that a record can have value in one of the two fields.
> A position cannot report to and manage same position during a point in time.

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

Reply | Threaded
Open this post in threaded view
|

[jira] Updated: (OFBIZ-1661) Improve usability of Reporting Structure Screen

Nicolas Malin (Jira)
In reply to this post by Nicolas Malin (Jira)

     [ https://issues.apache.org/jira/browse/OFBIZ-1661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Santosh Malviya updated OFBIZ-1661:
-----------------------------------

    Attachment: ReportingSttucture.patch

Hello,
Patch is uploaded for the issue, thanks Mridul Pathak to discuss the issue.

> Improve usability of Reporting Structure Screen
> -----------------------------------------------
>
>                 Key: OFBIZ-1661
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-1661
>             Project: OFBiz
>          Issue Type: Improvement
>          Components: humanres
>            Reporter: Anil K Patel
>            Assignee: Anil K Patel
>            Priority: Minor
>         Attachments: ReportingSttucture.patch
>
>
> The list should show data in two lists,
> 1) List of positions this position reports to.
> 2) List of positions this position manages.
> Add a constraint that a record can have value in one of the two fields.
> A position cannot report to and manage same position during a point in time.

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

Reply | Threaded
Open this post in threaded view
|

[jira] Assigned: (OFBIZ-1661) Improve usability of Reporting Structure Screen

Nicolas Malin (Jira)
In reply to this post by Nicolas Malin (Jira)

     [ https://issues.apache.org/jira/browse/OFBIZ-1661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Vikas Mayur reassigned OFBIZ-1661:
----------------------------------

    Assignee: Vikas Mayur  (was: Anil K Patel)

> Improve usability of Reporting Structure Screen
> -----------------------------------------------
>
>                 Key: OFBIZ-1661
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-1661
>             Project: OFBiz
>          Issue Type: Improvement
>          Components: humanres
>            Reporter: Anil K Patel
>            Assignee: Vikas Mayur
>            Priority: Minor
>         Attachments: ReportingSttucture.patch
>
>
> The list should show data in two lists,
> 1) List of positions this position reports to.
> 2) List of positions this position manages.
> Add a constraint that a record can have value in one of the two fields.
> A position cannot report to and manage same position during a point in time.

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

Reply | Threaded
Open this post in threaded view
|

[jira] Closed: (OFBIZ-1661) Improve usability of Reporting Structure Screen

Nicolas Malin (Jira)
In reply to this post by Nicolas Malin (Jira)

     [ https://issues.apache.org/jira/browse/OFBIZ-1661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Vikas Mayur closed OFBIZ-1661.
------------------------------

    Resolution: Fixed

Thanks Santosh,

Your patch is trunk rev.654569 with little modifications done using <screenlet> widget in place of <container> tag

> Improve usability of Reporting Structure Screen
> -----------------------------------------------
>
>                 Key: OFBIZ-1661
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-1661
>             Project: OFBiz
>          Issue Type: Improvement
>          Components: humanres
>            Reporter: Anil K Patel
>            Assignee: Vikas Mayur
>            Priority: Minor
>         Attachments: ReportingSttucture.patch
>
>
> The list should show data in two lists,
> 1) List of positions this position reports to.
> 2) List of positions this position manages.
> Add a constraint that a record can have value in one of the two fields.
> A position cannot report to and manage same position during a point in time.

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