If the custom process having timesheet as primary object and resource as linked object has conditions based on resource object attributes, the process may not start or advance even when the exact conditions are met.
For example, if we have a timesheet approval process with start conditions as Timesheet status = submitted; timesheet.resource(is_external) = no; timesheet.resource(employment_type = 'xxxx') , the employment type check does not work as expected. The process would fail to start even if conditions are evaluating to true.
This issue can also cause process engine startup performance issues in environments that have many processes associated to an object or objects with many custom attributes.
Here we tried with OOTB 'employment type' attribute and a custom attribute 'employment type' (with a custom lookup). Both of them fail to check the condition and process fails to start, even though the conditions are true.
Steps to Reproduce:
Expected Result: For step 7: The process 'my timesheet approval process' should start and approve the timesheet
Actual Result: The process does not start even when the condition is met
Resolved in Clarity 13.1.0 Generic Patch. Reference TEC581256
Resolved in Clarity 13.2