[jira] [Comment Edited] (OFBIZ-10934) Performance Increase: Using replace() instead of replaceAll() when a regex is not used increases performance

2019-05-13 Thread Mathieu Lirzin (JIRA)


[ 
https://issues.apache.org/jira/browse/OFBIZ-10934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16838369#comment-16838369
 ] 

Mathieu Lirzin edited comment on OFBIZ-10934 at 5/13/19 8:31 AM:
-

Hello,

the [^OFBIZ10934-MORE.patch] contains some unrelated using 
{{Random#nextDouble}} instead of {{Math#random. Can you remove those?}}

Personally I would find it more easy to review, if your patches were merged 
(meaning removing the old one and replacing it with an updated one)

Thanks in advance.


was (Author: mthl):
Hello,

the [^OFBIZ10934-MORE.patch] contains some unrelated using 
{{Random#nextDouble}} instead of {{Math#random. Can you remove those?}}

Personally I would find it more easy to review, if your patches were merge 
(meaning removing the old one and replacing it with an updated one)

Thanks in advance.

> Performance Increase: Using replace() instead of replaceAll() when a regex is 
> not used increases performance
> 
>
> Key: OFBIZ-10934
> URL: https://issues.apache.org/jira/browse/OFBIZ-10934
> Project: OFBiz
>  Issue Type: Improvement
>  Components: framework
>Affects Versions: Trunk
>Reporter: bd2019us
>Priority: Trivial
>  Labels: pull-request-available
> Attachments: OFBIZ-10934.patch, OFBIZ10934-MORE.patch, affected_files
>
>
> Affected files:
> # framework/base/src/main/java/org/apache/ofbiz/base/util/UtilHttp.java
> # 
> framework/widget/src/main/java/org/apache/ofbiz/widget/renderer/macro/MacroFormRenderer.java
> # 
> framework/entity/src/main/java/org/apache/ofbiz/entity/condition/EntityOperator.java
> # framework/base/src/main/java/org/apache/ofbiz/base/util/KeyStoreUtil.java 
> When replaceAll() is utilized and no regex is used, replaceAll() can be 
> replaced with replace() for better performance.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (OFBIZ-10934) Performance Increase: Using replace() instead of replaceAll() when a regex is not used increases performance

2019-05-13 Thread Mathieu Lirzin (JIRA)


[ 
https://issues.apache.org/jira/browse/OFBIZ-10934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16838369#comment-16838369
 ] 

Mathieu Lirzin commented on OFBIZ-10934:


Hello,

the [^OFBIZ10934-MORE.patch] contains some unrelated using 
{{Random#nextDouble}} instead of {{Math#random. Can you remove those?}}

Personally I would find it more easy to review, if your patches were merge 
(meaning removing the old one and replacing it with an updated one)

Thanks in advance.

> Performance Increase: Using replace() instead of replaceAll() when a regex is 
> not used increases performance
> 
>
> Key: OFBIZ-10934
> URL: https://issues.apache.org/jira/browse/OFBIZ-10934
> Project: OFBiz
>  Issue Type: Improvement
>  Components: framework
>Affects Versions: Trunk
>Reporter: bd2019us
>Priority: Trivial
>  Labels: pull-request-available
> Attachments: OFBIZ-10934.patch, OFBIZ10934-MORE.patch, affected_files
>
>
> Affected files:
> # framework/base/src/main/java/org/apache/ofbiz/base/util/UtilHttp.java
> # 
> framework/widget/src/main/java/org/apache/ofbiz/widget/renderer/macro/MacroFormRenderer.java
> # 
> framework/entity/src/main/java/org/apache/ofbiz/entity/condition/EntityOperator.java
> # framework/base/src/main/java/org/apache/ofbiz/base/util/KeyStoreUtil.java 
> When replaceAll() is utilized and no regex is used, replaceAll() can be 
> replaced with replace() for better performance.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Comment Edited] (OFBIZ-10934) Performance Increase: Using replace() instead of replaceAll() when a regex is not used increases performance

2019-05-13 Thread Aditya Sharma (JIRA)


[ 
https://issues.apache.org/jira/browse/OFBIZ-10934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16838420#comment-16838420
 ] 

Aditya Sharma edited comment on OFBIZ-10934 at 5/13/19 9:49 AM:


Adding to Mathieu's comment, Jira itself handles patch version so the new 
merged patch can have same name *OFBIZ-10934.patch*, old ones will appear in 
grey color.

Thanks!
  


was (Author: aditya.sharma):
Adding to Mathieu's comment Jira itself handles patch version so the new merged 
patch can have same name *OFBIZ-10934.patch*, old ones will appear in grey 
color.

Thanks!
 

> Performance Increase: Using replace() instead of replaceAll() when a regex is 
> not used increases performance
> 
>
> Key: OFBIZ-10934
> URL: https://issues.apache.org/jira/browse/OFBIZ-10934
> Project: OFBiz
>  Issue Type: Improvement
>  Components: framework
>Affects Versions: Trunk
>Reporter: bd2019us
>Priority: Trivial
>  Labels: pull-request-available
> Attachments: OFBIZ-10934.patch, OFBIZ10934-MORE.patch, affected_files
>
>
> Affected files:
> # framework/base/src/main/java/org/apache/ofbiz/base/util/UtilHttp.java
> # 
> framework/widget/src/main/java/org/apache/ofbiz/widget/renderer/macro/MacroFormRenderer.java
> # 
> framework/entity/src/main/java/org/apache/ofbiz/entity/condition/EntityOperator.java
> # framework/base/src/main/java/org/apache/ofbiz/base/util/KeyStoreUtil.java 
> When replaceAll() is utilized and no regex is used, replaceAll() can be 
> replaced with replace() for better performance.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (OFBIZ-11026) HR Doc drive by process

2019-05-13 Thread Olivier Heintz (JIRA)


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

Olivier Heintz updated OFBIZ-11026:
---
Description: 
Currently HR doc main chapters are on core HR object, I propose to group them 
in a chapter and having a chapter by process in the same level bot group in the 
HR Process.

Each process is described via a scenario explained like a tutorial, and each 
time a core object is used, a link is done to its chapter.

To help review : doc with these modifications are available at 
[https://ofbizadoc.ofbizextra.org/html5/user-manual.html#_human_resources]
and Apache OFBiz standard (without modifications) is available too at 
https://ofbizadoc.ofbizextra.org/html5/user-manual-std.html#_human_resources

current HR TOC
 --
 3.2. Human Resources
     3.2.1. About Human Resources
     3.2.2. Human Resources Processes
     3.2.3. Employee Positions
     3.2.4. Employees
     3.2.5. Employments
     3.2.6. Performance Review
     3.2.7. Qualifications
     3.2.8. Recruitment
     3.2.9. Skills
     3.2.10. Resumes
     3.2.11. Training
     3.2.12. Leave
     3.2.13. Security
     3.2.14. Global HR Settings
     3.2.15. Glossary
 Proposed HR TOC
 
 4. Human Resources
     4.1. About this documentation
     4.2. About Human Resources
     4.3. HR Processes
     4.3.1. Organization, Job Position and Definition
     4.3.2. Recruitment, Candidate Selection and Hiring
     4.3.3. Employee Training and Development
     4.3.4. Performance Management and Employee Evaluation
     4.3.5. Employee Salary and Benefits Administration
     4.4. HR core object
     4.4.1. Employee Positions
     4.4.2. Employees
     4.4.3. Employments
     4.4.4. Performance Review
     4.4.5. Qualifications
     4.4.6. Recruitment
     4.4.7. Skills
     4.4.8. Resumes
     4.4.9. Training
     4.4.10. Leave
     4.4.11. Security
     4.5. Global HR Settings
     4.5.1. Skills Types
     4.6. HR Data model
     4.6.1. Employee Position
     4.6.2. Employment
     4.6.3. Qualification, Skill, Review
     4.6.4. HR App intra-application integration
     4.7. Glossary

  was:
Currently HR doc main chapters are on core HR object, I propose to group them 
in a chapter and having a chapter by process in the same level bot group in the 
HR Process.

Each process is described via a scenario explained like a tutorial, and each 
time a core object is used, a link is done to its chapter.

current HR TOC
--
3.2. Human Resources
    3.2.1. About Human Resources
    3.2.2. Human Resources Processes
    3.2.3. Employee Positions
    3.2.4. Employees
    3.2.5. Employments
    3.2.6. Performance Review
    3.2.7. Qualifications
    3.2.8. Recruitment
    3.2.9. Skills
    3.2.10. Resumes
    3.2.11. Training
    3.2.12. Leave
    3.2.13. Security
    3.2.14. Global HR Settings
    3.2.15. Glossary
Proposed HR TOC

4. Human Resources
    4.1. About this documentation
    4.2. About Human Resources
    4.3. HR Processes
    4.3.1. Organization, Job Position and Definition
    4.3.2. Recruitment, Candidate Selection and Hiring
    4.3.3. Employee Training and Development
    4.3.4. Performance Management and Employee Evaluation
    4.3.5. Employee Salary and Benefits Administration
    4.4. HR core object
    4.4.1. Employee Positions
    4.4.2. Employees
    4.4.3. Employments
    4.4.4. Performance Review
    4.4.5. Qualifications
    4.4.6. Recruitment
    4.4.7. Skills
    4.4.8. Resumes
    4.4.9. Training
    4.4.10. Leave
    4.4.11. Security
    4.5. Global HR Settings
    4.5.1. Skills Types
    4.6. HR Data model
    4.6.1. Employee Position
    4.6.2. Employment
    4.6.3. Qualification, Skill, Review
    4.6.4. HR App intra-application integration
    4.7. Glossary


> HR Doc drive by process
> ---
>
> Key: OFBIZ-11026
> URL: https://issues.apache.org/jira/browse/OFBIZ-11026
> Project: OFBiz
>  Issue Type: Sub-task
>  Components: humanres
>Affects Versions: Trunk
>Reporter: Olivier Heintz
>Priority: Major
>  Labels: Documentation, humanres
> Attachments: OFBIZ-11026_hr-intro.adoc.patch, 
> OFBIZ-11026_humanres.adoc.patch
>
>
> Currently HR doc main chapters are on core HR object, I propose to group them 
> in a chapter and having a chapter by process in the same level bot group in 
> the HR Process.
> Each process is described via a scenario explained like a tutorial, and each 
> time a core object is used, a link is done to its chapter.
> To help review : doc with these modifications are available at 
> 

[jira] [Commented] (OFBIZ-10934) Performance Increase: Using replace() instead of replaceAll() when a regex is not used increases performance

2019-05-13 Thread Jacques Le Roux (JIRA)


[ 
https://issues.apache.org/jira/browse/OFBIZ-10934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16838539#comment-16838539
 ] 

Jacques Le Roux commented on OFBIZ-10934:
-

Yes, please bd2019us use the same name, easier for all of us (including you ;)) 

> Performance Increase: Using replace() instead of replaceAll() when a regex is 
> not used increases performance
> 
>
> Key: OFBIZ-10934
> URL: https://issues.apache.org/jira/browse/OFBIZ-10934
> Project: OFBiz
>  Issue Type: Improvement
>  Components: framework
>Affects Versions: Trunk
>Reporter: bd2019us
>Priority: Trivial
>  Labels: pull-request-available
> Attachments: OFBIZ-10934.patch, OFBIZ10934-MORE.patch, affected_files
>
>
> Affected files:
> # framework/base/src/main/java/org/apache/ofbiz/base/util/UtilHttp.java
> # 
> framework/widget/src/main/java/org/apache/ofbiz/widget/renderer/macro/MacroFormRenderer.java
> # 
> framework/entity/src/main/java/org/apache/ofbiz/entity/condition/EntityOperator.java
> # framework/base/src/main/java/org/apache/ofbiz/base/util/KeyStoreUtil.java 
> When replaceAll() is utilized and no regex is used, replaceAll() can be 
> replaced with replace() for better performance.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (OFBIZ-6040) Extend Ordermgr to provide an overview of parties and their roles of an order

2019-05-13 Thread Pierre Smits (JIRA)


[ 
https://issues.apache.org/jira/browse/OFBIZ-6040?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16838429#comment-16838429
 ] 

Pierre Smits commented on OFBIZ-6040:
-

Hi Nicolas,

Are you still working this ticket?

While working on several BI improvements I came across this ticket and found it 
still unresolved.

> Extend Ordermgr to provide an overview of parties and their roles of an order
> -
>
> Key: OFBIZ-6040
> URL: https://issues.apache.org/jira/browse/OFBIZ-6040
> Project: OFBiz
>  Issue Type: Improvement
>  Components: order
>Affects Versions: Trunk
>Reporter: Pierre Smits
>Assignee: Nicolas Malin
>Priority: Major
>  Labels: order, roles
> Attachments: Screen Shot 2016-01-12 at 21.20.42.png
>
>
> Currently the screens of an order show only references to the following 
> parties related to the order:
> * the internal party (referenced through OrderRoles)
> * the opposing party (the customer or the supplier - referenced through the 
> OrderRoles entity)
> * the creator of the order (referenced in the OrderHeader entity)
> * the approver, rejecter and on-hold placer (referenced through the 
> OrderStatus entity
> But an overview of all the parties involved in the process of creation and 
> evaluation of an order (think responsible sales-/purchase managers of both 
> contract partners, legal counsel of both parties, etc) is not available. Nor 
> can these kinds of players be added or changed in current feature set 
> regarding an order.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (OFBIZ-10934) Performance Increase: Using replace() instead of replaceAll() when a regex is not used increases performance

2019-05-13 Thread Aditya Sharma (JIRA)


[ 
https://issues.apache.org/jira/browse/OFBIZ-10934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16838420#comment-16838420
 ] 

Aditya Sharma commented on OFBIZ-10934:
---

Adding to Mathieu's comment Jira itself handles patch version so the new merged 
patch can have same name *OFBIZ-10934.patch*, old ones will appear in grey 
color.

Thanks!
 

> Performance Increase: Using replace() instead of replaceAll() when a regex is 
> not used increases performance
> 
>
> Key: OFBIZ-10934
> URL: https://issues.apache.org/jira/browse/OFBIZ-10934
> Project: OFBiz
>  Issue Type: Improvement
>  Components: framework
>Affects Versions: Trunk
>Reporter: bd2019us
>Priority: Trivial
>  Labels: pull-request-available
> Attachments: OFBIZ-10934.patch, OFBIZ10934-MORE.patch, affected_files
>
>
> Affected files:
> # framework/base/src/main/java/org/apache/ofbiz/base/util/UtilHttp.java
> # 
> framework/widget/src/main/java/org/apache/ofbiz/widget/renderer/macro/MacroFormRenderer.java
> # 
> framework/entity/src/main/java/org/apache/ofbiz/entity/condition/EntityOperator.java
> # framework/base/src/main/java/org/apache/ofbiz/base/util/KeyStoreUtil.java 
> When replaceAll() is utilized and no regex is used, replaceAll() can be 
> replaced with replace() for better performance.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Created] (OFBIZ-11026) HR Doc drive by process

2019-05-13 Thread Olivier Heintz (JIRA)
Olivier Heintz created OFBIZ-11026:
--

 Summary: HR Doc drive by process
 Key: OFBIZ-11026
 URL: https://issues.apache.org/jira/browse/OFBIZ-11026
 Project: OFBiz
  Issue Type: Improvement
  Components: humanres
Affects Versions: Trunk
Reporter: Olivier Heintz


Currently HR doc main chapters are on core HR object, I propose to group them 
in a chapter and having a chapter by process in the same level bot group in the 
HR Process.

Each process is described via a scenario explained like a tutorial, and each 
time a core object is used, a link is done to its chapter.

current HR TOC
--
3.2. Human Resources
    3.2.1. About Human Resources
    3.2.2. Human Resources Processes
    3.2.3. Employee Positions
    3.2.4. Employees
    3.2.5. Employments
    3.2.6. Performance Review
    3.2.7. Qualifications
    3.2.8. Recruitment
    3.2.9. Skills
    3.2.10. Resumes
    3.2.11. Training
    3.2.12. Leave
    3.2.13. Security
    3.2.14. Global HR Settings
    3.2.15. Glossary
Proposed HR TOC

4. Human Resources
    4.1. About this documentation
    4.2. About Human Resources
    4.3. HR Processes
    4.3.1. Organization, Job Position and Definition
    4.3.2. Recruitment, Candidate Selection and Hiring
    4.3.3. Employee Training and Development
    4.3.4. Performance Management and Employee Evaluation
    4.3.5. Employee Salary and Benefits Administration
    4.4. HR core object
    4.4.1. Employee Positions
    4.4.2. Employees
    4.4.3. Employments
    4.4.4. Performance Review
    4.4.5. Qualifications
    4.4.6. Recruitment
    4.4.7. Skills
    4.4.8. Resumes
    4.4.9. Training
    4.4.10. Leave
    4.4.11. Security
    4.5. Global HR Settings
    4.5.1. Skills Types
    4.6. HR Data model
    4.6.1. Employee Position
    4.6.2. Employment
    4.6.3. Qualification, Skill, Review
    4.6.4. HR App intra-application integration
    4.7. Glossary



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (OFBIZ-11026) HR Doc drive by process

2019-05-13 Thread Olivier Heintz (JIRA)


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

Olivier Heintz updated OFBIZ-11026:
---
Attachment: OFBIZ-11026_humanres.adoc.patch

> HR Doc drive by process
> ---
>
> Key: OFBIZ-11026
> URL: https://issues.apache.org/jira/browse/OFBIZ-11026
> Project: OFBiz
>  Issue Type: Sub-task
>  Components: humanres
>Affects Versions: Trunk
>Reporter: Olivier Heintz
>Priority: Major
>  Labels: Documentation, humanres
> Attachments: OFBIZ-11026_hr-intro.adoc.patch, 
> OFBIZ-11026_humanres.adoc.patch
>
>
> Currently HR doc main chapters are on core HR object, I propose to group them 
> in a chapter and having a chapter by process in the same level bot group in 
> the HR Process.
> Each process is described via a scenario explained like a tutorial, and each 
> time a core object is used, a link is done to its chapter.
> current HR TOC
> --
> 3.2. Human Resources
>     3.2.1. About Human Resources
>     3.2.2. Human Resources Processes
>     3.2.3. Employee Positions
>     3.2.4. Employees
>     3.2.5. Employments
>     3.2.6. Performance Review
>     3.2.7. Qualifications
>     3.2.8. Recruitment
>     3.2.9. Skills
>     3.2.10. Resumes
>     3.2.11. Training
>     3.2.12. Leave
>     3.2.13. Security
>     3.2.14. Global HR Settings
>     3.2.15. Glossary
> Proposed HR TOC
> 
> 4. Human Resources
>     4.1. About this documentation
>     4.2. About Human Resources
>     4.3. HR Processes
>     4.3.1. Organization, Job Position and Definition
>     4.3.2. Recruitment, Candidate Selection and Hiring
>     4.3.3. Employee Training and Development
>     4.3.4. Performance Management and Employee Evaluation
>     4.3.5. Employee Salary and Benefits Administration
>     4.4. HR core object
>     4.4.1. Employee Positions
>     4.4.2. Employees
>     4.4.3. Employments
>     4.4.4. Performance Review
>     4.4.5. Qualifications
>     4.4.6. Recruitment
>     4.4.7. Skills
>     4.4.8. Resumes
>     4.4.9. Training
>     4.4.10. Leave
>     4.4.11. Security
>     4.5. Global HR Settings
>     4.5.1. Skills Types
>     4.6. HR Data model
>     4.6.1. Employee Position
>     4.6.2. Employment
>     4.6.3. Qualification, Skill, Review
>     4.6.4. HR App intra-application integration
>     4.7. Glossary



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (OFBIZ-11026) HR Doc drive by process

2019-05-13 Thread Olivier Heintz (JIRA)


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

Olivier Heintz updated OFBIZ-11026:
---
Attachment: OFBIZ-11026_hr-intro.adoc.patch

> HR Doc drive by process
> ---
>
> Key: OFBIZ-11026
> URL: https://issues.apache.org/jira/browse/OFBIZ-11026
> Project: OFBiz
>  Issue Type: Sub-task
>  Components: humanres
>Affects Versions: Trunk
>Reporter: Olivier Heintz
>Priority: Major
>  Labels: Documentation, humanres
> Attachments: OFBIZ-11026_hr-intro.adoc.patch, 
> OFBIZ-11026_humanres.adoc.patch
>
>
> Currently HR doc main chapters are on core HR object, I propose to group them 
> in a chapter and having a chapter by process in the same level bot group in 
> the HR Process.
> Each process is described via a scenario explained like a tutorial, and each 
> time a core object is used, a link is done to its chapter.
> current HR TOC
> --
> 3.2. Human Resources
>     3.2.1. About Human Resources
>     3.2.2. Human Resources Processes
>     3.2.3. Employee Positions
>     3.2.4. Employees
>     3.2.5. Employments
>     3.2.6. Performance Review
>     3.2.7. Qualifications
>     3.2.8. Recruitment
>     3.2.9. Skills
>     3.2.10. Resumes
>     3.2.11. Training
>     3.2.12. Leave
>     3.2.13. Security
>     3.2.14. Global HR Settings
>     3.2.15. Glossary
> Proposed HR TOC
> 
> 4. Human Resources
>     4.1. About this documentation
>     4.2. About Human Resources
>     4.3. HR Processes
>     4.3.1. Organization, Job Position and Definition
>     4.3.2. Recruitment, Candidate Selection and Hiring
>     4.3.3. Employee Training and Development
>     4.3.4. Performance Management and Employee Evaluation
>     4.3.5. Employee Salary and Benefits Administration
>     4.4. HR core object
>     4.4.1. Employee Positions
>     4.4.2. Employees
>     4.4.3. Employments
>     4.4.4. Performance Review
>     4.4.5. Qualifications
>     4.4.6. Recruitment
>     4.4.7. Skills
>     4.4.8. Resumes
>     4.4.9. Training
>     4.4.10. Leave
>     4.4.11. Security
>     4.5. Global HR Settings
>     4.5.1. Skills Types
>     4.6. HR Data model
>     4.6.1. Employee Position
>     4.6.2. Employment
>     4.6.3. Qualification, Skill, Review
>     4.6.4. HR App intra-application integration
>     4.7. Glossary



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (OFBIZ-11026) HR Doc drive by process

2019-05-13 Thread Olivier Heintz (JIRA)


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

Olivier Heintz updated OFBIZ-11026:
---
Issue Type: Sub-task  (was: Improvement)
Parent: OFBIZ-10251

> HR Doc drive by process
> ---
>
> Key: OFBIZ-11026
> URL: https://issues.apache.org/jira/browse/OFBIZ-11026
> Project: OFBiz
>  Issue Type: Sub-task
>  Components: humanres
>Affects Versions: Trunk
>Reporter: Olivier Heintz
>Priority: Major
>  Labels: Documentation, humanres
>
> Currently HR doc main chapters are on core HR object, I propose to group them 
> in a chapter and having a chapter by process in the same level bot group in 
> the HR Process.
> Each process is described via a scenario explained like a tutorial, and each 
> time a core object is used, a link is done to its chapter.
> current HR TOC
> --
> 3.2. Human Resources
>     3.2.1. About Human Resources
>     3.2.2. Human Resources Processes
>     3.2.3. Employee Positions
>     3.2.4. Employees
>     3.2.5. Employments
>     3.2.6. Performance Review
>     3.2.7. Qualifications
>     3.2.8. Recruitment
>     3.2.9. Skills
>     3.2.10. Resumes
>     3.2.11. Training
>     3.2.12. Leave
>     3.2.13. Security
>     3.2.14. Global HR Settings
>     3.2.15. Glossary
> Proposed HR TOC
> 
> 4. Human Resources
>     4.1. About this documentation
>     4.2. About Human Resources
>     4.3. HR Processes
>     4.3.1. Organization, Job Position and Definition
>     4.3.2. Recruitment, Candidate Selection and Hiring
>     4.3.3. Employee Training and Development
>     4.3.4. Performance Management and Employee Evaluation
>     4.3.5. Employee Salary and Benefits Administration
>     4.4. HR core object
>     4.4.1. Employee Positions
>     4.4.2. Employees
>     4.4.3. Employments
>     4.4.4. Performance Review
>     4.4.5. Qualifications
>     4.4.6. Recruitment
>     4.4.7. Skills
>     4.4.8. Resumes
>     4.4.9. Training
>     4.4.10. Leave
>     4.4.11. Security
>     4.5. Global HR Settings
>     4.5.1. Skills Types
>     4.6. HR Data model
>     4.6.1. Employee Position
>     4.6.2. Employment
>     4.6.3. Qualification, Skill, Review
>     4.6.4. HR App intra-application integration
>     4.7. Glossary



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (OFBIZ-11026) HR Doc drive by process

2019-05-13 Thread Olivier Heintz (JIRA)


[ 
https://issues.apache.org/jira/browse/OFBIZ-11026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16838536#comment-16838536
 ] 

Olivier Heintz commented on OFBIZ-11026:


The two patch include too, enhancement in general HR presentation and HR intro.

In hr-intro, list of existing process have been re-ordered to follow a 
functional logic (first organisation and employees, second evaluation and 
evolution)

> HR Doc drive by process
> ---
>
> Key: OFBIZ-11026
> URL: https://issues.apache.org/jira/browse/OFBIZ-11026
> Project: OFBiz
>  Issue Type: Sub-task
>  Components: humanres
>Affects Versions: Trunk
>Reporter: Olivier Heintz
>Priority: Major
>  Labels: Documentation, humanres
> Attachments: OFBIZ-11026_hr-intro.adoc.patch, 
> OFBIZ-11026_humanres.adoc.patch
>
>
> Currently HR doc main chapters are on core HR object, I propose to group them 
> in a chapter and having a chapter by process in the same level bot group in 
> the HR Process.
> Each process is described via a scenario explained like a tutorial, and each 
> time a core object is used, a link is done to its chapter.
> current HR TOC
> --
> 3.2. Human Resources
>     3.2.1. About Human Resources
>     3.2.2. Human Resources Processes
>     3.2.3. Employee Positions
>     3.2.4. Employees
>     3.2.5. Employments
>     3.2.6. Performance Review
>     3.2.7. Qualifications
>     3.2.8. Recruitment
>     3.2.9. Skills
>     3.2.10. Resumes
>     3.2.11. Training
>     3.2.12. Leave
>     3.2.13. Security
>     3.2.14. Global HR Settings
>     3.2.15. Glossary
> Proposed HR TOC
> 
> 4. Human Resources
>     4.1. About this documentation
>     4.2. About Human Resources
>     4.3. HR Processes
>     4.3.1. Organization, Job Position and Definition
>     4.3.2. Recruitment, Candidate Selection and Hiring
>     4.3.3. Employee Training and Development
>     4.3.4. Performance Management and Employee Evaluation
>     4.3.5. Employee Salary and Benefits Administration
>     4.4. HR core object
>     4.4.1. Employee Positions
>     4.4.2. Employees
>     4.4.3. Employments
>     4.4.4. Performance Review
>     4.4.5. Qualifications
>     4.4.6. Recruitment
>     4.4.7. Skills
>     4.4.8. Resumes
>     4.4.9. Training
>     4.4.10. Leave
>     4.4.11. Security
>     4.5. Global HR Settings
>     4.5.1. Skills Types
>     4.6. HR Data model
>     4.6.1. Employee Position
>     4.6.2. Employment
>     4.6.3. Qualification, Skill, Review
>     4.6.4. HR App intra-application integration
>     4.7. Glossary



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (OFBIZ-11027) HR Doc, Associated a scenario UI test for each process

2019-05-13 Thread Olivier Heintz (JIRA)


[ 
https://issues.apache.org/jira/browse/OFBIZ-11027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16838561#comment-16838561
 ] 

Olivier Heintz commented on OFBIZ-11027:


hr_intro patch included modifications which are describe in OFBIZ-11026 (HR Doc 
drive by proces)

html generate doc can be read at

- 
https://ofbizadoc.ofbizextra.org/html5/user-manual.html#_tutorial_define_my_company_organization

- 
https://ofbizadoc.ofbizextra.org/html5/user-manual.html#_tutorial_employment_and_salary

> HR Doc, Associated a scenario UI test for each process
> --
>
> Key: OFBIZ-11027
> URL: https://issues.apache.org/jira/browse/OFBIZ-11027
> Project: OFBiz
>  Issue Type: Sub-task
>  Components: humanres
>Affects Versions: Trunk
>Reporter: Olivier Heintz
>Priority: Major
>  Labels: Documentation, humanres, tutorial
> Attachments: OFBIZ-11027_hr-intro.adoc.patch, 
> hr-tuto-define-company-organization.adoc, hr-tuto-employment-and-salary.adoc
>
>
> I propose that in HR documentation, each process is described via a scenario 
> explained like a tutorial.
> To realize the tutorial, and to have more quality, I propose to create a UI 
> Test for each process.
> In these tests, some user messages are added and a video recording is in 
> place when it run, so result is usable as a tutorial
> With this method to create tutorial we are sure it are up to date and it 
> works !
> Currently a tutorial / test exist for process "Organization, Job Position and 
> Definition" and it run ona daily base on Apache OFBiz trunk demo.
> A second one exist for process "Employee Salary and Benefits Administration" 
> but for runing some modification /enhancement are needed, so currenlty it not 
> run on Apache OFBiz trunk demo.
> Result video are readeable 
> https://video.ploud.fr/video-channels/ofbizextra_tutorial/videos  
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (OFBIZ-11028) field emplFromDate is forgot in PayHistory entity

2019-05-13 Thread Olivier Heintz (JIRA)


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

Olivier Heintz updated OFBIZ-11028:
---
Attachment: OFBIZ-11028.patch

> field emplFromDate is forgot in PayHistory entity
> -
>
> Key: OFBIZ-11028
> URL: https://issues.apache.org/jira/browse/OFBIZ-11028
> Project: OFBiz
>  Issue Type: Sub-task
>  Components: humanres
>Affects Versions: Trunk, 17.12.01, 18.12.01
>Reporter: Olivier Heintz
>Priority: Major
>  Labels: humanres
> Fix For: Trunk
>
> Attachments: OFBIZ-11028.patch
>
>
> A Employment can have multiple PayHistory and should have multiple 
> because PayHistory should show history of Pay  for a employment  !
> Currently, in PayHistory the field fromDate from Employment is confused with 
> fromDate about the current record, it's necessary to have a field 
> emplFromDate (to have the complete employment primaryKey).
> Currently user interface for PayHistory is not working, when modifying a 
> PayRecord the current should be expire and a new one should be created.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (OFBIZ-10934) Performance Increase: Using replace() instead of replaceAll() when a regex is not used increases performance

2019-05-13 Thread Mathieu Lirzin (JIRA)


[ 
https://issues.apache.org/jira/browse/OFBIZ-10934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16838659#comment-16838659
 ] 

Mathieu Lirzin commented on OFBIZ-10934:


Thanks [~aditya.sharma] I didn't know about that feature.

> Performance Increase: Using replace() instead of replaceAll() when a regex is 
> not used increases performance
> 
>
> Key: OFBIZ-10934
> URL: https://issues.apache.org/jira/browse/OFBIZ-10934
> Project: OFBiz
>  Issue Type: Improvement
>  Components: framework
>Affects Versions: Trunk
>Reporter: bd2019us
>Priority: Trivial
>  Labels: pull-request-available
> Attachments: OFBIZ-10934.patch, OFBIZ10934-MORE.patch, affected_files
>
>
> Affected files:
> # framework/base/src/main/java/org/apache/ofbiz/base/util/UtilHttp.java
> # 
> framework/widget/src/main/java/org/apache/ofbiz/widget/renderer/macro/MacroFormRenderer.java
> # 
> framework/entity/src/main/java/org/apache/ofbiz/entity/condition/EntityOperator.java
> # framework/base/src/main/java/org/apache/ofbiz/base/util/KeyStoreUtil.java 
> When replaceAll() is utilized and no regex is used, replaceAll() can be 
> replaced with replace() for better performance.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (OFBIZ-11027) HR Doc, Associated a scenario UI test for each process

2019-05-13 Thread Olivier Heintz (JIRA)


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

Olivier Heintz updated OFBIZ-11027:
---
Attachment: OFBIZ-11027_hr-intro.adoc.patch

> HR Doc, Associated a scenario UI test for each process
> --
>
> Key: OFBIZ-11027
> URL: https://issues.apache.org/jira/browse/OFBIZ-11027
> Project: OFBiz
>  Issue Type: Sub-task
>  Components: humanres
>Affects Versions: Trunk
>Reporter: Olivier Heintz
>Priority: Major
>  Labels: Documentation, humanres, tutorial
> Attachments: OFBIZ-11027_hr-intro.adoc.patch
>
>
> I propose that in HR documentation, each process is described via a scenario 
> explained like a tutorial.
> To realize the tutorial, and to have more quality, I propose to create a UI 
> Test for each process.
> In these tests, some user messages are added and a video recording is in 
> place when it run, so result is usable as a tutorial
> With this method to create tutorial we are sure it are up to date and it 
> works !
> Currently a tutorial / test exist for process "Organization, Job Position and 
> Definition" and it run ona daily base on Apache OFBiz trunk demo.
> A second one exist for process "Employee Salary and Benefits Administration" 
> but for runing some modification /enhancement are needed, so currenlty it not 
> run on Apache OFBiz trunk demo.
> Result video are readeable 
> https://video.ploud.fr/video-channels/ofbizextra_tutorial/videos  
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (OFBIZ-11028) field emplFromDate is forgot in PayHistory entity

2019-05-13 Thread Olivier Heintz (JIRA)


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

Olivier Heintz updated OFBIZ-11028:
---
Attachment: OFBIZ-11028.HumanResServices.xml.patch
OFBIZ-11028.services.xml.patch

> field emplFromDate is forgot in PayHistory entity
> -
>
> Key: OFBIZ-11028
> URL: https://issues.apache.org/jira/browse/OFBIZ-11028
> Project: OFBiz
>  Issue Type: Sub-task
>  Components: humanres
>Affects Versions: Trunk, 17.12.01, 18.12.01
>Reporter: Olivier Heintz
>Priority: Major
>  Labels: humanres
> Fix For: Trunk
>
> Attachments: OFBIZ-11028.HumanResServices.xml.patch, 
> OFBIZ-11028.services.xml.patch
>
>
> A Employment can have multiple PayHistory and should have multiple 
> because PayHistory should show history of Pay  for a employment  !
> Currently, in PayHistory the field fromDate from Employment is confused with 
> fromDate about the current record, it's necessary to have a field 
> emplFromDate (to have the complete employment primaryKey).
> Currently user interface for PayHistory is not working, when modifying a 
> PayRecord the current should be expire and a new one should be created.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (OFBIZ-11028) field emplFromDate is forgot in PayHistory entity

2019-05-13 Thread Olivier Heintz (JIRA)


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

Olivier Heintz updated OFBIZ-11028:
---
Attachment: (was: OFBIZ-11028.services.xml.patch)

> field emplFromDate is forgot in PayHistory entity
> -
>
> Key: OFBIZ-11028
> URL: https://issues.apache.org/jira/browse/OFBIZ-11028
> Project: OFBiz
>  Issue Type: Sub-task
>  Components: humanres
>Affects Versions: Trunk, 17.12.01, 18.12.01
>Reporter: Olivier Heintz
>Priority: Major
>  Labels: humanres
> Fix For: Trunk
>
> Attachments: OFBIZ-11028.patch
>
>
> A Employment can have multiple PayHistory and should have multiple 
> because PayHistory should show history of Pay  for a employment  !
> Currently, in PayHistory the field fromDate from Employment is confused with 
> fromDate about the current record, it's necessary to have a field 
> emplFromDate (to have the complete employment primaryKey).
> Currently user interface for PayHistory is not working, when modifying a 
> PayRecord the current should be expire and a new one should be created.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (OFBIZ-11028) field emplFromDate is forgot in PayHistory entity

2019-05-13 Thread Olivier Heintz (JIRA)


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

Olivier Heintz updated OFBIZ-11028:
---
Attachment: (was: OFBIZ-11028.HumanResServices.xml.patch)

> field emplFromDate is forgot in PayHistory entity
> -
>
> Key: OFBIZ-11028
> URL: https://issues.apache.org/jira/browse/OFBIZ-11028
> Project: OFBiz
>  Issue Type: Sub-task
>  Components: humanres
>Affects Versions: Trunk, 17.12.01, 18.12.01
>Reporter: Olivier Heintz
>Priority: Major
>  Labels: humanres
> Fix For: Trunk
>
> Attachments: OFBIZ-11028.patch
>
>
> A Employment can have multiple PayHistory and should have multiple 
> because PayHistory should show history of Pay  for a employment  !
> Currently, in PayHistory the field fromDate from Employment is confused with 
> fromDate about the current record, it's necessary to have a field 
> emplFromDate (to have the complete employment primaryKey).
> Currently user interface for PayHistory is not working, when modifying a 
> PayRecord the current should be expire and a new one should be created.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (OFBIZ-11027) HR Doc, Associated a scenario UI test for each process

2019-05-13 Thread Olivier Heintz (JIRA)


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

Olivier Heintz updated OFBIZ-11027:
---
Attachment: hr-tuto-define-company-organization.adoc
hr-tuto-employment-and-salary.adoc

> HR Doc, Associated a scenario UI test for each process
> --
>
> Key: OFBIZ-11027
> URL: https://issues.apache.org/jira/browse/OFBIZ-11027
> Project: OFBiz
>  Issue Type: Sub-task
>  Components: humanres
>Affects Versions: Trunk
>Reporter: Olivier Heintz
>Priority: Major
>  Labels: Documentation, humanres, tutorial
> Attachments: OFBIZ-11027_hr-intro.adoc.patch, 
> hr-tuto-define-company-organization.adoc, hr-tuto-employment-and-salary.adoc
>
>
> I propose that in HR documentation, each process is described via a scenario 
> explained like a tutorial.
> To realize the tutorial, and to have more quality, I propose to create a UI 
> Test for each process.
> In these tests, some user messages are added and a video recording is in 
> place when it run, so result is usable as a tutorial
> With this method to create tutorial we are sure it are up to date and it 
> works !
> Currently a tutorial / test exist for process "Organization, Job Position and 
> Definition" and it run ona daily base on Apache OFBiz trunk demo.
> A second one exist for process "Employee Salary and Benefits Administration" 
> but for runing some modification /enhancement are needed, so currenlty it not 
> run on Apache OFBiz trunk demo.
> Result video are readeable 
> https://video.ploud.fr/video-channels/ofbizextra_tutorial/videos  
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (OFBIZ-10969) Unable to create Employments

2019-05-13 Thread Olivier Heintz (JIRA)


[ 
https://issues.apache.org/jira/browse/OFBIZ-10969?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16838589#comment-16838589
 ] 

Olivier Heintz commented on OFBIZ-10969:


Employment is associated with PayHistory, and there is a problem in PayHistory 
entity definition in OFBiz,

In PayHistory, the field fromDate from Employment is confused with fromDate 
about the current record.
I have created a sub-task of this task to add the field emplFromDate to 
PayHistory and update associated services.

The current patch HumanResServices.xml need the new field.

> Unable to create Employments
> 
>
> Key: OFBIZ-10969
> URL: https://issues.apache.org/jira/browse/OFBIZ-10969
> Project: OFBiz
>  Issue Type: Bug
>  Components: humanres
>Affects Versions: Trunk
>Reporter: Arpit Mor
>Priority: Major
> Attachments: Image1.png, OFBIZ-10969.HumanResServices.xml.patch, 
> OFBIZ-10969.services.xml.patch
>
>
> Steps to regenerate:
>  # Login to the URL: 
> [https://demo-trunk.ofbiz.apache.org/humanres/control/main]
>  # Click on Employments
>  # Click on New Employments
>  # Click on Create
> Actual: Error message is displayed. Please refer attachment: Image1



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (OFBIZ-11028) field emplFromDate is forgot in PayHistory entity

2019-05-13 Thread Olivier Heintz (JIRA)


[ 
https://issues.apache.org/jira/browse/OFBIZ-11028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16838603#comment-16838603
 ] 

Olivier Heintz commented on OFBIZ-11028:


the two patch included modifications needed by master task

> field emplFromDate is forgot in PayHistory entity
> -
>
> Key: OFBIZ-11028
> URL: https://issues.apache.org/jira/browse/OFBIZ-11028
> Project: OFBiz
>  Issue Type: Sub-task
>  Components: humanres
>Affects Versions: Trunk, 17.12.01, 18.12.01
>Reporter: Olivier Heintz
>Priority: Major
>  Labels: humanres
> Fix For: Trunk
>
> Attachments: OFBIZ-11028.HumanResServices.xml.patch, 
> OFBIZ-11028.services.xml.patch
>
>
> A Employment can have multiple PayHistory and should have multiple 
> because PayHistory should show history of Pay  for a employment  !
> Currently, in PayHistory the field fromDate from Employment is confused with 
> fromDate about the current record, it's necessary to have a field 
> emplFromDate (to have the complete employment primaryKey).
> Currently user interface for PayHistory is not working, when modifying a 
> PayRecord the current should be expire and a new one should be created.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Comment Edited] (OFBIZ-11028) field emplFromDate is forgot in PayHistory entity

2019-05-13 Thread Olivier Heintz (JIRA)


[ 
https://issues.apache.org/jira/browse/OFBIZ-11028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16838603#comment-16838603
 ] 

Olivier Heintz edited comment on OFBIZ-11028 at 5/13/19 3:41 PM:
-

In the patch, it include the two modifications needed by master task.

Patch contain
 * added new field in PayHistory
 * Employment menu correction
 * employment edit corection
 * PayHistory list and Edit correction / enhancement


was (Author: holivier):
the two patch included modifications needed by master task

> field emplFromDate is forgot in PayHistory entity
> -
>
> Key: OFBIZ-11028
> URL: https://issues.apache.org/jira/browse/OFBIZ-11028
> Project: OFBiz
>  Issue Type: Sub-task
>  Components: humanres
>Affects Versions: Trunk, 17.12.01, 18.12.01
>Reporter: Olivier Heintz
>Priority: Major
>  Labels: humanres
> Fix For: Trunk
>
> Attachments: OFBIZ-11028.patch
>
>
> A Employment can have multiple PayHistory and should have multiple 
> because PayHistory should show history of Pay  for a employment  !
> Currently, in PayHistory the field fromDate from Employment is confused with 
> fromDate about the current record, it's necessary to have a field 
> emplFromDate (to have the complete employment primaryKey).
> Currently user interface for PayHistory is not working, when modifying a 
> PayRecord the current should be expire and a new one should be created.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (OFBIZ-10969) Unable to create Employments

2019-05-13 Thread Olivier Heintz (JIRA)


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

Olivier Heintz updated OFBIZ-10969:
---
Attachment: OFBIZ-10969.HumanResServices.xml.patch

> Unable to create Employments
> 
>
> Key: OFBIZ-10969
> URL: https://issues.apache.org/jira/browse/OFBIZ-10969
> Project: OFBiz
>  Issue Type: Bug
>  Components: humanres
>Affects Versions: Trunk
>Reporter: Arpit Mor
>Priority: Major
> Attachments: Image1.png, OFBIZ-10969.HumanResServices.xml.patch, 
> OFBIZ-10969.services.xml.patch
>
>
> Steps to regenerate:
>  # Login to the URL: 
> [https://demo-trunk.ofbiz.apache.org/humanres/control/main]
>  # Click on Employments
>  # Click on New Employments
>  # Click on Create
> Actual: Error message is displayed. Please refer attachment: Image1



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (OFBIZ-10969) Unable to create Employments

2019-05-13 Thread Olivier Heintz (JIRA)


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

Olivier Heintz updated OFBIZ-10969:
---
Attachment: OFBIZ-10969.services.xml.patch

> Unable to create Employments
> 
>
> Key: OFBIZ-10969
> URL: https://issues.apache.org/jira/browse/OFBIZ-10969
> Project: OFBiz
>  Issue Type: Bug
>  Components: humanres
>Affects Versions: Trunk
>Reporter: Arpit Mor
>Priority: Major
> Attachments: Image1.png, OFBIZ-10969.HumanResServices.xml.patch, 
> OFBIZ-10969.services.xml.patch
>
>
> Steps to regenerate:
>  # Login to the URL: 
> [https://demo-trunk.ofbiz.apache.org/humanres/control/main]
>  # Click on Employments
>  # Click on New Employments
>  # Click on Create
> Actual: Error message is displayed. Please refer attachment: Image1



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Created] (OFBIZ-11027) HR Doc, Associated a scenario UI test for each process

2019-05-13 Thread Olivier Heintz (JIRA)
Olivier Heintz created OFBIZ-11027:
--

 Summary: HR Doc, Associated a scenario UI test for each process
 Key: OFBIZ-11027
 URL: https://issues.apache.org/jira/browse/OFBIZ-11027
 Project: OFBiz
  Issue Type: Sub-task
  Components: humanres
Affects Versions: Trunk
Reporter: Olivier Heintz


I propose that in HR documentation, each process is described via a scenario 
explained like a tutorial.

To realize the tutorial, and to have more quality, I propose to create a UI 
Test for each process.
In these tests, some user messages are added and a video recording is in place 
when it run, so result is usable as a tutorial

With this method to create tutorial we are sure it are up to date and it works !

Currently a tutorial / test exist for process "Organization, Job Position and 
Definition" and it run ona daily base on Apache OFBiz trunk demo.
A second one exist for process "Employee Salary and Benefits Administration" 
but for runing some modification /enhancement are needed, so currenlty it not 
run on Apache OFBiz trunk demo.

Result video are readeable 
https://video.ploud.fr/video-channels/ofbizextra_tutorial/videos  
 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Created] (OFBIZ-11028) field emplFromDate is forgot in PayHistory entity

2019-05-13 Thread Olivier Heintz (JIRA)
Olivier Heintz created OFBIZ-11028:
--

 Summary: field emplFromDate is forgot in PayHistory entity
 Key: OFBIZ-11028
 URL: https://issues.apache.org/jira/browse/OFBIZ-11028
 Project: OFBiz
  Issue Type: Sub-task
  Components: humanres
Affects Versions: Trunk, 17.12.01, 18.12.01
Reporter: Olivier Heintz
 Fix For: Trunk


A Employment can have multiple PayHistory and should have multiple 
because PayHistory should show history of Pay  for a employment  !

Currently, in PayHistory the field fromDate from Employment is confused with 
fromDate about the current record, it's necessary to have a field emplFromDate 
(to have the complete employment primaryKey).

Currently user interface for PayHistory is not working, when modifying a 
PayRecord the current should be expire and a new one should be created.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)