I have reviewed the LCM workflows and noticed that the workHoursTillExpiration argument does not appear to have a value assigned to it.
However, I can see that the work item is expiring and being to the next level as expected.
Could you please help me understand where this value is configured or derived from? I would like to know where I can view the actual value being used for workHoursTillExpiration.
Only i can see this in workflow and sub workflows as well
workItemHoursTillExpiration may not be explicitly set in the subworkflow because the value can be passed from the parent workflow at runtime through input arguments in the WorkflowContext.
If it is not coming from the parent workflow, the behavior may be driven by Global Settings → Work Items or by custom code/rules that set the WorkItem expiration directly.
To verify the exact value being used, check the parent workflow/approval step arguments or add a temporary log before work item creation to print the runtime value.
Verify the workflow case for this request, We will get the idea where it will set in the workflow
@sureshbomm - Can you please share your workflow?
@sureshbomm workItemHoursTillExpiration defines the number of hours a work item (approval request) will remain open before it automatically expires. Normally this is being hardcoded in the approval subprocess or being passed from LCM workflow. Please check these and confirm if you find the values.
