fix: update READMEs with new agent changes

Author: muenzpraeger

force-app/main/02_actionConfiguration/actionDefinitions/README.md

@@ -224,7 +224,7 @@ get_forecast:
       days: number
          description: "Number of days to include in the forecast (1-10)"
    outputs:
-      forecast_data: list[object]
+      forecast_data: list[string]
          description: "List of daily forecast objects containing temperature, conditions, and precipitation data"
    target: "flow://GetWeatherForecast"
 ```
@@ -259,6 +259,16 @@ reasoning:
       else:
          | - Location: None specified
 
+      if @variables.current_temperature > 0:
+         | - Temperature: {[email protected]_temperature}
+      else:
+         | - Temperature: Not fetched
+
+      if @variables.conditions:
+         | - Conditions: {[email protected]}
+      else:
+         | - Conditions: Not fetched
+
       | When a user asks about weather:
         1. Identify the location they're asking about
         2. Use {[email protected]_current_weather} to fetch current conditions

force-app/main/04_architecturalPatterns/multiTopicNavigation/README.md

@@ -75,8 +75,8 @@ Move between topics using `@utils.transition to @topic.name`:
 ```agentscript
 reasoning:
    actions:
-      proceed_to_booking: @utils.transition to @topic.hotel_booking
-         description: "Move to booking when user wants to reserve a hotel"
+      browse_hotels: @utils.transition to @topic.hotel_browse
+         description: "Browse and search for available hotels"
 ```
 
 ### Conditional Transition Availability
@@ -98,27 +98,11 @@ Transition after an action completes using `transition to`:
 actions:
    create_booking: @actions.create_booking
       with hotel_name=...
-      with [email protected]_in_date
-      with [email protected]_out_date
-      set @variables.hotel_name = @inputs.hotel_name
-      set @variables.booking_id = @outputs.booking_id
-      set @variables.booking_confirmed = True
-      # Automatically move to confirmation after booking
-      transition to @topic.hotel_confirmation
-```
-
-### Storing Action Inputs
-
-Capture inputs that the LLM provides:
-
-```agentscript
-actions:
-   search_hotels: @actions.search_hotels
-      with location=...
       with check_in=...
       with check_out=...
-      set @variables.check_in_date = @inputs.check_in
-      set @variables.check_out_date = @inputs.check_out
+      set @variables.booking_id = @outputs.booking_id
+      set @variables.booking_confirmed = @outputs.success
+      transition to @topic.hotel_confirmation
 ```
 
 ## Key Code Snippets
@@ -141,36 +125,29 @@ topic hotel_browse:
                description: "Check-out date in ISO format (YYYY-MM-DD)"
          outputs:
             hotels: list[object]
-               description: "List of available hotel objects"
+               description: "List of available hotel objects with name, price, rating, and amenities information"
+               complex_data_type_name: "lightning__recordInfoType" # This is the name of the complex data type that is used to store the hotel objects
          target: "flow://SearchHotels"
 
    reasoning:
       instructions:->
-         | Help users find the perfect hotel.
-
-           Current search criteria:
+         | Help users find the perfect hotel using {[email protected]_hotels}.
 
-         if @variables.check_in_date:
-            | - Check-in: {[email protected]_in_date}
-         else:
-            | - Check-in: Not set
+           Ensure to ask the user for:
+           - location
+           - check-in date
+           - check-out date
 
-         if @variables.check_out_date:
-            | - Check-out: {[email protected]_out_date}
-         else:
-            | - Check-out: Not set
+           Do not ask for other booking details.
 
-         | When users are ready to book, use the proceed_to_booking action.
+           If you find available hotels provide the user the hotel information.
 
       actions:
          search_hotels: @actions.search_hotels
             with location=...
             with check_in=...
             with check_out=...
             transition to @topic.hotel_booking
-
-         proceed_to_booking: @utils.transition to @topic.hotel_booking
-            description: "Move to booking when user wants to reserve a hotel"
 ```
 
 ### Complete Topic: Hotel Booking
@@ -186,31 +163,19 @@ topic hotel_booking:
             hotel_name: string
                description: "Name of the hotel to book"
             check_in: string
-               description: "Check-in date"
+               description: "Check-in date in ISO format (YYYY-MM-DD)"
             check_out: string
-               description: "Check-out date"
+               description: "Check-out date in ISO format (YYYY-MM-DD)"
          outputs:
             booking_id: string
                description: "Unique booking confirmation identifier"
             success: boolean
-               description: "Whether the booking was created successfully"
+               description: "Indicates whether the booking was created successfully"
          target: "flow://CreateBooking"
 
    reasoning:
       instructions:->
-         | Complete the booking for the customer.
-
-           Booking details:
-
-         if @variables.hotel_name:
-            | - Hotel: {[email protected]_name}
-         else:
-            | - Hotel: Not selected
-
-         | - Check-in: {[email protected]_in_date}
-           - Check-out: {[email protected]_out_date}
-
-         | Once booking is complete, transition to hotel_confirmation topic.
+         | Complete the booking for the customer using {[email protected]_booking}.
 
       actions:
          create_booking: @actions.create_booking
@@ -220,9 +185,6 @@ topic hotel_booking:
             set @variables.booking_id = @outputs.booking_id
             set @variables.booking_confirmed = @outputs.success
             transition to @topic.hotel_confirmation
-
-         go_to_confirmation: @utils.transition to @topic.hotel_confirmation
-            description: "Move to confirmation after successful booking"
 ```
 
 ### Complete Topic: Hotel Confirmation
@@ -240,7 +202,7 @@ topic hotel_confirmation:
            - Hotel: {[email protected]_name}
            - Check-in: {[email protected]_in_date}
            - Check-out: {[email protected]_out_date}
-
+  
            Provide these details to the customer and ask if they need anything else.
            If they want to make another booking, use start_new_booking action.
 
@@ -275,7 +237,7 @@ User: I'll take the Bay View Hotel
 Agent: Excellent choice! Let me help you book the Bay View Hotel.
 ```
 
-**[Agent calls proceed_to_booking → transitions to hotel_booking]**
+**[Agent calls search_hotels action → transitions to hotel_booking]**
 
 ```text
 Agent: I'm ready to complete your booking at Bay View Hotel.
@@ -351,8 +313,8 @@ Good for: Exploratory interfaces, comparison shopping
 **Good:**
 
 ```agentscript
-proceed_to_booking: @utils.transition to @topic.hotel_booking
-   description: "Move to booking when user wants to reserve a hotel"
+start_new_booking: @utils.transition to @topic.hotel_browse
+   description: "Start a new hotel search and booking"
 ```
 
 **Poor:**
@@ -362,18 +324,6 @@ go_next: @utils.transition to @topic.next
    description: "Go next"
 ```
 
-### State Management
-
-Store state in variables before transitioning:
-
-```agentscript
-actions:
-   search_hotels: @actions.search_hotels
-      with check_in=...
-      set @variables.check_in_date = @inputs.check_in
-      # State preserved for next topic
-```
-
 ## What's Next
 
 - **TopicDelegation**: Learn about delegation (consulting other topics)