cancel
Showing results for 
Search instead for 
Did you mean: 

Workflows dependend on user attributes/input

Former Member
0 Kudos

I would like to ask two questions:

1. Is there a possibility to hide tasks from users who don't have access rights to them? Like, a task "Select Customer" which should be only visible to Sales Persons (could be that the "department" attribute is being filtered or even a special attribute being used for that)?

2. Is there a possibility to make a input dependent workflow?

Like, in the example above, one user would be want to change his responsibilities for the customer "Walmart" and Walmart's Department "Beverages" and to the customer "Target" and their Department "Cosmetics".

First, he would select the customer (=single select), second, he would then select the department <b>dependent on which customer he has chosen</b>.

This would then be to be approved by managers associated with the different customers.

Message was edited by:

Thomas P. Felder

Accepted Solutions (0)

Answers (2)

Answers (2)

Frank_Buchholz
Advisor
Advisor
0 Kudos

1. Is there a possibility to hide tasks from users who don't have access rights to them? Like, a task "Select Customer" which should be only visible to Sales Persons (could be that the "department" attribute is being filtered or even a special attribute being used for that)?

Yes, that's standard functionality of SAP NetWeaver Identity Management: On the tab 'Access control' you can simply assign a privilege to a web enabled task to only show this task to identities who are assigned to that privilege.

In addition to that you can configure more sophisticated filters or even code a complex rule for defining who is able to view that web enabled task .

2. Is there a possibility to make a input dependent workflow?

Like, in the example above, one user would be want to change his responsibilities for the customer "Walmart" and Walmart's Department "Beverages" and to the customer "Target" and their Department "Cosmetics".

First, he would select the customer (=single select), second, he would then select the department dependent on which customer he has chosen.

This would then be to be approved by managers associated with the different customers.

Up to now, I've seen only one-screen workflow tasks.

However, requesting the approval from a manager of the customer, which is handled by the work item, is possible: Like above you use the filters on the 'Access control' tab to define who sees a work item.

Kind regards

Frank Buchholz

Former Member
0 Kudos

Hi Frank,

thanks, you're right with the 1st answer, naturally.

Message was edited by:

Thomas P. Felder

Former Member
0 Kudos

How about defining of business roles based on ROLE:WALLMART:BEVERAGES and ROLE:TARGET:COSMETICS.

I can't see a business use of having a user assigned just a "top node" role like ROLE:WALLMART. This would require some work, but since you can limit the search results by parameters, then this would compound the two-step workflow into a single step?

Cheers,

Eric

Former Member
0 Kudos

Hi Eric,

these roles would be assigned, in the end, true.

But for ease of user interaction, they want them to select customer first and than his responsibility with this specific customer.

Here's an official answer to the problem from Kare:

"What we usually implement when we have this type of requests, is a new entry-type (Request-entry-type).

The way we implement this is that for each request, we create a new entry, with status-info, who did the request, what the request was about, and so on. You are free to add any required info into this entry-type.

When a new request-entry is added, additional tasks will be visible for the user, and he can then list request-objects, in different stages, available and carry on the request until it comes to the final stage.

When the request is finalized, the execution is executed, and the request-object deleted."

Former Member
0 Kudos

Hi Thomas,

Iteresting take on the issue, nice idea.

Former Member
0 Kudos

Run the corresponding "Select Customer" tcode, and find out the Authorization Object using SU53 and restrict users from using the Authorization Object.

regards

tamilboy

Former Member
0 Kudos

Hi tamilboy,

unfortunately, the SAP NetWeaver Identity Center doesn't know tcodes, as it is a just recently bought in former 3rd party product.

But thanks anyway.