Customizing Task Title in GP - passing info from Process to Process

[Former Member]

Hello,

I have a scenario where there are 4 sequential blocks. The first block has two actions. In the first action, I call a VC app that sends a PO number to an endpoint which I then take and display in the second action task title. That part is no problem.

The problem is when I want to use that same PO number in the second process block in the first action. Its not a required field, or a list, so I created an additional parameter and referenced that in the customized task title reference.

Next I mapped the PO num from the first process block, 1st step to my new additional parameter in the second block, first action. I also should mention that the first step of the second block is a call to a VC app that expects the PO number in the starting point.

When I run the GP, the PO number shows up in the VC app but NOT the task title. I've tried several combination's of mapping from the first block but so far nothing will allow me to use that PO number in the title.

It seems like once the 'variable' is populated in the process block I can use it to display in the task title but I cant pass it into that same variable from block to block.

Any ideas?

[Former Member]

Hi Mike,

i've been experimenting the same problem... parameters mapping in Guided Procedures behaves buggy some times...

Mixing "additional parameters" with input/output parameters from VC Callable Objects always brought me trouble.

In the first action of block 1 you should create more outputs : po1 , po2 , po3... all containing exactly the same value and create the same amount of input additional parameters(always as "required" and no "list") , for example ttitle1 as input in action 2 block1 , ttitle2 as input in action3 block2 ,ttitle as input in action4 and so on...

Then, at block1 level you have to consolidate the first pair of parameters,

block 1 : map (po1 -> ttitle1) IN group"map1"

In the rest of the blocks block group all of the additional parameters at block level(wich are all inputs).

block 2: map (ttitle2 , title3) IN group "map2"

block 3 .. the same..

then at process level consolidate ALL the parameters together in the same group:

Process level: map (map1, map2, map3...po2,po3..) IN group "totalMapping".

Give it a try,

Regards,

Marco.

[Former Member]

I'm stuck on the first part of your instructions. How do I create more outputs? When I am in edit mode, and click on my callable object for the VC line, I navigate to the output of that object. There is no 'insert' new parameters there.

The only outputs that show up in the list are what we defined in the VC endpoint.

I can add a additional parameter to the action. This gets marked as 'exposed in'.

EDIT:

I found this

http://help.sap.com/saphelp_nw04s/helpdata/en/e4/8a5742330ad142e10000000a1550b0/frameset.htm

Edited by: Mike Marowski on Dec 2, 2008 7:44 PM

[Former Member]

ok, step by step, here is what I did....

1) Create a new process, called 'Purchase Order'

2) Create 2 sequential blocks, "Create PO" and "Work with PO"

3) In Create PO, create 2 actions "Input PO Information" and "View Results"

4) In "Work with PO", create action "Stock Overview"

5) In "Input PO Information" create callable object named "Stock Request", type WDP4VC. I pick my VC app from here. I use all of the defaults. No start point, but an endpoint called 'PurchDoc' appears.

6) In "View Results", create callable object named "Display Results", type Webdynpro form. I add input filed, "fldPONum" and a button "butNext"

7) I select the process and map 'PurchDoc' to 'fldPONum', into a group called 'blockCreatePO.PONum'

😎 In "Stock Overview", create callable object named "StockReview", type WDP4VC. I pick my VC app from here. I use all of the defaults. Starting point shows a complex structure, but the value 'PurchaseOrderID' is in there. An endpoint also appears that has some PO related data.

9) I go back and set the Result states for each action to the next action in line, with the last action pointing to 'no target'.

10) I then go to the Process level, "Purchase Order", and select the parameters tab. I group 'blockCreatePO.PONum' and 'PurchaseOrderID' into 'procPurchaseOrder.PONum'.

11) I also remove the flags for 'Exposed In' at the process level because I do not want to populate these values when I kick off the GP during runtime.

12) I update all of the roles at the process level to 'Initiator' and then select the 'Process Started Automatically' from the Instantiation tab.

13) I go back to the parameters page and notice that SAP has rechecked my exposed in for my procPurchaseOrder.PONum' group. I uncheck this.

14) I activate my GP and related objects.

15) I kick off my GP. The PO number shows up correctly in my 'View Results' step. I click my next button. The PO number shows up correctly in my 'Stock Overview' VC app.

• At this point I know I can pass the parameter between blocks ***

16) Next, I go back and edit all of the objects.

17) I then go into the "Stock Overview' action and notice that there is nothing I can add because I do not have anything that is required and not a list. I change to the parameters tab and click additional parameters, and then insert new. I add a new one called 'addPONUm', set the technical name to the same thing, and mark it required. I hit apply. Whats interesting here is that the parameter says its defined for 'action 3' instead of 'stock overview', even though I am in the correct place. This is a sap bug.

18) I navigate back to the task tab, click on 'customize task title' and see my new additional parameter listed. I select it, and choose append parameter. I click on Verify and get a 'text pattern is valid'.

19) I activate the action only.

20) I then go back to the process level parameter, and see that my new 'addPONum' is listed. I select that and 'procPurchaseOrder.PONum' and then 'add to group'.

21) I activate everything.

22) I then go back and try to run the GP again. The PO number shows up correctly in my 'View Results' step. I click my next button. The PO number shows up correctly in my 'Stock Overview' VC app but NOT in the task title.

[Former Member]

The next thing I tried is to create an additional parameter earlier in the process...

23) In 'Input PO', create additional parameter 'addPurchDoc'. Set it to required.

24) I go to the block level and add 'addPurchDoc' to 'blockCreatePO.PONum'.

25) I go to process level and check to see if anything is changed. Since 'blockCreatePO.PONum' is already part of an existing grouping, I am all set.

26) I activate everything.

27) I execute my GP doing the same thing as before. And of course, the results are the same. PO number correctly goes into my start point of the next callable object, but the task name is unchanged.

Ideas?

[Former Member]

I also should mention that we are at CE 7.1. SP6

[Former Member]

I'm opening an OSS note about this. Ive done some further testing and have found that I can get the task title to display the parameter depending on the sequence that the task 'customizing a task title' check mark is used and activated. I will update this thread after I get results.

[Former Member]

Here's how to reproduce (and fix) the error:

1) open the GP in design mode. Select the task that you want to display the parameter.

2) Navigate to the task page. Click on the task tab. Notice that there is an 'AdditionalParameters' twistie with the additional parameter listed

3) Uncheck the Customize Task Title checkbox.

4) Recheck the Customize Task Title checkbox. Notice that the 'AdditionalParameters' twistie is gone and the additional parameter listed like a normal parameter. Select the parameter in that is displayed.

5) Append, Verify, and Activate. The task will now display the parameter correctly.

6) Edit the action and go back the same task. Notice that the system now complains that there is an invalid text expression and that the 'AdditionalParameters' twistie is back. It complains because the string that you added should have come from the selection listed under the twistie. If you use this string, you will not be able to get the value to be displayed. To fix it go to the next step.

7) Repeat step 3,4, and 5 now instead of 'fixing it'

[Former Member]

how you are customizing the task title?

if you are doing that customization code in GP desisn time,the parameter which you are using to customize the task title should be required parameter.

pls check that

Thanks and Regards

shanto aloor

[Former Member]

Im customizing it pretty much like I described in the first post.

To customize a task title, you need to pick a parameter that is NOT a list and IS required. Unfortunately, my first action in the block is a Visual Composer application and the start point is a list and is not required.

Therefore, the workaround is to create an additional parameter and set that to not a list and is required. I can then go into the task customization and select that parameter to be displayed in the task title.

The last step is to give that parameter a value (right now it just a placeholder). To do that, I mapped/grouped a parameter out of the previous process block (last action) and into the new parameter I defined.

I also needed the same value to be sent into the start point of my vc app. That value gets displayed on a form. I used the same parameter from the previous block and created a new group. I could have used the same group but I wanted to keep these separate for design considerations.

When I run the GP, the parameter displays the value in the VC app but not the task title. I know that the value is correctly being passed into the second process block this way.

I've tried using a single group with and have got the same results. I've even tried creating a new additional parameter in the first process block and mapping it to the parameter I created earlier.