AnsweredAssumed Answered

Group Owner not added to group approval request

Question asked by Shlomo Katz on Mar 21, 2018
Latest reply on Mar 26, 2018 by Shlomo Katz

Like • Show 0 Likes0
Comment • 4

Environment:

7.0.2 Patch 4

Appliance

I have a similar problem as another thread (search: Approval Workflow - Approve By Group Owner - Not working). however, the process works in Dev environment but not in Production.

Resource: Application - High Risk Groups

High Risk AD groups are marked with a special attribute and then collected under the High Risk Groups application.

User then make a request to the High Risk Group from the HRG application NOT the Active Directory Directory.

The Approval workflow then pulls the Group Owner for approval.

This is working great in Dev, so I exported the Application and WF to Prod - but Prod cannot find the group owner so it goes to system approval by default.

So , I deleted the Dev application, and export/import Prod to Dev - but Dev worked again without any changes.

The only other difference that I see is that the run-time data in the Dev request adds the following Interation1 value with the group owner, where Production does not.

Any thoughts?

Shlomo Katz Mar 26, 2018 12:01 PM

Correct Answer

This was resolved by recreating the workflow as the imported workflow is corrupt.

See the reply in context

No one else had this question

Outcomes

Boris Lekumovich

Mar 21, 2018 6:42 PM

Does the relevant high risk groups have collected and resolved owners (which are not terminated/deleted)?

How is the approval node configured? Can you share a screenshot?

Actions

Shlomo Katz @ Boris Lekumovich on Mar 22, 2018 8:13 AM

Hi Boris

The collected groups show the owner and the owner is not terminated and again, this is set up the same way in Dev and it works.

It is a simple approval workflow:

The Group Owner Approval (I have tried all three options):

Which is mapped to :

Actions

Boris Lekumovich

@ Shlomo Katz on Mar 22, 2018 9:23 PM

It might work in DEV but in PROD you have most likely different data collected.

Is it possible that the group owner is part of the exclude list?

In the Include configuration, where you have configured the group owner, I would try to add another static approver, create the same request and observe what happens.

Check the logs for errors as well.

Actions

Shlomo Katz Mar 26, 2018 12:01 PM

This was resolved by recreating the workflow as the imported workflow is corrupt.

Actions

4 Replies

Boris Lekumovich Mar 21, 2018 6:42 PM
Mark Correct
Correct Answer
Does the relevant high risk groups have collected and resolved owners (which are not terminated/deleted)?
How is the approval node configured? Can you share a screenshot?
Like • Show 0 Likes0
Actions
- Shlomo Katz @ Boris Lekumovich on Mar 22, 2018 8:13 AM
  Mark Correct
  Correct Answer
  Hi Boris
  The collected groups show the owner and the owner is not terminated and again, this is set up the same way in Dev and it works.
  It is a simple approval workflow:
  
  The Group Owner Approval (I have tried all three options):
  Which is mapped to :
  Like • Show 0 Likes0
  Actions
  - Boris Lekumovich @ Shlomo Katz on Mar 22, 2018 9:23 PM
    Mark Correct
    Correct Answer
    It might work in DEV but in PROD you have most likely different data collected.
    
    Is it possible that the group owner is part of the exclude list?
    
    In the Include configuration, where you have configured the group owner, I would try to add another static approver, create the same request and observe what happens.
    
    Check the logs for errors as well.
    Like • Show 0 Likes0
    Actions
Shlomo Katz Mar 26, 2018 12:01 PM
Unmark Correct
Correct Answer
This was resolved by recreating the workflow as the imported workflow is corrupt.
Like • Show 1 Like1
Actions

Group Owner not added to group approval request

Outcomes

Related Content

Recommended Content