You create an application for employees to submit timesheets. Employees enter work, vacation, and
sick time for a particular week.
On the entry form, employees see a summary of the total hours entered.
After the employee submits the timesheet, the application displays remaining vacation and sick time
for the employee.
To configure the form where users enter hours, select the best configuration option to calculate the
total hours for the week.
A. Use a When rule. When the value of any work, vacation, or sick time changes, the total hours
B. Use declarative processing. When the value of any work, vacation, or sick time changes, the total
C. Use procedural processing. When the value of any work, vacation, or sick time changes and the
user submits the form, the total hours change.
D. Use a data transform. When the user enters the form, the data transform determines the sum of
the work, vacation, and sick time properties.
As a best practice, it is advised to use declarative processing cautiously as you do not want to overload the declarative network. A simple on-change logic should suffice where you calculate the total hours as and when you enter the values for each day. This solution, however, is subjective to your UX requirements.
A and C seem unnecessary, why show the change after the user submits or use multiple when conditions and reduce the n the maintainability?
Posted: 1 year ago
Updated: 1 year ago
Posted: 16 Feb 2020 19:23 EST Updated: 19 Feb 2020 15:05 EST
@PagidalaJ I would agree with you that it might see like we should use procedural processing if we don't need to see the values on the same form. It is only updated after we submit. However we still need to call the activity or data transform. I'd rather it up as Declarative Processing and let the system take care of the calculation for me. Regardless of what form it was on it would be updated. I do not have to remember to call the data transform or activity.