Automate

Problem Description

I need to add a new form element to an existing Form Group inside a Winshuttle Solution.  In this instance, I need to add a Dropdown List Box that binds to a set of Labels and Values from a SharePoint List.  All the existing Form Group elements are bound to a Transaction Script that posts all the values to an SAP Web Service call.  In order to use an updated version of the Transaction Script to post the values back through the Web Service call, I am trying to add the new Dropdown List Box to the same Form Group's Parent XPath.  However, the approaches  I have tried result in the new Dropdown List Box being added to a different XPath group and not the parent XPath for the existing form group.  I would appreciate any help or suggestions with the following question:

Is it possible to add a new Form Group element, be it a Textbox, Dropdown List box or any other Basic Element to an Existing Form Group and have the new Form Group Element referenced in the same XPath Parent path for the Form Group?

Problem Details

My existing Form Group, named Sales Area, has its form group element values referenced in the XPath /my:myFields/my:SalesArea/my:SalesArea_Input/my:RunParameter_1/.  For example, the Customer Segmentation value Dropdown List Box in the form group has the XPath value of /my:myFields/my:SalesArea/my:SalesArea_Input/my:RunParameter_1/my:BP__Legal_form_of_organization_1

I am trying to add a new Dropdown List Box to the Sales Area form group for the user to select a Warranty Period, as shown in the updated screenshot below:

All Sales Area Form Group values are posted to SAP through a Web Service named BP_SalesArea_xml, and all Transaction Script bindings for the Form Group are done through the parent XPath /my:myFields/my:SalesArea/my:SalesArea_Input/my:RunParameter_1.  As shown in the Field Mapping Parameters dialog box below, the Customer Segmentation value with the XPath  /my:myFields/my:SalesArea/my:SalesArea_Input/my:RunParameter_1/my:BP__Legal_form_of_organization_1 is mapped to the Transaction Script Web Service Field BP__Legal_Form_Of_Organization:

When I add the Warranty Field Dropdown List Box to the Sales Area form group, I was expecting to see its XPath reference the same parent XPath /my:myFields/my:SalesArea/my:SalesArea_Input/my:RunParameter_1, with an XPath for the new Dropdown List Box resembling /my:myFields/my:SalesArea/my:SalesArea_Input/my:RunParameter_1/my:Warranty_Period.  However, after adding the Warranty Period Dropdown List Box to the form group, its parent XPath now references /my:myFields/ instead of what I had expected, /my:myFields/my:SalesArea/my:SalesArea_Input/my:RunParameter_1/.  The Composer assigned XPath value for the new Dropdown List Box is /my:myFields/my:Warranty_Period

While trying to update the Web Service Transaction Script's Web Service Field Mappings and enter the automatically assigned XPath for the Dropdown List Box, /my:myFields/my:Warranty_Period, with the Use Existing Input and Output Fields checkboxes enabled, the Field Mapping Parameters own Dropdown List Box shows the error message No Matches Found:

Is there a way to add the Warranty Period Dropdown List Box to the Sales Area form group for all Form Views in my solution that can be correctly set and used as a Field Mapping Parameter Value to my updated Web Service call?  

Thank you in advance for your time, help and patience.

I think I may have found the solution.   When defining the Field Mapping Parameters for the new Warranty Field, I just had to specify the XPath Field Name, and NOT the entire or "fully qualified" XPath value.   The actual dropdown list XPath is /my:myFields/my:DS_S_Warranty.  In the Form Field mapping box, i had to just add the XPath field name my:DS_S_Warranty as shown below:

My mistake was thinking that I had to add the full explicit XPath value for the Dropdown List Box's field value.  But then I realized that when Composer assigns XPath values to Form Element Values of any type within a form, the Full XPath value is unique, and that the Field  Mapping Parameters dialog box shown above just needs the XPath field name to find and bind the full mapping value.  Is this correct?

Original Message:
Sent: 11-26-2019 11:39
From: Bill Wonneberger
Subject: How To Add a New Form Group Element to an Existing For Group to Keep the Same Group XPath Bindings in a Web Service Transaction Script Using Composer 12

Problem Description

I need to add a new form element to an existing Form Group inside a Winshuttle Solution.  In this instance, I need to add a Dropdown List Box that binds to a set of Labels and Values from a SharePoint List.  All the existing Form Group elements are bound to a Transaction Script that posts all the values to an SAP Web Service call.  In order to use an updated version of the Transaction Script to post the values back through the Web Service call, I am trying to add the new Dropdown List Box to the same Form Group's Parent XPath.  However, the approaches  I have tried result in the new Dropdown List Box being added to a different XPath group and not the parent XPath for the existing form group.  I would appreciate any help or suggestions with the following question:

Is it possible to add a new Form Group element, be it a Textbox, Dropdown List box or any other Basic Element to an Existing Form Group and have the new Form Group Element referenced in the same XPath Parent path for the Form Group?

Problem Details

The visual layout of the Sales Area Form Group resembles the following:

My existing Form Group, named Sales Area, has its form group element values referenced in the XPath /my:myFields/my:SalesArea/my:SalesArea_Input/my:RunParameter_1/.  For example, the Customer Segmentation value Dropdown List Box in the form group has the XPath value of /my:myFields/my:SalesArea/my:SalesArea_Input/my:RunParameter_1/my:BP__Legal_form_of_organization_1

I am trying to add a new Dropdown List Box to the Sales Area form group for the user to select a Warranty Period, as shown in the updated screenshot below:

All Sales Area Form Group values are posted to SAP through a Web Service named BP_SalesArea_xml, and all Transaction Script bindings for the Form Group are done through the parent XPath /my:myFields/my:SalesArea/my:SalesArea_Input/my:RunParameter_1.  As shown in the Field Mapping Parameters dialog box below, the Customer Segmentation value with the XPath  /my:myFields/my:SalesArea/my:SalesArea_Input/my:RunParameter_1/my:BP__Legal_form_of_organization_1 is mapped to the Transaction Script Web Service Field BP__Legal_Form_Of_Organization:

When I add the Warranty Field Dropdown List Box to the Sales Area form group, I was expecting to see its XPath reference the same parent XPath /my:myFields/my:SalesArea/my:SalesArea_Input/my:RunParameter_1, with an XPath for the new Dropdown List Box resembling /my:myFields/my:SalesArea/my:SalesArea_Input/my:RunParameter_1/my:Warranty_Period.  However, after adding the Warranty Period Dropdown List Box to the form group, its parent XPath now references /my:myFields/ instead of what I had expected, /my:myFields/my:SalesArea/my:SalesArea_Input/my:RunParameter_1/.  The Composer assigned XPath value for the new Dropdown List Box is /my:myFields/my:Warranty_Period

 

While trying to update the Web Service Transaction Script's Web Service Field Mappings and enter the automatically assigned XPath for the Dropdown List Box, /my:myFields/my:Warranty_Period, with the Use Existing Input and Output Fields checkboxes enabled, the Field Mapping Parameters own Dropdown List Box shows the error message No Matches Found:

Is there a way to add the Warranty Period Dropdown List Box to the Sales Area form group for all Form Views in my solution that can be correctly set and used as a Field Mapping Parameter Value to my updated Web Service call?  

Thank you in advance for your time, help and patience.

------------------------------
Bill Wonneberger
bill.wonneberger@versummaterials.com
------------------------------