Quantcast
Channel: SCN : Unanswered Discussions - SAP Gateway
Viewing all articles
Browse latest Browse all 1745

Filter Gateway workflow tasks in HR Renewal approval chip

$
0
0

Hi,

 

We have a setup consisting of a system with a local GW for running our HR Renewal setup on our ECC system.

I the IMG as seen in the step1 attachment below. we have updated this according to SAP specifications but with the filter active(Enable Task Filter in IMG) this should filter the WF list so only steps corresponding to the filter list is shown.

 

step1.png

 

This is not the case which I find confusing - If I read the doc for this IMG step then it clearly states that:

 

Maintain Task Names and Decision Options

Use

This activity allows you to maintain workflow tasks that need to be included in the task filter together with their names and decision keys.

These customizations are relevant when the filter is active. When the filter is  not active, all workflow items are read and all notifications are sent.

 

Activities

You can add workflow tasks and their corresponding IDs to the workflow task filter. If the filter is active,  only the workflow items maintained in this list are included in the query results. Notifications are sent to the SAP NetWeaver Gateway only for these items.

You can define a name to be displayed when reading a specific task. Names can be maintained in several languages. You can add names only in the language in which you logged on to the system. If a task is read in a specific language in which no name is maintained, the name will be read according to the system kernel language. If no name is maintained for the system kernel language, the name will consist of the workflow and step ID.

 

so with the filter active only WF with these steps as defined should appear in the users worklist - But due to Fiory I have inserted a decision step in a Fork setup with one of the existing activities and the decision step should be shown in our Fiori setup and the other should be shown in our HR Renewal approval setup.

 

In our Fiori Gateway(which is running on a separate system) we have defined Scenario ID as seen in picture step2 below. in the attached word doc and this works as the scenario ID can be passed to the fiori app and therefor is called during inbox retrival. so on Fiori only those two tasks that are defined are shown.

 

I guess setting up the Scenario ID on the ECC GW could be an option and then pass the the scenarioID from inside the BSP Approval javascript code, but that is just one idea.

 

I really dont understand why the IMG entry does not work as SAP's own doc states it should :-S

 

step2.png


Viewing all articles
Browse latest Browse all 1745

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>