You have a requirement for not processing an element entry based on a specific condition that will be evaluated during payroll run. How should you achieve this?
You write a skip rule with the condition so that the element is not processed when the condition is satisfied.
You write a calculation formula with the condition so that the element is not processed when the condition is satisfied.
You write a validation formula with the condition so that the element is not processed when the condition is satisfied.
You cannot meet this requirement because once an element entry is created, it will be processed all the time.
Your customer has a business requirement to only allow their employees to create one personal payment method. How should you configure this within the product?
Remove the “Manage Personal Payment Method” privilege from the employee role, so that employees cannot create personal payment methods.
Create a formula to define the maximum number of payment methods allowed, ant attach it to the payroll user interface configuration user defined table.
Create an information element with an input value to store the maximum number of payment methods allowed.
It is not possible to implement this type of restriction within the application.
Your customer is using Fusion Absences and wants to send absence information through to Fusion Global Payroll so that it can be proceed. Aside from creating your absence elements and an absence plan, which two steps do you need to complete? (Choose two.)
Create an Absence Calculation Card to store the absence details.
Create element eligibility for your absence elements.
Manually enter the absence units in the employees element entry.
Select the “Transfer absence payment Information for payroll processing” Checkbox and attach the absence element to the absence plan.