Hi all! I've been trying to implement this functionality and i had some troubles, being the current one that there are some concepts that doesn't get paid once the payroll is processed.
I've checked the "valid from" date in their definition, and they are defined for the specific payroll in two places: One, the concept catalog window, attribute tab, and two, the payroll definition window, payroll concepts tab. Another thing to consider is that i have a concept that is configured just like the ones that doesn't show up, and i don't know where else to check for any difference. The concepts are type rule, employee=N, paid=N, registered=N, printed=N, read/write=N. And since they should get their value from another concept as defined in their rule i've arranged their sequence for this to work.
Is there an extra setup i'm missing for these concepts? Thank you for your help.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello Yogan! Thanks for your reply. Sorry if i didn't make myself clear. I'll answer your questions in order:
a) I tried changing the rule so it would always return something, a fixed value, is this posible?. It went from
result=getConcept("SueldoBase")*(2/100);
to
result=4;
And didn't show up in hr_movements either after the process. Im sure that SueldoBase is ok too because i use it in some other concepts that do work.
b) I think that with the previous test we can cross out this one too, since there isn't a call to the concept in result=4;.
c) I configured a specific date in the followings (windows)/(tabs): (payroll employee)/(employee) and (concept catalog)/(employee attribute). Then i tried processing the payroll for a later date, so both the employee and the concept could become valid. No good.
d) Same as a) and b)?
Thank you for your time.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi again. I'm still facing this problem. Could it be how the rules are set? I use Model Validator Document Event and JSR 94 Rule Engine API. Is there a way to debug the rules? I tried viewing the server log for some information on where is the mistake with no luck. I even started using AD 3.60 looking for some improvment here.
I hope you can help me. I wanted to open a new topic on how to debug the rules.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi all! I've been trying to implement this functionality and i had some troubles, being the current one that there are some concepts that doesn't get paid once the payroll is processed.
I've checked the "valid from" date in their definition, and they are defined for the specific payroll in two places: One, the concept catalog window, attribute tab, and two, the payroll definition window, payroll concepts tab. Another thing to consider is that i have a concept that is configured just like the ones that doesn't show up, and i don't know where else to check for any difference. The concepts are type rule, employee=N, paid=N, registered=N, printed=N, read/write=N. And since they should get their value from another concept as defined in their rule i've arranged their sequence for this to work.
Is there an extra setup i'm missing for these concepts? Thank you for your help.
Hi, I am not sure if I completely understand your question….but here goes anyway….
a) Maybe the Rule/Concept is returning zero…in which case it will not show in the movements
b) Maybe comment off the call to the other concept and see if that makes a difference
c) Is the "valid from" date of the employee correct?
d) If there is an incorrect value for the parameter of getConcept……..no error is reported
Regards
Yogan Naidoo
Hello Yogan! Thanks for your reply. Sorry if i didn't make myself clear. I'll answer your questions in order:
a) I tried changing the rule so it would always return something, a fixed value, is this posible?. It went from
result=getConcept("SueldoBase")*(2/100);to
And didn't show up in hr_movements either after the process. Im sure that SueldoBase is ok too because i use it in some other concepts that do work.
b) I think that with the previous test we can cross out this one too, since there isn't a call to the concept in result=4;.
c) I configured a specific date in the followings (windows)/(tabs): (payroll employee)/(employee) and (concept catalog)/(employee attribute). Then i tried processing the payroll for a later date, so both the employee and the concept could become valid. No good.
d) Same as a) and b)?
Thank you for your time.
Hi, it sounds like you have covered all the usual stuff…
I am not sure what else could be wrong. My final thoughts..
Hopefully the concept is being called i.e.
a) either from another concept or
b) Set the employee tick box 'on' in the concept and pull it in for a particular employee.
Let me know if you find the issue.
Regards
Yogan Naidoo
Hi again. I'm still facing this problem. Could it be how the rules are set? I use Model Validator Document Event and JSR 94 Rule Engine API. Is there a way to debug the rules? I tried viewing the server log for some information on where is the mistake with no luck. I even started using AD 3.60 looking for some improvment here.
I hope you can help me. I wanted to open a new topic on how to debug the rules.