Skip to Content
Product Information

Import package to user preferred location via Content Network

What’s currently available?

Ability to import package from one Neo tenant to another irrespective of their landscape. Similarly, for CF platform.

If user wants to group content while importing to specific location, then that currently is not possible as part of import workflow, rather user has to follow 2 step approach:

  1. Import package in destination tenant
  2. Move package to desired location in destination tenant using file “Move To” option

Current UI


What’s new?

  • Ability to choose location while importing in destination tenant
  • Ability to choose different location for each folder while importing in destination tenant
  • Choosing location during import is OPTIONAL, if user wishes to continue with old behaviour, can simply be done by not meddling with Import location options
  • Available since 2021.06 SAC release

 

Rules – when import is allowed?

  1. Fresh Import – object with same ID doesn’t exists:
    • Option to choose folder during import is available only if the object with same ID doesn’t exist in the system
  2. Re-import – object with same ID exists:
    • If objects exist, retain in existing location –
      • its retained in existing location in destination tenant
      • based on import preferences it will be updated
    • If user wants to relocate existing objects, then:
      • delete the objects (even from recycle bin) and choose desired location during import
      • manually move the objects to desired location via “Move to” option

Limitations

  • Location can be chosen only for Folder type objects, which exist within Public folder
  • Location cannot be chosen for Story, Model etc objects
  • Location cannot be chosen for System objects like Team, Team folder, Connections etc


Step by step workflow

Ex.,

Folder1 contains Folder2, Story1, Model1

Folder2 contains Story2, Connection1, Team1

  1. Open package to import
  2. New UI is as below
  3. With the “Import To” user can choose any location within “Public” folder
  4. “Import To” dialog to browse through Public folder
  5. Toggle on “Override Folder Import Location”
  6. Content table below should refresh to provide “Browse” option for individual folder
  7. If any object already exists in destination tenant, then warning is shown
  8. Toggle off “Override Folder Import Location” shows warning message

Flowchart


Use cases

Ex1.,

Folder1 contains Folder2, Story1, Model1

Folder2 contains Story2, Connection1, Team1

Case 1 – None of the objects exist in destination tenant, chose same location for all

  • Open package
  • Switch to Import Options tab
  • Option to choose location within “Public” folder via “Import To”, select “My Files/Public/NewDest”
  • Content table shows user selected location ie “My Files/Public/NewDest”
  • Folder1 and Folder2 along with its content will be imported into “My Files/Public/NewDest”
  • System objects – Connection, Team not impacted by location change

Case 2 – None of the objects exist in destination tenant, chose different location for all

  • Open package
  • Switch to Import Options tab
  • Select “My Files/Public/NewDest” location via “Import To”
  • Content table shows user selected location ie “My Files/Public/NewDest”
  • Toggle on “Override Folder Import Location”
  • Select “My Files/Public/NewDestXYZ” for Folder2
  • Content table shows user selected location ie “My Files/Public/NewDestXYZ” for Folder2
  • Folder1 and its content will be imported to “My Files/Public/NewDest”
  • Folder2 and its content will be imported to “My Files/Public/NewDestXYZ”
  • System objects – Connection, Team not impacted by location change

Case 3 – Some of the objects exist in destination tenant, Folder1 exists

  • Open package
  • Switch to Import Options tab
  • Select “My Files/Public/NewDest” location via “Import To”
  • Content table shows user selected location ie “My Files/Public/NewDest” for Folder2
  • Folder1 already exists in destination tenant — path selection will have no impact
  • Toggle on “Override Folder Import Location”
  • Select “My Files/Public/NewDestXYZ” for Folder2
  • Folder1 and its content will be re-imported to current location by applying Overwrite Preferences accordingly
  • Folder2 and its content will be imported to “My Files/Public/NewDestXYZ”
  • System objects – Connection, Team not impacted by location change

Case 4 – All of the objects exist in destination tenant

  • Open package
  • Switch to Import Options tab
  • “Import To” option not available
  • No “Browse” option to choose location for individual folder in Content table
  • Content table shows current location of non-System objects in destination tenant
  • Folder1 and Folder2 along with its content will be re-imported to current location by applying Overwrite Preferences accordingly

Ex2.,

Package contains Story1, Model1

Case 1 – None of the objects exist in destination tenant

Case 2 – Some of the objects exist in destination tenant

  • Open package
  • Switch to Import Options tab
  • “Import To” option available
  • No “Browse” option to choose location for individual folder in Content table
  • Content table shows location of objects in destination tenant
  • Story1, Model1 will be imported to chosen location by applying Overwrite Preferences accordingly

Case 3 – All of the objects exist in destination tenant

  • Open package
  • Switch to Import Options tab
  • “Import To” option not available
  • No “Browse” option to choose location for individual folder in Content table
  • Content table shows location of objects in destination tenant
  • Story1, Model1 will be re-imported to default location by applying Overwrite Preferences accordingly

Ex3.,

Package contains Connection1, Team1 (System objects only)

Case 1 – None of the objects exist in destination tenant

Case 2 – Some of the objects exist in destination tenant

Case 3 – All of the objects exist in destination tenant

  • Open package
  • Switch to Import Options tab
  • “Import To” option not available
  • No “Browse” option to choose location for individual folder in Content table
  • Content table doesn’t show location of objects in destination tenant
  • Connection1, Team1 will be re-imported to default system location by applying Overwrite Preferences accordingly

 

Concluding thoughts

Do try this new feature and share your feedback.

Be the first to leave a comment
You must be Logged on to comment or reply to a post.