got rid of deprecated function, added 2.4.0 info

Author: nparavicini7

guide/13-managing-arcgis-applications/experience-builder-workflows.ipynb

@@ -271,7 +271,7 @@
    "source": [
     "## Cloning an Experience and Validating its Success\n",
     "\n",
-    "Among other changes, 2.2.0 brings in the ability to clone experiences. This can be done both through `gis.content.clone_items()` or through the WebExperience class. We'll show here the helpful extra tools the class has to aid in this workflow."
+    "Among other changes, 2.2.0 brought in the ability to clone experiences, meaning you can create experiences in one GIS organization and easily move them to another. As with other items, this can be done by using `gis.content.clone_items()`. We'll show here the helpful extra tools the class has to aid in this workflow."
    ]
   },
   {
@@ -354,11 +354,11 @@
    ],
    "source": [
     "target = GIS(profile=\"another_online_profile\")\n",
-    "cloned_exp = portal_exp.clone(\n",
-    "    target = target, \n",
-    "    owner = \"another_online_user\",\n",
+    "cloned_list = target.content.clone_items(\n",
+    "    [portal_exp],\n",
     "    search_existing_items = False,\n",
     ")\n",
+    "cloned_exp = cloned_list[1]\n",
     "cloned_exp"
    ]
   },
@@ -374,9 +374,7 @@
    "cell_type": "code",
    "execution_count": null,
    "id": "d45bf80a",
-   "metadata": {
-    "scrolled": false
-   },
+   "metadata": {},
    "outputs": [],
    "source": [
     "WebExperience(cloned_exp).view()"
@@ -401,7 +399,7 @@
     "\n",
     "We'll show how to get an experience from the Developer Edition Experience Builder, upload it to different portals, and make sure the dependent data items get remapped accordingly. Instructions downloading and installing the Developer Edition can be found [here](https://developers.arcgis.com/experience-builder/guide/install-guide/).\n",
     "\n",
-    "First, you'll want to download your experience from the homepage of your local Experience Builder app, and then figure out what the path to the `config.json` file is. Once you know this, you can work with it in the ArcGIS API for Python."
+    "It's easy as just downloading your experience from the Developer Edition interface, and then knowing the path to your the download folder. Within the inner folders, there will be a file named `config.json`- this file contains the structure of your experience, expressed in the exact same way that online experiences are. You can pass in the path to this file to the `upload()` function, or the path to the main project folder in version 2.4.0 or higher."
    ]
   },
   {
@@ -618,7 +616,9 @@
    "id": "b7d49ce9",
    "metadata": {},
    "source": [
-    "As you can see, we can check instantly that our Experience is viewable in the new target GIS, and that the data sources were properly remapped. `dataSource_1` was remapped through `auto_remap`, and `dataSource_4` had its `itemId` and `portalUrl` values changed by `item_mapping`."
+    "As you can see, we can check instantly that our Experience is viewable in the new target GIS, and that the data sources were properly remapped. `dataSource_1` was remapped through `auto_remap`, and `dataSource_4` had its `itemId` and `portalUrl` values changed by `item_mapping`.\n",
+    "\n",
+    "One final note is that as of ArcGIS API for Python version 2.4.0, locally created experiences uploaded to a portal will also copy the experience's image resources as well- so if you have embedded images in your experience, those will get carried over, portrayed in your experience, and stored in the experience item's resources."
    ]
   }
  ],
@@ -638,7 +638,7 @@
    "name": "python",
    "nbconvert_exporter": "python",
    "pygments_lexer": "ipython3",
-   "version": "3.9.17"
+   "version": "3.10.14"
   }
  },
  "nbformat": 4,