Validate if a pay component already exist in Recurring Payments Portlet

[SG21]

Hi All,

There are 5 Pay components created of which any one gets defaulted based on the value entered in one of the field in the Job Info portlet.

Requirement 1 - based on the value in the field, the relevant pay component has to be manually created in Recurring payments. If the pay component added is not as per the value in the field, system throws error message. This is working correct.

Requirement 2 - If there is a change of value in that field, the relevant pay component has to be added in the Recurring payment portlet. At any point there should only be one pay component (out of the 5 pay components created) in the Recurring Payment portlet against the value. So when the User adds another pay component (because the value in Job Info has changed) and saves the record, system should throw an error message. Since we have 2 pay components against one field, system should not allow to save the record. The old pay component has to be manually be deleted.

Request assistance in configuring the business rule for requirement 2 please.

Regards,

Sarika

[adriangalisteo]

Hi,

I think sgoda requirements can get complicated but the bottom line of it as the title states is that needs to know if there is a way to make the business rules check if there is an existing pay component in the Recurring payments porlet before triggering the rule.

Do you know if this is possible to achieve?

xavierlegarrec jasper.de.groot

[xavierlegarrec]

Hi sgoda

Could you please explain the whys of these 2 designs ? Sounds very worst practice to me and I would be surprised we can only find a solution to meet the customer requirement that involves so much manual work.

All the best

Xavier

[nlgro02343]

Would it not be most fitting to have some variables that calculate how much the amount is (so in each var you use the treat null as scenario + select the amount where the paycomponent matches the pay components to check) + with If then else statements you can then do the check if they Var is > 0 in a situation where it should not be to throw in the error.