Record Count to be 0, blank or mandatory by default.
P
Paul Abarca Calderon
As a business we are using the record count for various payroll parameters. However the default value for record count is 1, and not mandatory for both ad hoc or scheduled processes.
This leads to a problem where the users of enate misses to update the record count to the actual value for that process, which causes report issues. Having a record count that is blank or 0 will lead the users to update the record count as 0 or blank is not a proper value. Ideally having the field to be mandatory at some point in the process (such as the custom cards) will make the users to always put the proper value in that field and track the data for reporting and performance.
P
Paul Abarca Calderon
We have several processes that are using record count, mostly for the HRP Service Line. Since the record count is not mandatory offices are missing this very often. I do not have the percentage but our dashboards reflect that the majority of the offices are missing to update the record count. Record count should be mandatory at some point of the process as the flow has to progress to a certain activity that after completed, the user can update the record count with the appropriate value. We as a business should have the option select when and where the record count should be mandatory.
C
Claudine Richardson
Great to hear your perspective, Paul Abarca Calderon! I have a few more questions for you:
- What specific processes or workflows are most affected by the current default record count setting?
- How often do users forget to update the record count, and what impact does this have on your operations?
- Would you prefer the record count to be mandatory at the start of the process or at a specific point, such as when using custom cards?