Idea Summary
The idea is to add a new parameter p_bypass_permission_check (default: false) to most APEX_HUMAN_TASK API procedures and functions. When p_bypass_permission_check = true, you don't need to be a Business Administrator or Actual Owner to perform a specific action.

Use Case
It would be useful when you want to perform some actions from the background processes (Oracle Job/Automation, APEX Workflow).

Let's look at my use case.

I have a risk assessment workflow that creates a Human Task (number of participants for HT > 1) with a 5-day deadline. During these 5 days, someone may or may not be assigned to the task. If the deadline passes, the workflow continues and logs the delay, changes the record's status to delayed, and then creates another instance of the same Human Task definition, this time without a deadline because I know that this record is already delayed so now I'm waiting to be completed.

If someone assigned to the first instance of the task within the first 5 days and that task expired, I would like them to be assigned to the task even after the second instance of the same Human Tasks definition is created. I can do this using the APEX_HUMAN_TASK.DELEGATE_TASK procedure executed after task creation, but there's a permissions issue.

My current workaround

I added the following code snippet to the Business Administrator participant definition:

union
select 'MY_SYSTEM_USER' from dual

When I want to execute an operation, such as delegate_task, from a workflow or subworkflow, I use my own extension package I created based on APEX_HUMAN_TASK, which performs something like this:

1. Detaches from the current user session
2. Creates an APEX session as MY_SYSTEM_USER
3. Executes the delegate_task operation and logs information that the technical user MY_SYSTEM_USER was used to delegate this task
4. Detaches and deletes the MY_SYSTEM_USER session
5. Attaches back to the main user session

Preferred Solution (Optional)
I see two solutions:

1. Simple IF statement based on parameter. If p_bypass_permission_check = true, avoid checking permissions. I'm not sure what the complications are with this approach, as you probably need to log who performed the operation in some way.
2. Add preconfigured, static background user for each Human Task definition. If p_bypass_permission_check = true, use this user to perform BA-restricted or Actual Owner-resticted operations.