Anonymous_User Absent Member.
Absent Member.
140 views

Re: Creating Workflow composed of two or more steps

Yes, this should work if the "Deny" flow path does not skip the 3rd
approver.

You might want to double-check what happens when the first admin presses
"Deny" on the external interface and verify the APIs used.
Each approval step should have a unique work id.

Wolfgang

On 04.05.2012 15:16, stavae wrote:
>
>
> I was thinking --- what if I modify my workflow, so that : after the
> "First" and "Second" Approvals, *_BOTH__* the _approve_ and _deny_
> flow-arrows will always continue to the next Approval ??
>
> In other words : after First Approval, whether or not the action is
> "Approved" or "Denied", the process moves forward to the Second
> Approval, etc, etc
>
>

Labels (1)
0 Likes
1 Reply
Anonymous_User Absent Member.
Absent Member.

Re: Creating Workflow composed of two or more steps

On 05/04/2012 10:42 AM, Wolfgang Schreiber wrote:
> Yes, this should work if the "Deny" flow path does not skip the 3rd
> approver.
>
> You might want to double-check what happens when the first admin presses
> "Deny" on the external interface and verify the APIs used.
> Each approval step should have a unique work id.
>
> Wolfgang
>
> On 04.05.2012 15:16, stavae wrote:
>>
>>
>> I was thinking --- what if I modify my workflow, so that : after the
>> "First" and "Second" Approvals, *_BOTH__* the _approve_ and _deny_
>> flow-arrows will always continue to the next Approval ??
>>
>> In other words : after First Approval, whether or not the action is
>> "Approved" or "Denied", the process moves forward to the Second
>> Approval, etc, etc
>>
>>

Greetings,
You should remove the deny paths in the workflow itself and the deny
button (I believe that will happen when you remove the deny paths) from
the 1st and 2nd Approvers. This will ensure that workflow will always
follow the Approve path for the case of Timed-out action and it is the
only action available for your 1st and 2nd approvers (it does not matter
the interface)

--
Sincerely,
Steven Williams
Lead Software Engineer
NetIQ
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.