I realise that the JOBKEEPER allowance type has been recently deprecated in the Ruby gem, but we still have customers for one reason or another that still use this allowance type in their system. This is causing the reading of their employee information to throw an exception while trying to build the array of allowance types.
Unless there is a way to prevent customers from using this allowance type in their payroll template setups, or a way to remove it on legacy setups, I don't think it should be removed from the SDK at this stage.
I realise that the
JOBKEEPERallowance type has been recently deprecated in the Ruby gem, but we still have customers for one reason or another that still use this allowance type in their system. This is causing the reading of their employee information to throw an exception while trying to build the array of allowance types.Unless there is a way to prevent customers from using this allowance type in their payroll template setups, or a way to remove it on legacy setups, I don't think it should be removed from the SDK at this stage.