[jira] Commented: (OFBIZ-2205) Implemented recruitment in HR module
[ https://issues.apache.org/jira/browse/OFBIZ-2205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12711488#action_12711488 ] Abhinav Vaid commented on OFBIZ-2205: - Hi Ashish, Thanks for reviewing and commiting our work. I would like to thank Anil Soni, Srikanth Jagannadhula and Simranjeet Singh for their tremendous support and review. Regards Abhinav Vaid iLabs, L T Infotech Ltd. Mumbai. Implemented recruitment in HR module Key: OFBIZ-2205 URL: https://issues.apache.org/jira/browse/OFBIZ-2205 Project: OFBiz Issue Type: New Feature Components: humanres Affects Versions: SVN trunk Environment: Windows XP Professional (5.1, Build 2600) Service Pack 2, Intel(R) Core(TM)2 CPU 4300 @ 1.80GHz (2 CPUs), 1014MB RAM, jdk1.5.0, apache-ant-1.7.0 Reporter: Abhinav Vaid Assignee: Ashish Vijaywargiya Priority: Minor Fix For: SVN trunk Attachments: HR_Recruitment.patch, HR_Recruitment.patch, HR_Recruitment.patch, HR_Recruitment.patch, HR_Recruitment.patch, HR_Recruitment.patch, HR_Recruitment.patch In this patch we have included recruitment in the HR module. Recruitment performs tasks such as admin can create new job requisitions. He can update or delete new job requisitions. Now once the job requisition has been added, it is visible to all the employees. Then if interested employee wants to apply for the job requisition he sends it for approval to his superior. Superior from his login can check who all have applied for job requisition. He can update the status and same is reflected at employee's end. Here admin can also create new interview types and he can store the information of the diffrent interviews of employees. We have created Security groups: HUMANRES_APPROVER HUMANRES_EMPLOYEE We have created Security permissions: HUMANRES_APPROVE We have created Login Id's : demoadmin belongs to FULLADMIN security group demoapprover belongs to HUMANRES_APPROVER security group demoemployee belongs to HUMANRES_EMPLOYEE security group -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (OFBIZ-2205) Implemented recruitment in HR module
[ https://issues.apache.org/jira/browse/OFBIZ-2205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12711461#action_12711461 ] Abhinav Vaid commented on OFBIZ-2205: - Hi Ashish We have not seen any response from your side since long time. Hope to hear from you soon. Regards Abhinav Vaid iLabs, L T Infotech Ltd. Mumbai. Implemented recruitment in HR module Key: OFBIZ-2205 URL: https://issues.apache.org/jira/browse/OFBIZ-2205 Project: OFBiz Issue Type: New Feature Components: humanres Affects Versions: SVN trunk Environment: Windows XP Professional (5.1, Build 2600) Service Pack 2, Intel(R) Core(TM)2 CPU 4300 @ 1.80GHz (2 CPUs), 1014MB RAM, jdk1.5.0, apache-ant-1.7.0 Reporter: Abhinav Vaid Assignee: Ashish Vijaywargiya Priority: Minor Fix For: SVN trunk Attachments: HR_Recruitment.patch, HR_Recruitment.patch, HR_Recruitment.patch, HR_Recruitment.patch, HR_Recruitment.patch, HR_Recruitment.patch, HR_Recruitment.patch In this patch we have included recruitment in the HR module. Recruitment performs tasks such as admin can create new job requisitions. He can update or delete new job requisitions. Now once the job requisition has been added, it is visible to all the employees. Then if interested employee wants to apply for the job requisition he sends it for approval to his superior. Superior from his login can check who all have applied for job requisition. He can update the status and same is reflected at employee's end. Here admin can also create new interview types and he can store the information of the diffrent interviews of employees. We have created Security groups: HUMANRES_APPROVER HUMANRES_EMPLOYEE We have created Security permissions: HUMANRES_APPROVE We have created Login Id's : demoadmin belongs to FULLADMIN security group demoapprover belongs to HUMANRES_APPROVER security group demoemployee belongs to HUMANRES_EMPLOYEE security group -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (OFBIZ-2205) Implemented recruitment in HR module
[ https://issues.apache.org/jira/browse/OFBIZ-2205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12709283#action_12709283 ] Simranjeet Singh commented on OFBIZ-2205: - Hello Aswath Thanks for your keen interest in our patch. Here is the answer to your query. HUMANRES_APPROVER security group contains HUMANRES_APPROVE permission. We have given this permission in menu item named Approval. Any person who belongs to the security group HUMANRES_APPROVER will be able to see this tab on the screen. Thats why we have created this permission. Thanks Regards Abhinav Vaid iLabs, L T Infotech Ltd. Mumbai. Implemented recruitment in HR module Key: OFBIZ-2205 URL: https://issues.apache.org/jira/browse/OFBIZ-2205 Project: OFBiz Issue Type: New Feature Components: humanres Affects Versions: SVN trunk Environment: Windows XP Professional (5.1, Build 2600) Service Pack 2, Intel(R) Core(TM)2 CPU 4300 @ 1.80GHz (2 CPUs), 1014MB RAM, jdk1.5.0, apache-ant-1.7.0 Reporter: Abhinav Vaid Assignee: Ashish Vijaywargiya Priority: Minor Fix For: SVN trunk Attachments: HR_Recruitment.patch, HR_Recruitment.patch, HR_Recruitment.patch, HR_Recruitment.patch, HR_Recruitment.patch, HR_Recruitment.patch, HR_Recruitment.patch In this patch we have included recruitment in the HR module. Recruitment performs tasks such as admin can create new job requisitions. He can update or delete new job requisitions. Now once the job requisition has been added, it is visible to all the employees. Then if interested employee wants to apply for the job requisition he sends it for approval to his superior. Superior from his login can check who all have applied for job requisition. He can update the status and same is reflected at employee's end. Here admin can also create new interview types and he can store the information of the diffrent interviews of employees. We have created Security groups: HUMANRES_APPROVER HUMANRES_EMPLOYEE We have created Security permissions: HUMANRES_APPROVE We have created Login Id's : demoadmin belongs to FULLADMIN security group demoapprover belongs to HUMANRES_APPROVER security group demoemployee belongs to HUMANRES_EMPLOYEE security group -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (OFBIZ-2205) Implemented recruitment in HR module
[ https://issues.apache.org/jira/browse/OFBIZ-2205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12709286#action_12709286 ] Abhinav Vaid commented on OFBIZ-2205: - Hello Aswath Thanks for your keen interest in our patch. Here is the answer to your query. HUMANRES_APPROVER security group contains HUMANRES_APPROVE permission. We have given this permission in menu item named Approval. Any person who belongs to the security group HUMANRES_APPROVER will be able to see this tab on the screen. Thats why we have created this permission. Thanks Regards Abhinav Vaid iLabs, L T Infotech Ltd. Mumbai. Implemented recruitment in HR module Key: OFBIZ-2205 URL: https://issues.apache.org/jira/browse/OFBIZ-2205 Project: OFBiz Issue Type: New Feature Components: humanres Affects Versions: SVN trunk Environment: Windows XP Professional (5.1, Build 2600) Service Pack 2, Intel(R) Core(TM)2 CPU 4300 @ 1.80GHz (2 CPUs), 1014MB RAM, jdk1.5.0, apache-ant-1.7.0 Reporter: Abhinav Vaid Assignee: Ashish Vijaywargiya Priority: Minor Fix For: SVN trunk Attachments: HR_Recruitment.patch, HR_Recruitment.patch, HR_Recruitment.patch, HR_Recruitment.patch, HR_Recruitment.patch, HR_Recruitment.patch, HR_Recruitment.patch In this patch we have included recruitment in the HR module. Recruitment performs tasks such as admin can create new job requisitions. He can update or delete new job requisitions. Now once the job requisition has been added, it is visible to all the employees. Then if interested employee wants to apply for the job requisition he sends it for approval to his superior. Superior from his login can check who all have applied for job requisition. He can update the status and same is reflected at employee's end. Here admin can also create new interview types and he can store the information of the diffrent interviews of employees. We have created Security groups: HUMANRES_APPROVER HUMANRES_EMPLOYEE We have created Security permissions: HUMANRES_APPROVE We have created Login Id's : demoadmin belongs to FULLADMIN security group demoapprover belongs to HUMANRES_APPROVER security group demoemployee belongs to HUMANRES_EMPLOYEE security group -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (OFBIZ-2205) Implemented recruitment in HR module
[ https://issues.apache.org/jira/browse/OFBIZ-2205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12709389#action_12709389 ] Aswath Satrasala commented on OFBIZ-2205: - Thanks Abhinav. I have no more comments. Implemented recruitment in HR module Key: OFBIZ-2205 URL: https://issues.apache.org/jira/browse/OFBIZ-2205 Project: OFBiz Issue Type: New Feature Components: humanres Affects Versions: SVN trunk Environment: Windows XP Professional (5.1, Build 2600) Service Pack 2, Intel(R) Core(TM)2 CPU 4300 @ 1.80GHz (2 CPUs), 1014MB RAM, jdk1.5.0, apache-ant-1.7.0 Reporter: Abhinav Vaid Assignee: Ashish Vijaywargiya Priority: Minor Fix For: SVN trunk Attachments: HR_Recruitment.patch, HR_Recruitment.patch, HR_Recruitment.patch, HR_Recruitment.patch, HR_Recruitment.patch, HR_Recruitment.patch, HR_Recruitment.patch In this patch we have included recruitment in the HR module. Recruitment performs tasks such as admin can create new job requisitions. He can update or delete new job requisitions. Now once the job requisition has been added, it is visible to all the employees. Then if interested employee wants to apply for the job requisition he sends it for approval to his superior. Superior from his login can check who all have applied for job requisition. He can update the status and same is reflected at employee's end. Here admin can also create new interview types and he can store the information of the diffrent interviews of employees. We have created Security groups: HUMANRES_APPROVER HUMANRES_EMPLOYEE We have created Security permissions: HUMANRES_APPROVE We have created Login Id's : demoadmin belongs to FULLADMIN security group demoapprover belongs to HUMANRES_APPROVER security group demoemployee belongs to HUMANRES_EMPLOYEE security group -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (OFBIZ-2205) Implemented recruitment in HR module
[ https://issues.apache.org/jira/browse/OFBIZ-2205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12708400#action_12708400 ] Aswath Satrasala commented on OFBIZ-2205: - Hello Abhinav, The HUMANRES_APPROVER securty group is create in the demo.xml file. But, I don't see it being used anywhere in other parts of the patch. How is it used and what is its use? Thanks -Aswath Implemented recruitment in HR module Key: OFBIZ-2205 URL: https://issues.apache.org/jira/browse/OFBIZ-2205 Project: OFBiz Issue Type: New Feature Components: humanres Affects Versions: SVN trunk Environment: Windows XP Professional (5.1, Build 2600) Service Pack 2, Intel(R) Core(TM)2 CPU 4300 @ 1.80GHz (2 CPUs), 1014MB RAM, jdk1.5.0, apache-ant-1.7.0 Reporter: Abhinav Vaid Assignee: Ashish Vijaywargiya Priority: Minor Fix For: SVN trunk Attachments: HR_Recruitment.patch, HR_Recruitment.patch, HR_Recruitment.patch, HR_Recruitment.patch, HR_Recruitment.patch, HR_Recruitment.patch, HR_Recruitment.patch In this patch we have included recruitment in the HR module. Recruitment performs tasks such as admin can create new job requisitions. He can update or delete new job requisitions. Now once the job requisition has been added, it is visible to all the employees. Then if interested employee wants to apply for the job requisition he sends it for approval to his superior. Superior from his login can check who all have applied for job requisition. He can update the status and same is reflected at employee's end. Here admin can also create new interview types and he can store the information of the diffrent interviews of employees. We have created Security groups: HUMANRES_APPROVER HUMANRES_EMPLOYEE We have created Security permissions: HUMANRES_APPROVE We have created Login Id's : demoadmin belongs to FULLADMIN security group demoapprover belongs to HUMANRES_APPROVER security group demoemployee belongs to HUMANRES_EMPLOYEE security group -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (OFBIZ-2205) Implemented recruitment in HR module
[ https://issues.apache.org/jira/browse/OFBIZ-2205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12708081#action_12708081 ] Ashish Vijaywargiya commented on OFBIZ-2205: Hello Abhinav, Thanks for the updated patch. Lets see what community members has to say in next few days. Very soon I will pick it and will commit it if everything looks good or close to me. -- Ashish Vijaywargiya Implemented recruitment in HR module Key: OFBIZ-2205 URL: https://issues.apache.org/jira/browse/OFBIZ-2205 Project: OFBiz Issue Type: New Feature Components: humanres Affects Versions: SVN trunk Environment: Windows XP Professional (5.1, Build 2600) Service Pack 2, Intel(R) Core(TM)2 CPU 4300 @ 1.80GHz (2 CPUs), 1014MB RAM, jdk1.5.0, apache-ant-1.7.0 Reporter: Abhinav Vaid Assignee: Ashish Vijaywargiya Priority: Minor Fix For: SVN trunk Attachments: HR_Recruitment.patch, HR_Recruitment.patch, HR_Recruitment.patch, HR_Recruitment.patch, HR_Recruitment.patch, HR_Recruitment.patch, HR_Recruitment.patch In this patch we have included recruitment in the HR module. Recruitment performs tasks such as admin can create new job requisitions. He can update or delete new job requisitions. Now once the job requisition has been added, it is visible to all the employees. Then if interested employee wants to apply for the job requisition he sends it for approval to his superior. Superior from his login can check who all have applied for job requisition. He can update the status and same is reflected at employee's end. Here admin can also create new interview types and he can store the information of the diffrent interviews of employees. We have created Security groups: HUMANRES_APPROVER HUMANRES_EMPLOYEE We have created Security permissions: HUMANRES_APPROVE We have created Login Id's : demoadmin belongs to FULLADMIN security group demoapprover belongs to HUMANRES_APPROVER security group demoemployee belongs to HUMANRES_EMPLOYEE security group -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (OFBIZ-2205) Implemented recruitment in HR module
[ https://issues.apache.org/jira/browse/OFBIZ-2205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12707802#action_12707802 ] Abhinav Vaid commented on OFBIZ-2205: - Hi Jacopo and Ashish, Thanks Jacopo for your thoughts and comments on our patch. We have considered all of your comments and made the changes accordingly. We are uploading the updated patch. We would also like to mention that after having a look at enumeration entity we decided to remove the exam as well as the JobPostingType entities. As the functionality provided by these two entities can be achieved by using Enumeration entity. Here is my comment on your 5th comment dated 27/Apr/09: 5) EmployeeAction: I am not 100% sure about the meaning of this entity but maybe instead of it we could use the EmplPosition and EmplPositionFulfillment entities (I suspect that they model the same exact data) Comment : As per Jacopo's suggestion we have implemented Relocation functionality by using EmplPosition, EmplPositionFulfillment and EmplPositionReportingStruct entities instead of creating an entity EmployeeAction. Thanks Regards Abhinav Vaid iLabs, L T Infotech Ltd. Mumbai. Implemented recruitment in HR module Key: OFBIZ-2205 URL: https://issues.apache.org/jira/browse/OFBIZ-2205 Project: OFBiz Issue Type: New Feature Components: humanres Affects Versions: SVN trunk Environment: Windows XP Professional (5.1, Build 2600) Service Pack 2, Intel(R) Core(TM)2 CPU 4300 @ 1.80GHz (2 CPUs), 1014MB RAM, jdk1.5.0, apache-ant-1.7.0 Reporter: Abhinav Vaid Assignee: Ashish Vijaywargiya Priority: Minor Fix For: SVN trunk Attachments: HR_Recruitment.patch, HR_Recruitment.patch, HR_Recruitment.patch, HR_Recruitment.patch, HR_Recruitment.patch, HR_Recruitment.patch In this patch we have included recruitment in the HR module. Recruitment performs tasks such as admin can create new job requisitions. He can update or delete new job requisitions. Now once the job requisition has been added, it is visible to all the employees. Then if interested employee wants to apply for the job requisition he sends it for approval to his superior. Superior from his login can check who all have applied for job requisition. He can update the status and same is reflected at employee's end. Here admin can also create new interview types and he can store the information of the diffrent interviews of employees. We have created Security groups: HUMANRES_APPROVER HUMANRES_EMPLOYEE We have created Security permissions: HUMANRES_APPROVE We have created Login Id's : demoadmin belongs to FULLADMIN security group demoapprover belongs to HUMANRES_APPROVER security group demoemployee belongs to HUMANRES_EMPLOYEE security group -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (OFBIZ-2205) Implemented recruitment in HR module
[ https://issues.apache.org/jira/browse/OFBIZ-2205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12706869#action_12706869 ] Abhinav Vaid commented on OFBIZ-2205: - Hello Ashish, We are now working on the 5th point related to EmployeeAction entity and fixed other comments as suggested by Jacopo dated 27/Apr/09. We will upload the patch in few days. Thanks Regards Abhinav Vaid iLabs, L T Infotech Ltd. Mumbai. Implemented recruitment in HR module Key: OFBIZ-2205 URL: https://issues.apache.org/jira/browse/OFBIZ-2205 Project: OFBiz Issue Type: New Feature Components: humanres Affects Versions: SVN trunk Environment: Windows XP Professional (5.1, Build 2600) Service Pack 2, Intel(R) Core(TM)2 CPU 4300 @ 1.80GHz (2 CPUs), 1014MB RAM, jdk1.5.0, apache-ant-1.7.0 Reporter: Abhinav Vaid Assignee: Ashish Vijaywargiya Priority: Minor Fix For: SVN trunk Attachments: HR_Recruitment.patch, HR_Recruitment.patch, HR_Recruitment.patch, HR_Recruitment.patch, HR_Recruitment.patch, HR_Recruitment.patch In this patch we have included recruitment in the HR module. Recruitment performs tasks such as admin can create new job requisitions. He can update or delete new job requisitions. Now once the job requisition has been added, it is visible to all the employees. Then if interested employee wants to apply for the job requisition he sends it for approval to his superior. Superior from his login can check who all have applied for job requisition. He can update the status and same is reflected at employee's end. Here admin can also create new interview types and he can store the information of the diffrent interviews of employees. We have created Security groups: HUMANRES_APPROVER HUMANRES_EMPLOYEE We have created Security permissions: HUMANRES_APPROVE We have created Login Id's : demoadmin belongs to FULLADMIN security group demoapprover belongs to HUMANRES_APPROVER security group demoemployee belongs to HUMANRES_EMPLOYEE security group -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (OFBIZ-2205) Implemented recruitment in HR module
[ https://issues.apache.org/jira/browse/OFBIZ-2205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12706913#action_12706913 ] Ashish Vijaywargiya commented on OFBIZ-2205: Sounds good to me. Looking forward to have updated patch from you soon. -- Ashish Vijaywargiya Implemented recruitment in HR module Key: OFBIZ-2205 URL: https://issues.apache.org/jira/browse/OFBIZ-2205 Project: OFBiz Issue Type: New Feature Components: humanres Affects Versions: SVN trunk Environment: Windows XP Professional (5.1, Build 2600) Service Pack 2, Intel(R) Core(TM)2 CPU 4300 @ 1.80GHz (2 CPUs), 1014MB RAM, jdk1.5.0, apache-ant-1.7.0 Reporter: Abhinav Vaid Assignee: Ashish Vijaywargiya Priority: Minor Fix For: SVN trunk Attachments: HR_Recruitment.patch, HR_Recruitment.patch, HR_Recruitment.patch, HR_Recruitment.patch, HR_Recruitment.patch, HR_Recruitment.patch In this patch we have included recruitment in the HR module. Recruitment performs tasks such as admin can create new job requisitions. He can update or delete new job requisitions. Now once the job requisition has been added, it is visible to all the employees. Then if interested employee wants to apply for the job requisition he sends it for approval to his superior. Superior from his login can check who all have applied for job requisition. He can update the status and same is reflected at employee's end. Here admin can also create new interview types and he can store the information of the diffrent interviews of employees. We have created Security groups: HUMANRES_APPROVER HUMANRES_EMPLOYEE We have created Security permissions: HUMANRES_APPROVE We have created Login Id's : demoadmin belongs to FULLADMIN security group demoapprover belongs to HUMANRES_APPROVER security group demoemployee belongs to HUMANRES_EMPLOYEE security group -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (OFBIZ-2205) Implemented recruitment in HR module
[ https://issues.apache.org/jira/browse/OFBIZ-2205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12706388#action_12706388 ] Ashish Vijaywargiya commented on OFBIZ-2205: Hello Abhinav, Are you working on the points suggested by Jacopo ? Didn't see any response from since long so was curious to know how is it going ? -- Ashish Implemented recruitment in HR module Key: OFBIZ-2205 URL: https://issues.apache.org/jira/browse/OFBIZ-2205 Project: OFBiz Issue Type: New Feature Components: humanres Affects Versions: SVN trunk Environment: Windows XP Professional (5.1, Build 2600) Service Pack 2, Intel(R) Core(TM)2 CPU 4300 @ 1.80GHz (2 CPUs), 1014MB RAM, jdk1.5.0, apache-ant-1.7.0 Reporter: Abhinav Vaid Assignee: Ashish Vijaywargiya Priority: Minor Fix For: SVN trunk Attachments: HR_Recruitment.patch, HR_Recruitment.patch, HR_Recruitment.patch, HR_Recruitment.patch, HR_Recruitment.patch, HR_Recruitment.patch In this patch we have included recruitment in the HR module. Recruitment performs tasks such as admin can create new job requisitions. He can update or delete new job requisitions. Now once the job requisition has been added, it is visible to all the employees. Then if interested employee wants to apply for the job requisition he sends it for approval to his superior. Superior from his login can check who all have applied for job requisition. He can update the status and same is reflected at employee's end. Here admin can also create new interview types and he can store the information of the diffrent interviews of employees. We have created Security groups: HUMANRES_APPROVER HUMANRES_EMPLOYEE We have created Security permissions: HUMANRES_APPROVE We have created Login Id's : demoadmin belongs to FULLADMIN security group demoapprover belongs to HUMANRES_APPROVER security group demoemployee belongs to HUMANRES_EMPLOYEE security group -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (OFBIZ-2205) Implemented recruitment in HR module
[ https://issues.apache.org/jira/browse/OFBIZ-2205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12703134#action_12703134 ] Jacopo Cappellato commented on OFBIZ-2205: -- Abhinav, Ashish, thanks for your work and review, they are both very appreciated. I would like to add mine comments after reviewing the data model part of this patch: 1) instead of approverId I would suggest approverPartyId; also, wouldn't be better to define the fk to the Party entity (instead of the Person entity)? 2) InterviewInformation: 2a) woudn't be better to name it just Interview or even better JobInterview? (but if we choose JobInterview then we shoudl add the job prefix to some of its fields for consistency) 2b) should gradeSecured, result be associated to the Enumeration entity (and renamed to gradeSecuredEnumId etc..)? 2c) intervieweeId and interviewerId should be intervieweePartyId and interviewerPartyId and associated to the Party entity (not Person entity) 3) Exam: I think we can use the Enumeration entity instead of a new entity; or at least we should rename it as ExamType 4) what is the purpose of the JobPostingType entity? sorry, I can't understand it from the context (in general, what is a job posting?) 5) EmployeeAction: I am not 100% sure about the meaning of this entity but maybe instead of it we could use the EmplPosition and EmplPositionFulfillment entities (I suspect that they model the same exact data) Cheers, Jacopo Implemented recruitment in HR module Key: OFBIZ-2205 URL: https://issues.apache.org/jira/browse/OFBIZ-2205 Project: OFBiz Issue Type: New Feature Components: humanres Affects Versions: SVN trunk Environment: Windows XP Professional (5.1, Build 2600) Service Pack 2, Intel(R) Core(TM)2 CPU 4300 @ 1.80GHz (2 CPUs), 1014MB RAM, jdk1.5.0, apache-ant-1.7.0 Reporter: Abhinav Vaid Assignee: Ashish Vijaywargiya Priority: Minor Fix For: SVN trunk Attachments: HR_Recruitment.patch, HR_Recruitment.patch, HR_Recruitment.patch, HR_Recruitment.patch, HR_Recruitment.patch, HR_Recruitment.patch In this patch we have included recruitment in the HR module. Recruitment performs tasks such as admin can create new job requisitions. He can update or delete new job requisitions. Now once the job requisition has been added, it is visible to all the employees. Then if interested employee wants to apply for the job requisition he sends it for approval to his superior. Superior from his login can check who all have applied for job requisition. He can update the status and same is reflected at employee's end. Here admin can also create new interview types and he can store the information of the diffrent interviews of employees. We have created Security groups: HUMANRES_APPROVER HUMANRES_EMPLOYEE We have created Security permissions: HUMANRES_APPROVE We have created Login Id's : demoadmin belongs to FULLADMIN security group demoapprover belongs to HUMANRES_APPROVER security group demoemployee belongs to HUMANRES_EMPLOYEE security group -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (OFBIZ-2205) Implemented recruitment in HR module
[ https://issues.apache.org/jira/browse/OFBIZ-2205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12703137#action_12703137 ] Ashish Vijaywargiya commented on OFBIZ-2205: Hello Jacopo, Thanks for your comment on this. I agree on all of them. Hello Abhinav, Can you please take the recent patch uploaded by me and start working on Jacopo's comment ? Please ask question if you need help so that we all could discuss the things on the mailing list. Thanks ! -- Ashish Vijaywargiya Implemented recruitment in HR module Key: OFBIZ-2205 URL: https://issues.apache.org/jira/browse/OFBIZ-2205 Project: OFBiz Issue Type: New Feature Components: humanres Affects Versions: SVN trunk Environment: Windows XP Professional (5.1, Build 2600) Service Pack 2, Intel(R) Core(TM)2 CPU 4300 @ 1.80GHz (2 CPUs), 1014MB RAM, jdk1.5.0, apache-ant-1.7.0 Reporter: Abhinav Vaid Assignee: Ashish Vijaywargiya Priority: Minor Fix For: SVN trunk Attachments: HR_Recruitment.patch, HR_Recruitment.patch, HR_Recruitment.patch, HR_Recruitment.patch, HR_Recruitment.patch, HR_Recruitment.patch In this patch we have included recruitment in the HR module. Recruitment performs tasks such as admin can create new job requisitions. He can update or delete new job requisitions. Now once the job requisition has been added, it is visible to all the employees. Then if interested employee wants to apply for the job requisition he sends it for approval to his superior. Superior from his login can check who all have applied for job requisition. He can update the status and same is reflected at employee's end. Here admin can also create new interview types and he can store the information of the diffrent interviews of employees. We have created Security groups: HUMANRES_APPROVER HUMANRES_EMPLOYEE We have created Security permissions: HUMANRES_APPROVE We have created Login Id's : demoadmin belongs to FULLADMIN security group demoapprover belongs to HUMANRES_APPROVER security group demoemployee belongs to HUMANRES_EMPLOYEE security group -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (OFBIZ-2205) Implemented recruitment in HR module
[ https://issues.apache.org/jira/browse/OFBIZ-2205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12701460#action_12701460 ] Abhinav Vaid commented on OFBIZ-2205: - Hi Ashish Thanks for your appreciation. Did you get any chance to look into the patch? Hope to hear from you soon. Regards Abhinav Vaid iLabs, L T Infotech Ltd. Mumbai. Implemented recruitment in HR module Key: OFBIZ-2205 URL: https://issues.apache.org/jira/browse/OFBIZ-2205 Project: OFBiz Issue Type: New Feature Components: humanres Affects Versions: SVN trunk Environment: Windows XP Professional (5.1, Build 2600) Service Pack 2, Intel(R) Core(TM)2 CPU 4300 @ 1.80GHz (2 CPUs), 1014MB RAM, jdk1.5.0, apache-ant-1.7.0 Reporter: Abhinav Vaid Assignee: Ashish Vijaywargiya Priority: Minor Fix For: SVN trunk Attachments: HR_Recruitment.patch, HR_Recruitment.patch, HR_Recruitment.patch, HR_Recruitment.patch, HR_Recruitment.patch In this patch we have included recruitment in the HR module. Recruitment performs tasks such as admin can create new job requisitions. He can update or delete new job requisitions. Now once the job requisition has been added, it is visible to all the employees. Then if interested employee wants to apply for the job requisition he sends it for approval to his superior. Superior from his login can check who all have applied for job requisition. He can update the status and same is reflected at employee's end. Here admin can also create new interview types and he can store the information of the diffrent interviews of employees. We have created Security groups: HUMANRES_APPROVER HUMANRES_EMPLOYEE We have created Security permissions: HUMANRES_APPROVE We have created Login Id's : demoadmin belongs to FULLADMIN security group demoapprover belongs to HUMANRES_APPROVER security group demoemployee belongs to HUMANRES_EMPLOYEE security group -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (OFBIZ-2205) Implemented recruitment in HR module
[ https://issues.apache.org/jira/browse/OFBIZ-2205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12701470#action_12701470 ] Ashish Vijaywargiya commented on OFBIZ-2205: Hello Abhinav, Sorry, I didn't get a chance to review your patch on Sunday. Will do it today after reaching to home in the evening. Thanks for the reminder ... although it is there in my queue (and my notes remind me each day to review your patch :-) ). -- Ashish Implemented recruitment in HR module Key: OFBIZ-2205 URL: https://issues.apache.org/jira/browse/OFBIZ-2205 Project: OFBiz Issue Type: New Feature Components: humanres Affects Versions: SVN trunk Environment: Windows XP Professional (5.1, Build 2600) Service Pack 2, Intel(R) Core(TM)2 CPU 4300 @ 1.80GHz (2 CPUs), 1014MB RAM, jdk1.5.0, apache-ant-1.7.0 Reporter: Abhinav Vaid Assignee: Ashish Vijaywargiya Priority: Minor Fix For: SVN trunk Attachments: HR_Recruitment.patch, HR_Recruitment.patch, HR_Recruitment.patch, HR_Recruitment.patch, HR_Recruitment.patch In this patch we have included recruitment in the HR module. Recruitment performs tasks such as admin can create new job requisitions. He can update or delete new job requisitions. Now once the job requisition has been added, it is visible to all the employees. Then if interested employee wants to apply for the job requisition he sends it for approval to his superior. Superior from his login can check who all have applied for job requisition. He can update the status and same is reflected at employee's end. Here admin can also create new interview types and he can store the information of the diffrent interviews of employees. We have created Security groups: HUMANRES_APPROVER HUMANRES_EMPLOYEE We have created Security permissions: HUMANRES_APPROVE We have created Login Id's : demoadmin belongs to FULLADMIN security group demoapprover belongs to HUMANRES_APPROVER security group demoemployee belongs to HUMANRES_EMPLOYEE security group -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (OFBIZ-2205) Implemented recruitment in HR module
[ https://issues.apache.org/jira/browse/OFBIZ-2205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12700034#action_12700034 ] Ashish Vijaywargiya commented on OFBIZ-2205: Hello Abhinav, Thanks for your continue work on this. I will review your patch on this weekend and will share my thoughts / comments. Sorry for being little late but I was bit busy in last week so didn't get a chance to review your patch. -- Ashish Implemented recruitment in HR module Key: OFBIZ-2205 URL: https://issues.apache.org/jira/browse/OFBIZ-2205 Project: OFBiz Issue Type: New Feature Components: humanres Affects Versions: SVN trunk Environment: Windows XP Professional (5.1, Build 2600) Service Pack 2, Intel(R) Core(TM)2 CPU 4300 @ 1.80GHz (2 CPUs), 1014MB RAM, jdk1.5.0, apache-ant-1.7.0 Reporter: Abhinav Vaid Assignee: Ashish Vijaywargiya Priority: Minor Fix For: SVN trunk Attachments: HR_Recruitment.patch, HR_Recruitment.patch, HR_Recruitment.patch, HR_Recruitment.patch, HR_Recruitment.patch In this patch we have included recruitment in the HR module. Recruitment performs tasks such as admin can create new job requisitions. He can update or delete new job requisitions. Now once the job requisition has been added, it is visible to all the employees. Then if interested employee wants to apply for the job requisition he sends it for approval to his superior. Superior from his login can check who all have applied for job requisition. He can update the status and same is reflected at employee's end. Here admin can also create new interview types and he can store the information of the diffrent interviews of employees. We have created Security groups: HUMANRES_APPROVER HUMANRES_EMPLOYEE We have created Security permissions: HUMANRES_APPROVE We have created Login Id's : demoadmin belongs to FULLADMIN security group demoapprover belongs to HUMANRES_APPROVER security group demoemployee belongs to HUMANRES_EMPLOYEE security group -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (OFBIZ-2205) Implemented recruitment in HR module
[
https://issues.apache.org/jira/browse/OFBIZ-2205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12696007#action_12696007
]
Ashish Vijaywargiya commented on OFBIZ-2205:
Hello Abhinav,
Let's go with the Approach 1:
For displaying the First Name and Last Name you can use the following code
snippet. It will also provide you the link to navigate to the Profile page of
the party.
field name=partyId widget-style=buttontext
display-entity entity-name=PartyNameView
description=${firstName} ${middleName} ${lastName} ${groupName}
sub-hyperlink target=/partymgr/control/viewprofile
target-type=inter-app description=${partyId} link-style=buttontext
parameter param-name=partyId from-field=partyId/
/sub-hyperlink
/display-entity
/field
If you want to see the contents on the GUI then take a look at the following
link. And in this link add one record and see the Party Id column in the
resultant screen in the bottom.
https://localhost:8443/workeffort/control/ListWorkEffortPartyAssigns?workEffortId=DEFAULT_ROUTING
--
Ashish Vijaywargiya
Implemented recruitment in HR module
Key: OFBIZ-2205
URL: https://issues.apache.org/jira/browse/OFBIZ-2205
Project: OFBiz
Issue Type: New Feature
Components: humanres
Affects Versions: SVN trunk
Environment: Windows XP Professional (5.1, Build 2600) Service Pack
2, Intel(R) Core(TM)2 CPU 4300 @ 1.80GHz (2 CPUs), 1014MB RAM, jdk1.5.0,
apache-ant-1.7.0
Reporter: Abhinav Vaid
Assignee: Ashish Vijaywargiya
Priority: Minor
Fix For: SVN trunk
Attachments: HR_Recruitment.patch, HR_Recruitment.patch,
HR_Recruitment.patch, HR_Recruitment.patch
In this patch we have included recruitment in the HR module.
Recruitment performs tasks such as admin can create new job requisitions.
He can update or delete new job requisitions.
Now once the job requisition has been added, it is visible to all the
employees.
Then if interested employee wants to apply for the job requisition he sends
it for approval to his superior.
Superior from his login can check who all have applied for job requisition.
He can update the status and same is reflected at employee's end.
Here admin can also create new interview types and he can store the
information of the diffrent interviews of employees.
We have created Security groups:
HUMANRES_APPROVER
HUMANRES_EMPLOYEE
We have created Security permissions:
HUMANRES_APPROVE
We have created Login Id's :
demoadmin belongs to FULLADMIN security group
demoapprover belongs to HUMANRES_APPROVER security group
demoemployee belongs to HUMANRES_EMPLOYEE security group
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (OFBIZ-2205) Implemented recruitment in HR module
[ https://issues.apache.org/jira/browse/OFBIZ-2205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12694952#action_12694952 ] Abhinav Vaid commented on OFBIZ-2205: - Hi Ashish, Thanks for all your comments and appreciation. With respect to comment dated 24th March 09 it was suggested to use different approach for doing the same things instead of using ApproverAndCandidate, InterviweeAndInterviewer, PersonAndEmployeeActions view entities to solve our purpose, as they were created from two view-entities. I would like to elaborate on the purpose of these view entities. As we are providing login functionality, so user (admin, employee and approver) can view the names of all the applying parties as well as their approver's. So for displaying their names in the search result, we had to create these view entities. We have created one view entity (ApproverAndCandidate) from two view entities (CandidateAndPerson and ApproverAndPerson) as in our entity EmploymentApp we have two fields i.e. applyingPartyId and approverId which are both partyId's. So for fetching first and last names of applyingPartyId we had to create one view (CandidateAndPerson) that will first fetch names for applyingPartyId from Person table and then another view (ApproverAndPerson) that will fetch names for approverId from the same Person table. This is the reason why we had to create another view from these two views. We understand your concern and here we suggest three Approaches that can be followed: - Approach 1: We can make both approverId and applyingPartyId as hyperlinks. They can be redirected to ViewProfile page. In this case all the view entities can be ignored and if anybody is interested in their details then he can click on the partyId and the same will be redirected to party detail page where he can see the first name and last name of the party. Approach 2: We display either approverId's first and last names or applyingPartyId's first and last names. In this case we will not require the third view entity that is created from two veiw entities. Approach 3: We display names of both approver and applying party. In this case we will require all the view entities that have created in our patch. Kindly suggest us which approach to follow and also if there are some other alternative approaches for the same. Regards Abhinav Vaid iLabs, L T Infotech Ltd. Mumbai. Implemented recruitment in HR module Key: OFBIZ-2205 URL: https://issues.apache.org/jira/browse/OFBIZ-2205 Project: OFBiz Issue Type: New Feature Components: humanres Affects Versions: SVN trunk Environment: Windows XP Professional (5.1, Build 2600) Service Pack 2, Intel(R) Core(TM)2 CPU 4300 @ 1.80GHz (2 CPUs), 1014MB RAM, jdk1.5.0, apache-ant-1.7.0 Reporter: Abhinav Vaid Assignee: Ashish Vijaywargiya Priority: Minor Fix For: SVN trunk Attachments: HR_Recruitment.patch, HR_Recruitment.patch, HR_Recruitment.patch, HR_Recruitment.patch In this patch we have included recruitment in the HR module. Recruitment performs tasks such as admin can create new job requisitions. He can update or delete new job requisitions. Now once the job requisition has been added, it is visible to all the employees. Then if interested employee wants to apply for the job requisition he sends it for approval to his superior. Superior from his login can check who all have applied for job requisition. He can update the status and same is reflected at employee's end. Here admin can also create new interview types and he can store the information of the diffrent interviews of employees. We have created Security groups: HUMANRES_APPROVER HUMANRES_EMPLOYEE We have created Security permissions: HUMANRES_APPROVE We have created Login Id's : demoadmin belongs to FULLADMIN security group demoapprover belongs to HUMANRES_APPROVER security group demoemployee belongs to HUMANRES_EMPLOYEE security group -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (OFBIZ-2205) Implemented recruitment in HR module
[ https://issues.apache.org/jira/browse/OFBIZ-2205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12689476#action_12689476 ] Abhinav Vaid commented on OFBIZ-2205: - Hello Ashish Thanks for your comments. We are happy to answer questions that you asked : 1) Purpose of default map in forms : It tells the form, what default map is to be used. If you have anything in addition to it, please share with us. 2) Purpose of default-field-type=hidden in auto-fields : It is used to select only the fields required for our target service from the input map. If we get our data from a map other than the default, we specify it with map-name=otherMap. If you have anything in addition to it, please share with us. 3) Removal of else part from all the service implementation except Create Job Requisition: You have told us to get rid of the else part of all the service implementation except job requisition. In job requisition also we are not explicitly passing the job requisition id. So it would be better if we remove the else part from its implementation as well. 4) Instead of Begins With we should prefer Contains for searching: You asked to use Contains as the default option instead of Begins With. To accomplish this we will have to make changes in framework file i.e HtmlFormRenderer.java. And, the same will be reflected everywhere in the OFBiz. We suggest it is better to use Contains as the default option because Contains covers begins with. What do you suggest? Regards Abhinav Vaid iLabs, Larsen Toubro Infotech Ltd. Mumbai. Implemented recruitment in HR module Key: OFBIZ-2205 URL: https://issues.apache.org/jira/browse/OFBIZ-2205 Project: OFBiz Issue Type: New Feature Components: humanres Affects Versions: SVN trunk Environment: Windows XP Professional (5.1, Build 2600) Service Pack 2, Intel(R) Core(TM)2 CPU 4300 @ 1.80GHz (2 CPUs), 1014MB RAM, jdk1.5.0, apache-ant-1.7.0 Reporter: Abhinav Vaid Assignee: Ashish Vijaywargiya Priority: Minor Fix For: SVN trunk Attachments: HR_Recruitment.patch, HR_Recruitment.patch, HR_Recruitment.patch, HR_Recruitment.patch In this patch we have included recruitment in the HR module. Recruitment performs tasks such as admin can create new job requisitions. He can update or delete new job requisitions. Now once the job requisition has been added, it is visible to all the employees. Then if interested employee wants to apply for the job requisition he sends it for approval to his superior. Superior from his login can check who all have applied for job requisition. He can update the status and same is reflected at employee's end. Here admin can also create new interview types and he can store the information of the diffrent interviews of employees. We have created Security groups: HUMANRES_APPROVER HUMANRES_EMPLOYEE We have created Security permissions: HUMANRES_APPROVE We have created Login Id's : demoadmin belongs to FULLADMIN security group demoapprover belongs to HUMANRES_APPROVER security group demoemployee belongs to HUMANRES_EMPLOYEE security group -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (OFBIZ-2205) Implemented recruitment in HR module
[ https://issues.apache.org/jira/browse/OFBIZ-2205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12688619#action_12688619 ] Ashish Vijaywargiya commented on OFBIZ-2205: Hello Abhinav, Please take a look at the ongoing discussion on creating View entity using another View entity. Here is the link to see the discussion. http://www.nabble.com/One-view-entity-member-of-another-view-entity-to22657407.html Specially notice the David's reply in that thread. (For your reference pasting the contents here) Is it feasible? That depends on the constraints you're working with. It does usually work and can be done, but also often results in asking the database to do more than your code really needs it to do (ie including things in the joins that you don't need, significantly slowing performance). The same is true of poorly defined view-entities with normal (non-view) member entities, but there is more of a tendency for that with views of views. -David -- So now we can say that we should avoid the use of View that uses another View entity for data preparation. We should find the alternate approach for doing the same thing instead of using ApproverAndCandidate, InterviweeAndInterviewer, PersonAndEmployeeAction view entities to solve our purpose. -- Ashish Vijaywargiya Implemented recruitment in HR module Key: OFBIZ-2205 URL: https://issues.apache.org/jira/browse/OFBIZ-2205 Project: OFBiz Issue Type: New Feature Components: humanres Affects Versions: SVN trunk Environment: Windows XP Professional (5.1, Build 2600) Service Pack 2, Intel(R) Core(TM)2 CPU 4300 @ 1.80GHz (2 CPUs), 1014MB RAM, jdk1.5.0, apache-ant-1.7.0 Reporter: Abhinav Vaid Assignee: Ashish Vijaywargiya Priority: Minor Fix For: SVN trunk Attachments: HR_Recruitment.patch, HR_Recruitment.patch, HR_Recruitment.patch, HR_Recruitment.patch In this patch we have included recruitment in the HR module. Recruitment performs tasks such as admin can create new job requisitions. He can update or delete new job requisitions. Now once the job requisition has been added, it is visible to all the employees. Then if interested employee wants to apply for the job requisition he sends it for approval to his superior. Superior from his login can check who all have applied for job requisition. He can update the status and same is reflected at employee's end. Here admin can also create new interview types and he can store the information of the diffrent interviews of employees. We have created Security groups: HUMANRES_APPROVER HUMANRES_EMPLOYEE We have created Security permissions: HUMANRES_APPROVE We have created Login Id's : demoadmin belongs to FULLADMIN security group demoapprover belongs to HUMANRES_APPROVER security group demoemployee belongs to HUMANRES_EMPLOYEE security group -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (OFBIZ-2205) Implemented recruitment in HR module
[
https://issues.apache.org/jira/browse/OFBIZ-2205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12688229#action_12688229
]
Ashish Vijaywargiya commented on OFBIZ-2205:
Hello Abhinav,
The updated patch looks lot better from the initial one.
Yesterday I have spent some time in reviewing the content of your patch Here
are few more comments
(I am sure you will not feel bad to see my comments again :-) ):
1) JobRequisition lookup should be improved. It is hard to remember the exact
jobRequisitionId so we should include other fields from JobRequisition entity.
Instead of Begins With we should prefer Contains for searching. Change this
everywhere in the patch.
2) EditApprovalStatus form should be improved to use the StatusValidChange. For
ex: Internal Job Posting status can't be changed from Rejected to Approved.
Please ask question if it is confusing. You can search existing patterns to
understand the concept.
3) I think we should get rid of else part from all the service implementation
except Create Job Requisition.
The reason is that we are not explicitly passing the applicationId from the
html form.
+if-empty field=parameters.applicationId
+make-next-seq-id value-field=newEntity
seq-field-name=applicationId/
+else
+set from-field=parameters.applicationId
field=newEntity.applicationId/
+/else
+/if-empty
This case will not be applied on *Type entity based service implementation like
InterviewType JobPostingType.
4) For changing the behaviour(optional=true to optional=false vice versa)
of any field in the service definition we should use the override tag.
Change all the attribute tag into override tag and do the same for other
service definition.
+service name=updateJobRequisition engine=simple
default-entity-name=JobRequisition
+location=org/ofbiz/humanres/HumanResServices.xml
invoke=updateJobRequisition auth=true
+descriptionUpdate Job Requisition/description
+permission-service service-name=humanResManagerPermission
main-action=UPDATE/
+auto-attributes mode=IN include=pk optional=false/
+auto-attributes mode=IN include=nonpk optional=true/
+attribute name=noOfResources mode=IN type=java.lang.Long
optional=false/
+attribute name=durationMonths mode=IN type=java.lang.Long
optional=false/
+attribute name=location mode=IN type=String optional=false/
+/service
+
5) Do you know the purpose of default-map attribute in form tag ?
+form name=AddJobPostingType type=single target=createJobPostingType
default-map-name=jobPostingType
Please explain if its not clear then let me know I will help you.
6) The following line should be changed to use the new pattern (see revision
756025 for more details) :
+field name=deleteLink title=${uiLabelMap.CommonDelete}
widget-style=buttontext
+hyperlink
target=deleteInterviewType?interviewTypeId=${interviewTypeId}
description=${uiLabelMap.CommonDelete} also-hidden=false/
+/field
Please try to find the reason of this change and if you are unable to find the
reason then please let us know.
7) Do you know the purpose of default-field-type=hidden in the following line
?
+auto-fields-service service-name=updateJobPostingType
default-field-type=hidden/
Please explain if its not clear then let me know I will help you.
8) You need not to fetch the userLogin object from session attribute in the
groovy files.
It is implicitly available.
+userLogin = session.getAttribute(userLogin);
9) We should change the groovy file name from LoginHR.groovy to something
more verbose.
Like ApproverPermissionCheck.groovy or ValidateApproverPermission.groovy or
IdentifyApproverPermission.groovy.
10) There is no need to add prefix or suffix as genericValue. Just write the
name of entity following camelcase pattern.
For example : genericValueUserLoginSecurityGroup can be changed to
userLoginSecurityGroup.
This is again best practice and code can be reviewed in existing applications.
For fetching list you need to add only s as suffix after the name of entity
following camelcase pattern.
For example : UserLoginSecurityGroupList can be changed into
userLoginSecurityGroups
Although userLoginSecurityGroupList is also good to keep (Change U to u).
General Note : Initially I was thinking to do all these changes but I thought
it would be difficult for you to review the changes.
I hope my comments will help you to overcome from such issues in future.
--
Ashish Vijaywargiya
Implemented recruitment in HR module
Key: OFBIZ-2205
URL: https://issues.apache.org/jira/browse/OFBIZ-2205
Project: OFBiz
Issue Type: New Feature
Components: humanres
Affects Versions: SVN trunk
Environment:
[jira] Commented: (OFBIZ-2205) Implemented recruitment in HR module
[ https://issues.apache.org/jira/browse/OFBIZ-2205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12682125#action_12682125 ] Ashish Vijaywargiya commented on OFBIZ-2205: Thanks Abhinav for the updated patch. I will take care of this as soon as I will get a chance. -- Ashish Implemented recruitment in HR module Key: OFBIZ-2205 URL: https://issues.apache.org/jira/browse/OFBIZ-2205 Project: OFBiz Issue Type: New Feature Components: humanres Affects Versions: SVN trunk Environment: Windows XP Professional (5.1, Build 2600) Service Pack 2, Intel(R) Core(TM)2 CPU 4300 @ 1.80GHz (2 CPUs), 1014MB RAM, jdk1.5.0, apache-ant-1.7.0 Reporter: Abhinav Vaid Assignee: Ashish Vijaywargiya Priority: Minor Fix For: SVN trunk Attachments: HR_Recruitment.patch, HR_Recruitment.patch, HR_Recruitment.patch, HR_Recruitment.patch In this patch we have included recruitment in the HR module. Recruitment performs tasks such as admin can create new job requisitions. He can update or delete new job requisitions. Now once the job requisition has been added, it is visible to all the employees. Then if interested employee wants to apply for the job requisition he sends it for approval to his superior. Superior from his login can check who all have applied for job requisition. He can update the status and same is reflected at employee's end. Here admin can also create new interview types and he can store the information of the diffrent interviews of employees. We have created Security groups: HUMANRES_APPROVER HUMANRES_EMPLOYEE We have created Security permissions: HUMANRES_APPROVE We have created Login Id's : demoadmin belongs to FULLADMIN security group demoapprover belongs to HUMANRES_APPROVER security group demoemployee belongs to HUMANRES_EMPLOYEE security group -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (OFBIZ-2205) Implemented recruitment in HR module
[ https://issues.apache.org/jira/browse/OFBIZ-2205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12680128#action_12680128 ] Ashish Vijaywargiya commented on OFBIZ-2205: Hello Abhinav, Thanks for improving the patch. Here are few more comments to improve the patch: 1) Please look at the console while clicking each link. It is giving error for missing requirement for the tags in Xml files. The reason is that some of the attribute has been deprecated and replaced by new one. For example : set-nonpk-fields map-name=parameters value-name=newEntity/ Changed to set-nonpk-fields map-name=parameters value-field=newEntity/ Change in value-name -- value-field. Please update it in all the XML files. Also check the other tags and use the proper attribute so we don't see console errors. You can always take Example component for improving your files. As all these changes are being done in example component first. 2) We should always put the seed data in XML files instead of hard coding all the values in the form widget or FTL files. For Example : +option key=B.tech description=B.tech/ +option key=MBA description=MBA/ +option key=Bsc description=Bsc/ +option key=Msc description=Msc/ What should be the case if we will be having 50 degree course for selection criteria ? Please shift all this values in the seed data files. 3) Why are you using auto-field-entity twice in a patch, please explain ? +auto-fields-entity entity-name=JobRequisition default-field-type=display/ +actions +set field=jobRequisitionId from-field=parameters.jobRequisitionId/ +/actions +auto-fields-entity entity-name=JobRequisition default-field-type=find/ 4) We should improve the naming convention. Like for search form in example component we have used FindExamples ListExamples. EditExample screen definition is used for Create and Update operation on single record of example. EditExampleFeatureAppls screen definition is used to contain two forms. One is list for and another is add form. (Note the use of s in the last of name) 5) Create the new Uilabel map entry for the following line or use use the existing one if it presents. labelYou Dont Have Permissions to Update/label Please review the code in example component before uploading another patch as there might be so many places for improvement. I will wait for your next updated patch. -- Ashish Vijaywargiya Implemented recruitment in HR module Key: OFBIZ-2205 URL: https://issues.apache.org/jira/browse/OFBIZ-2205 Project: OFBiz Issue Type: New Feature Components: humanres Affects Versions: SVN trunk Environment: Windows XP Professional (5.1, Build 2600) Service Pack 2, Intel(R) Core(TM)2 CPU 4300 @ 1.80GHz (2 CPUs), 1014MB RAM, jdk1.5.0, apache-ant-1.7.0 Reporter: Abhinav Vaid Assignee: Ashish Vijaywargiya Priority: Minor Fix For: SVN trunk Attachments: HR_Recruitment.patch, HR_Recruitment.patch In this patch we have included recruitment in the HR module. Recruitment performs tasks such as admin can create new job requisitions. He can update or delete new job requisitions. Now once the job requisition has been added, it is visible to all the employees. Then if interested employee wants to apply for the job requisition he sends it for approval to his superior. Superior from his login can check who all have applied for job requisition. He can update the status and same is reflected at employee's end. Here admin can also create new interview types and he can store the information of the diffrent interviews of employees. We have created Security groups: HUMANRES_APPROVER HUMANRES_EMPLOYEE We have created Security permissions: HUMANRES_APPROVE We have created Login Id's : demoadmin belongs to FULLADMIN security group demoapprover belongs to HUMANRES_APPROVER security group demoemployee belongs to HUMANRES_EMPLOYEE security group -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (OFBIZ-2205) Implemented recruitment in HR module
[ https://issues.apache.org/jira/browse/OFBIZ-2205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12679141#action_12679141 ] Abhinav Vaid commented on OFBIZ-2205: - Hello Ashish, Thanks for your comments and renaming the patch.Actually the recruitment process that we have followed for implementation of recruitment sub module is followed in our organization and the concepts have been referred from book named Human Resource Management by T.N. Chhabra.We are working at Larsen Toubro Infotech Ltd, Mumbai. Regards Abhinav Vaid iLabs, Larsen Toubro Infotech Ltd. Mumbai. Implemented recruitment in HR module Key: OFBIZ-2205 URL: https://issues.apache.org/jira/browse/OFBIZ-2205 Project: OFBiz Issue Type: New Feature Components: humanres Affects Versions: SVN trunk Environment: Windows XP Professional (5.1, Build 2600) Service Pack 2, Intel(R) Core(TM)2 CPU 4300 @ 1.80GHz (2 CPUs), 1014MB RAM, jdk1.5.0, apache-ant-1.7.0 Reporter: Abhinav Vaid Assignee: Ashish Vijaywargiya Priority: Minor Fix For: SVN trunk Attachments: HR_Recruitment.patch, HR_Recruitment.patch In this patch we have included recruitment in the HR module. Recruitment performs tasks such as admin can create new job requisitions. He can update or delete new job requisitions. Now once the job requisition has been added, it is visible to all the employees. Then if interested employee wants to apply for the job requisition he sends it for approval to his superior. Superior from his login can check who all have applied for job requisition. He can update the status and same is reflected at employee's end. Here admin can also create new interview types and he can store the information of the diffrent interviews of employees. We have created Security groups: HUMANRES_APPROVER HUMANRES_EMPLOYEE We have created Security permissions: HUMANRES_APPROVE We have created Login Id's : demoadmin belongs to FULLADMIN security group demoapprover belongs to HUMANRES_APPROVER security group demoemployee belongs to HUMANRES_EMPLOYEE security group -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (OFBIZ-2205) Implemented recruitment in HR module
[ https://issues.apache.org/jira/browse/OFBIZ-2205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12679153#action_12679153 ] Ashish Vijaywargiya commented on OFBIZ-2205: Hello Abhinav, Thanks for letting us know the name and author of this book. This book is very famous in India and referred by so may students in MBA stream. Good to know that you are working for Larsen Toubro Infotech Ltd. I will try to come back to your patch on this weekend and will commit the things one by one. -- Ashish Vijaywargiya Implemented recruitment in HR module Key: OFBIZ-2205 URL: https://issues.apache.org/jira/browse/OFBIZ-2205 Project: OFBiz Issue Type: New Feature Components: humanres Affects Versions: SVN trunk Environment: Windows XP Professional (5.1, Build 2600) Service Pack 2, Intel(R) Core(TM)2 CPU 4300 @ 1.80GHz (2 CPUs), 1014MB RAM, jdk1.5.0, apache-ant-1.7.0 Reporter: Abhinav Vaid Assignee: Ashish Vijaywargiya Priority: Minor Fix For: SVN trunk Attachments: HR_Recruitment.patch, HR_Recruitment.patch In this patch we have included recruitment in the HR module. Recruitment performs tasks such as admin can create new job requisitions. He can update or delete new job requisitions. Now once the job requisition has been added, it is visible to all the employees. Then if interested employee wants to apply for the job requisition he sends it for approval to his superior. Superior from his login can check who all have applied for job requisition. He can update the status and same is reflected at employee's end. Here admin can also create new interview types and he can store the information of the diffrent interviews of employees. We have created Security groups: HUMANRES_APPROVER HUMANRES_EMPLOYEE We have created Security permissions: HUMANRES_APPROVE We have created Login Id's : demoadmin belongs to FULLADMIN security group demoapprover belongs to HUMANRES_APPROVER security group demoemployee belongs to HUMANRES_EMPLOYEE security group -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (OFBIZ-2205) Implemented recruitment in HR module
[ https://issues.apache.org/jira/browse/OFBIZ-2205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12679157#action_12679157 ] avdhesh yadav commented on OFBIZ-2205: -- Hello, I am new to ofbiz and recently started exploring ofbiz .I want to know that what is standard procedure of adding any module or sub- module into ofbiz. If a company follow a certain processes ,is this process is candidate of the adding to the ofbiz ? I think only standard and well known processes should be implemented into the ofbiz. Avdhesh Yadav Implemented recruitment in HR module Key: OFBIZ-2205 URL: https://issues.apache.org/jira/browse/OFBIZ-2205 Project: OFBiz Issue Type: New Feature Components: humanres Affects Versions: SVN trunk Environment: Windows XP Professional (5.1, Build 2600) Service Pack 2, Intel(R) Core(TM)2 CPU 4300 @ 1.80GHz (2 CPUs), 1014MB RAM, jdk1.5.0, apache-ant-1.7.0 Reporter: Abhinav Vaid Assignee: Ashish Vijaywargiya Priority: Minor Fix For: SVN trunk Attachments: HR_Recruitment.patch, HR_Recruitment.patch In this patch we have included recruitment in the HR module. Recruitment performs tasks such as admin can create new job requisitions. He can update or delete new job requisitions. Now once the job requisition has been added, it is visible to all the employees. Then if interested employee wants to apply for the job requisition he sends it for approval to his superior. Superior from his login can check who all have applied for job requisition. He can update the status and same is reflected at employee's end. Here admin can also create new interview types and he can store the information of the diffrent interviews of employees. We have created Security groups: HUMANRES_APPROVER HUMANRES_EMPLOYEE We have created Security permissions: HUMANRES_APPROVE We have created Login Id's : demoadmin belongs to FULLADMIN security group demoapprover belongs to HUMANRES_APPROVER security group demoemployee belongs to HUMANRES_EMPLOYEE security group -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (OFBIZ-2205) Implemented recruitment in HR module
[ https://issues.apache.org/jira/browse/OFBIZ-2205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12679235#action_12679235 ] Jacques Le Roux commented on OFBIZ-2205: Avdhesh, You should better ask such questions on [user ML|http://docs.ofbiz.org/display/OFBADMIN/Mailing+Lists] For your specific question though : [OFBiz Contributors Best Practices|http://docs.ofbiz.org/display/OFBADMIN/OFBiz+Contributors+Best+Practices] Thanks Jacques Implemented recruitment in HR module Key: OFBIZ-2205 URL: https://issues.apache.org/jira/browse/OFBIZ-2205 Project: OFBiz Issue Type: New Feature Components: humanres Affects Versions: SVN trunk Environment: Windows XP Professional (5.1, Build 2600) Service Pack 2, Intel(R) Core(TM)2 CPU 4300 @ 1.80GHz (2 CPUs), 1014MB RAM, jdk1.5.0, apache-ant-1.7.0 Reporter: Abhinav Vaid Assignee: Ashish Vijaywargiya Priority: Minor Fix For: SVN trunk Attachments: HR_Recruitment.patch, HR_Recruitment.patch In this patch we have included recruitment in the HR module. Recruitment performs tasks such as admin can create new job requisitions. He can update or delete new job requisitions. Now once the job requisition has been added, it is visible to all the employees. Then if interested employee wants to apply for the job requisition he sends it for approval to his superior. Superior from his login can check who all have applied for job requisition. He can update the status and same is reflected at employee's end. Here admin can also create new interview types and he can store the information of the diffrent interviews of employees. We have created Security groups: HUMANRES_APPROVER HUMANRES_EMPLOYEE We have created Security permissions: HUMANRES_APPROVE We have created Login Id's : demoadmin belongs to FULLADMIN security group demoapprover belongs to HUMANRES_APPROVER security group demoemployee belongs to HUMANRES_EMPLOYEE security group -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (OFBIZ-2205) Implemented recruitment in HR module
[ https://issues.apache.org/jira/browse/OFBIZ-2205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12678594#action_12678594 ] Hans Bakker commented on OFBIZ-2205: Hello Abhinav, I would like to suggest to extend the existing entity if it has the same purpose: recording an application for a job. This is better than to create a new entity. This saves entities, services, forms and screens and integrates better with the existing application. Regards, Hans Implemented recruitment in HR module Key: OFBIZ-2205 URL: https://issues.apache.org/jira/browse/OFBIZ-2205 Project: OFBiz Issue Type: New Feature Components: humanres Affects Versions: SVN trunk Environment: Windows XP Professional (5.1, Build 2600) Service Pack 2, Intel(R) Core(TM)2 CPU 4300 @ 1.80GHz (2 CPUs), 1014MB RAM, jdk1.5.0, apache-ant-1.7.0 Reporter: Abhinav Vaid Assignee: Ashish Vijaywargiya Priority: Minor Fix For: SVN trunk Attachments: HR_Recruitment.patch In this patch we have included recruitment in the HR module. Recruitment performs tasks such as admin can create new job requisitions. He can update or delete new job requisitions. Now once the job requisition has been added, it is visible to all the employees. Then if interested employee wants to apply for the job requisition he sends it for approval to his superior. Superior from his login can check who all have applied for job requisition. He can update the status and same is reflected at employee's end. Here admin can also create new interview types and he can store the information of the diffrent interviews of employees. We have created Security groups: HUMANRES_APPROVER HUMANRES_EMPLOYEE We have created Security permissions: HUMANRES_APPROVE We have created Login Id's : demoadmin belongs to FULLADMIN security group demoapprover belongs to HUMANRES_APPROVER security group demoemployee belongs to HUMANRES_EMPLOYEE security group -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (OFBIZ-2205) Implemented recruitment in HR module
[ https://issues.apache.org/jira/browse/OFBIZ-2205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12677944#action_12677944 ] Abhinav Vaid commented on OFBIZ-2205: - Hi Ashish, Thanks for reviewing our patch. We are now working on the review comments that you have given. We will do the suggested changes and upload the patch once again. Before I upload the updated patch i would like to answer 2 of your questions. 1. Description of LoginHR.groovy This groovy file gives the login functionality in Recruitment sub module. Login Functionality : In screens like Internal Job Posting, Approval we want that a particular user should see only his records. So implicitly we need to pass partyId as filter (In search option). If that user is admin then we do not need to pass partyId in filter (In search option) as he should see all the records. This functionality is achieved in this groovy file. First we check the sercurity group to which the user belongs who has logged in. Then with that security group we check all the security permissions that the group has. If the group has HUMANRES_ADMIN permission then partyId is not passed to the screens. 2. We took reference of Recruitment process from Book named Human Resource Management by T.N. Chhabra. Regards, Abhinav Vaid Implemented recruitment in HR module Key: OFBIZ-2205 URL: https://issues.apache.org/jira/browse/OFBIZ-2205 Project: OFBiz Issue Type: New Feature Components: humanres Affects Versions: SVN trunk Environment: Windows XP Professional (5.1, Build 2600) Service Pack 2, Intel(R) Core(TM)2 CPU 4300 @ 1.80GHz (2 CPUs), 1014MB RAM, jdk1.5.0, apache-ant-1.7.0 Reporter: Abhinav Vaid Assignee: Ashish Vijaywargiya Priority: Minor Fix For: SVN trunk Attachments: HR_Recruitment.patch In this patch we have included recruitment in the HR module. Recruitment performs tasks such as admin can create new job requisitions. He can update or delete new job requisitions. Now once the job requisition has been added, it is visible to all the employees. Then if interested employee wants to apply for the job requisition he sends it for approval to his superior. Superior from his login can check who all have applied for job requisition. He can update the status and same is reflected at employee's end. Here admin can also create new interview types and he can store the information of the diffrent interviews of employees. We have created Security groups: HUMANRES_APPROVER HUMANRES_EMPLOYEE We have created Security permissions: HUMANRES_APPROVE We have created Login Id's : demoadmin belongs to FULLADMIN security group demoapprover belongs to HUMANRES_APPROVER security group demoemployee belongs to HUMANRES_EMPLOYEE security group -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (OFBIZ-2205) Implemented recruitment in HR module
[ https://issues.apache.org/jira/browse/OFBIZ-2205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12677953#action_12677953 ] Abhinav Vaid commented on OFBIZ-2205: - Hi Hans, Thanks for reviewing our patch. We created an entity named JobApplication as we want to maintain the data that which employee has sent request to which approver. After your suggestion, we have gone through the existing EmploymentApp entity. We can also extend EmploymentApp entity by adding two fields namely: approverid and jobRequisitionId. What do you suggest? Regards Abhinav Vaid Implemented recruitment in HR module Key: OFBIZ-2205 URL: https://issues.apache.org/jira/browse/OFBIZ-2205 Project: OFBiz Issue Type: New Feature Components: humanres Affects Versions: SVN trunk Environment: Windows XP Professional (5.1, Build 2600) Service Pack 2, Intel(R) Core(TM)2 CPU 4300 @ 1.80GHz (2 CPUs), 1014MB RAM, jdk1.5.0, apache-ant-1.7.0 Reporter: Abhinav Vaid Assignee: Ashish Vijaywargiya Priority: Minor Fix For: SVN trunk Attachments: HR_Recruitment.patch In this patch we have included recruitment in the HR module. Recruitment performs tasks such as admin can create new job requisitions. He can update or delete new job requisitions. Now once the job requisition has been added, it is visible to all the employees. Then if interested employee wants to apply for the job requisition he sends it for approval to his superior. Superior from his login can check who all have applied for job requisition. He can update the status and same is reflected at employee's end. Here admin can also create new interview types and he can store the information of the diffrent interviews of employees. We have created Security groups: HUMANRES_APPROVER HUMANRES_EMPLOYEE We have created Security permissions: HUMANRES_APPROVE We have created Login Id's : demoadmin belongs to FULLADMIN security group demoapprover belongs to HUMANRES_APPROVER security group demoemployee belongs to HUMANRES_EMPLOYEE security group -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (OFBIZ-2205) Implemented recruitment in HR module
[
https://issues.apache.org/jira/browse/OFBIZ-2205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12677659#action_12677659
]
Ashish Vijaywargiya commented on OFBIZ-2205:
Hello Abhinav,
Thanks for your great work on HR Recruitment Process.
I appreciate your efforts.
Here are some of my thoughts on your patch :
1) This is very big patch and takes good amount of time to review. Can you
please upload the short patch from next time ? It will help me or others to
review patch easily.
2) Please arrange the UiLabels for Recruitment in Alphabetical order.
3) We should rework on the HumanResRecruitmentData.xml file.
Here we should find out which data can be put in seed and which data can be
put in demo.
If you need reference of data types you can read the build.xml file in ofbiz
home.
4) Can you please elaborate the purpose of LoginHR.groovy file ?
5) For service implementation (inside HumanResServices.xml)
5a) We should prefer to use fail-property tag instead of fail-message so
that we could internationalize the message.
5b) check-permission should be done in service definition. Please take a look
at example component for reference.
6) We should move the CommonRecruitmentDecorator into CommonScreens.xml file
and will use location attribute in each screen definition then call this
decorator by ${parameters.mainDecoratorLocation}.
We should also remove the entries of property-map from
CommonRecruitmentDecorator.
7) Which document or book you have referred to create this recruitment process
? I will be more then happy to read and explore that :) in my spare time.
Thanks !
--
Ashish Vijaywargiya
Implemented recruitment in HR module
Key: OFBIZ-2205
URL: https://issues.apache.org/jira/browse/OFBIZ-2205
Project: OFBiz
Issue Type: New Feature
Components: humanres
Affects Versions: SVN trunk
Environment: Windows XP Professional (5.1, Build 2600) Service Pack
2, Intel(R) Core(TM)2 CPU 4300 @ 1.80GHz (2 CPUs), 1014MB RAM, jdk1.5.0,
apache-ant-1.7.0
Reporter: Abhinav Vaid
Assignee: Ashish Vijaywargiya
Priority: Minor
Fix For: SVN trunk
Attachments: HR_Recruitment.patch
In this patch we have included recruitment in the HR module.
Recruitment performs tasks such as admin can create new job requisitions.
He can update or delete new job requisitions.
Now once the job requisition has been added, it is visible to all the
employees.
Then if interested employee wants to apply for the job requisition he sends
it for approval to his superior.
Superior from his login can check who all have applied for job requisition.
He can update the status and same is reflected at employee's end.
Here admin can also create new interview types and he can store the
information of the diffrent interviews of employees.
We have created Security groups:
HUMANRES_APPROVER
HUMANRES_EMPLOYEE
We have created Security permissions:
HUMANRES_APPROVE
We have created Login Id's :
demoadmin belongs to FULLADMIN security group
demoapprover belongs to HUMANRES_APPROVER security group
demoemployee belongs to HUMANRES_EMPLOYEE security group
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (OFBIZ-2205) Implemented recruitment in HR module
[ https://issues.apache.org/jira/browse/OFBIZ-2205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12677661#action_12677661 ] Hans Bakker commented on OFBIZ-2205: Hi Abhinav Vaid, sure this would be a nice addition to ofbiz. I did not tried it, just looked at the patch. It looked to be programmed well. but can you tell me why you have added the new entity called: JobApplication while we do have already a similar entity called: EmploymentApp? Regards, Hans Implemented recruitment in HR module Key: OFBIZ-2205 URL: https://issues.apache.org/jira/browse/OFBIZ-2205 Project: OFBiz Issue Type: New Feature Components: humanres Affects Versions: SVN trunk Environment: Windows XP Professional (5.1, Build 2600) Service Pack 2, Intel(R) Core(TM)2 CPU 4300 @ 1.80GHz (2 CPUs), 1014MB RAM, jdk1.5.0, apache-ant-1.7.0 Reporter: Abhinav Vaid Assignee: Ashish Vijaywargiya Priority: Minor Fix For: SVN trunk Attachments: HR_Recruitment.patch In this patch we have included recruitment in the HR module. Recruitment performs tasks such as admin can create new job requisitions. He can update or delete new job requisitions. Now once the job requisition has been added, it is visible to all the employees. Then if interested employee wants to apply for the job requisition he sends it for approval to his superior. Superior from his login can check who all have applied for job requisition. He can update the status and same is reflected at employee's end. Here admin can also create new interview types and he can store the information of the diffrent interviews of employees. We have created Security groups: HUMANRES_APPROVER HUMANRES_EMPLOYEE We have created Security permissions: HUMANRES_APPROVE We have created Login Id's : demoadmin belongs to FULLADMIN security group demoapprover belongs to HUMANRES_APPROVER security group demoemployee belongs to HUMANRES_EMPLOYEE security group -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (OFBIZ-2205) Implemented recruitment in HR module
[ https://issues.apache.org/jira/browse/OFBIZ-2205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12676940#action_12676940 ] Ashish Vijaywargiya commented on OFBIZ-2205: Hello Abhinav, I will review your code on this weekend and will let you know my thoughts on this. BTW thanks a lot for your contribution. -- Ashish Implemented recruitment in HR module Key: OFBIZ-2205 URL: https://issues.apache.org/jira/browse/OFBIZ-2205 Project: OFBiz Issue Type: New Feature Components: humanres Affects Versions: SVN trunk Environment: Windows XP Professional (5.1, Build 2600) Service Pack 2, Intel(R) Core(TM)2 CPU 4300 @ 1.80GHz (2 CPUs), 1014MB RAM, jdk1.5.0, apache-ant-1.7.0 Reporter: Abhinav Vaid Assignee: Ashish Vijaywargiya Priority: Minor Fix For: SVN trunk Attachments: HR_Recruitment.patch In this patch we have included recruitment in the HR module. Recruitment performs tasks such as admin can create new job requisitions. He can update or delete new job requisitions. Now once the job requisition has been added, it is visible to all the employees. Then if interested employee wants to apply for the job requisition he sends it for approval to his superior. Superior from his login can check who all have applied for job requisition. He can update the status and same is reflected at employee's end. Here admin can also create new interview types and he can store the information of the diffrent interviews of employees. We have created Security groups: HUMANRES_APPROVER HUMANRES_EMPLOYEE We have created Security permissions: HUMANRES_APPROVE We have created Login Id's : demoadmin belongs to FULLADMIN security group demoapprover belongs to HUMANRES_APPROVER security group demoemployee belongs to HUMANRES_EMPLOYEE security group -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
