Update 2011

* Stage 2011

* Update Draft Bindings (V4) 
Update Managed BDEF

* Delete #dmo#ui_travel_d_d.srvb.xml

* Delete #dmo#ui_travel_a_d.srvb.xml

* Update ReadMe with Service Binding Specifics

* Update README.md

Author: MarinaBlank

.abapgit.xml

@@ -28,6 +28,10 @@
     <item>/src/unmanaged/#dmo#i_travel_u.bdef.xml</item>
     <item>/src/unmanaged/#dmo#travel_u.srvd.srvdsrv</item>
     <item>/src/unmanaged/#dmo#travel_u.srvd.xml</item>
+    <item>/src/draft/#dmo#ui_travel_a_d.srvb.xml</item>
+    <item>/src/draft/#dmo#ui_travel_a_d.srvd.srvdsrv</item>
+    <item>/src/draft/#dmo#ui_travel_d_d.srvb.xml</item>
+    <item>/src/draft/#dmo#ui_travel_d_d.srvd.srvdsrv</item>
    </IGNORE>
   </DATA>
  </asx:values>

README.md

@@ -20,10 +20,10 @@ Use the abapGit plug-in to install the <em>ABAP Flight Reference Scenario</em> b
 2. To add the <em>abapGit Repositories</em> view to the <em>ABAP</em> perspective, click `Window` > `Show View` > `Other...` from the menu bar and choose `abapGit Repositories`.
 3. In the <em>abapGit Repositories</em> view, click the `+` icon to clone an abapGit repository.
 4. Enter the following URL of this repository: `https://github.com/SAP-samples/abap-platform-refscen-flight.git` and choose <em>Next</em>.
-5. Select the branch <em>Cloud-Platform</em> and enter the newly created package `/DMO/FLIGHT` as the target package.
+5. Select the branch <em>Cloud-Platform</em> and enter the newly created package `/DMO/FLIGHT` as the target package and choose <em>Next</em>.
 6. Create a new transport request that you only use for this demo content installation (recommendation) and choose <em>Finish</em> to link the Git repository to your ABAP cloud project. The repository appears in the abapGit Repositories View with status <em>Linked</em>.
 7. Right-click on the new ABAP repository and choose `pull` to start the cloning of the repository contents. Note that this procedure may take a few minutes. 
-8. Once the cloning has finished, the status is set to `Pulled Successfully`. Then refresh your project tree. 
+8. Once the cloning has finished, the status is set to `Pulled Successfully`. (Refresh the `abapGit Repositories` view to see the progress of the import). Then refresh your project tree. 
 
 As a result of the installation procedure above, the ABAP system creates an inactive version of all artifacts from the demo content and adds the following sub packages to the target package: 
 * `/DMO/FLIGHT_LEGACY`
@@ -39,12 +39,11 @@ NOTE: The service bindings of the develop scenarios are imported with the warnin
 
 To activate all development objects from the `/DMO/FLIGHT` package: 
 1. Click the mass-activation icon (<em>Activate Inactive ABAP Development Objects</em>) in the toolbar.  
-2. In the dialog that appears, select all development objects in the transport request (that you created for the demo content installation) and choose `Activate`.
+2. In the dialog that appears, select all development objects except for all service binding artifacts (`/DMO/UI_FLIGHT_R_V2` , `/DMO/UI_TRAVEL_PROC_M_O2`, `/DMO/UI_TRAVEL_APPR_M_O2`, `/DMO/UI_TRAVEL_U_V2`, and `/DMO/API_TRAVEL_U_V2` `/DMO/UI_TRAVEL_A_D`, `/DMO/UI_TRAVEL_D_D`)in the transport request (that you created for the demo content installation) and choose `Activate`. 
+3. Service bindings can only be activated once the underlying service definition is activated. To activate each service binding separately open them and choose the `Activate` button.
 
 To generate service artifacts for the service bindings:
-1. Open the service bindings: `/DMO/UI_FLIGHT_R_V2` , `/DMO/UI_TRAVEL_PROC_M_O2`, `/DMO/UI_TRAVEL_APPR_M_O2`, `/DMO/UI_TRAVEL_U_V2`, and `/DMO/API_TRAVEL_U_V2` `/DMO/UI_TRAVEL_A_D`, `/DMO/UI_TRAVEL_D_D`.
-2. In each service binding editor, choose `Generate service artifacts` in the top left corner of the editor. 
-3. In each service binding, choose the button `Activate` or choose `Activate local service endpoint` in the top right corner of the editor.
+1. In each service binding, choose the button `Publish` or choose `Publish local service endpoint` in the top right corner of the editor.
 
 To fill the demo database tables for the read-only and the unmanaged scenario with sample business data: 
 1. Expand the package structure in the Project Explorer `/DMO/FLIGHT_LEGACY` > `Source Code Library` > `Classes`.