MUX - Timesheet rules throwing error unexpectedly
book
Article ID: 383989
calendar_today
Updated On: 01-13-2025
Products
Clarity PPM SaaS
Clarity PPM On Premise
Issue/Introduction
After upgrading to 16.3.0 your existing timesheet rules are no longer working as expected as they are triggering when condition is not true.
Steps to Reproduce:
- Login as Admin
- Create Static Lookup with 2 values: Part Time and Full Time
- Create attribute on resource object based on the lookup created in the step above and API enable it.
- Navigate to MUX->Administration and create new timesheet rule.
- Timesheet Error Condition for the Rule should be set as follows:
- Person Type = Employee
- Set Custom attribute created in Step 3 above = Part Time
- Timesheet Entry Error Conditions:
- Sum of Entries Total Sum < 20
- Attempt to submit timesheet where this rule should not trigger.
- Notice error is coming from the rule.
Expected Results: it should not throw timesheet error when condition for the rule is not true.
Actual Results: it is throwing an error for a condition when it is not true.
Resolution
DE157218, Fixed in 16.3.1, also backported to 16.3.0 Patch 1
In Broadcom SaaS DE157218 was applied with upgrade
Feedback
thumb_up
Yes
thumb_down
No