What sets task.approval to Requested when approval is started via Approval - User WF activity?

[Jacob Hancock]

When task approval is started via Workflow using the Approval - User activity, what out-of-the-box functionality changes the task.approval value to 'Requested'?

We recently created two new tables which extend task in two separate custom, scoped applications.  We created workflow for each of those tables using the Approval - User activity.  Everything works correctly EXCEPT when the approvals are created, the approval field does not change to 'Requested'.  All of the created sysapproval_approver records show state of Requested.  When approvals are approved or rejected, the approval field on the extended tables properly changes to Approved or Rejected.

I realize that I could add a Set Value activity in the workflow before the Approval - User activity, but I would really like to understand what out-of-the-box feature normally sets this value and why it isn't working in the extended tables.

[Allen Andreas]

In my workflows this is done in the initial start of it whereby the activity sets this:

I would imagine, you'd do the same?

Please mark reply as Helpful/Correct. Thanks!

[Jacob Hancock]

Thank you for your input, however, that is the same workaround that I stated I know I can use.  This is does not answer the question.

[Allen Andreas]

Hi,

The purpose of my reply was to show and tell you what I do...so...I'm not seeing where it is being set OOB by the system normally, I can't recall it doing that and I was showing you what I do. We have a very large community here, so if you're getting responses back saying: "well I do this and I do this"...then that may mean that it's an understood way of doing things. Hence why the two responses you got back from two different people are saying the same thing.

So...as far as your "question"...I don't think it's a question that is from a problem that actually exists...I don't think there's an OOB method that is working for core tables and just now not working for your extended tables.

I could be wrong...but honestly, adding the activity, marking it as requested and moving on, may be the best option.

Thanks so much!

[Daniel Plunkett]

Jacob,

On the workflow, you can use what's called an Approval action to set the task.approval field to requested. One of the options is Mark Task Requested. Approval actions are in the same group