Using the Fusion 4.0 Object Explorer

Issue:

I'm migrating from Fusion 3.1.x to Fusion 4.x, and I used the API to move collections or pipelines and now they're not showing up? 

Environment:

Fusion 

Resolution:

If you’ve had to migrate from Fusion 3.1.x to Fusion 4.x, and you happened to use the API to move collections or pipelines, etc, you may notice that they’re not showing up.  There’s a reason for that: Fusion has become app-centric.

What’s “app-centric?”  In short, it means that your collections, pipelines, profiles and so on are bound to a top-level application.  

Object Explorer to the Rescue!

Once you’ve uploaded your pipelines, etc, you’ll want to bind them to an app.  You can do that with the Object Explorer.   The Object Explorer allows you to view and manage links between objects.  For more advanced projects, you can make use of the links and/or apps APIs.

Links API:

https://doc.lucidworks.com/fusion-server/4.0/reference/api/links-api.html

Apps API:

https://doc.lucidworks.com/fusion-server/4.0/reference/api/apps-api.html

In Fusion 4.x, the Object Explorer is your key to keeping things organized.  You’ll find it under the “wrench” icon on the left-hand-side navigation:

 Once launched, you’ll see a UI that looks something like this:

 This represents all the various object types (pipelines, collections, profiles, etc) associated with this application.  You’ll notice the three tabs in the upper-left corner, with “In Current App” selected. If you click on “In No Apps,” you’ll see your recently uploaded objects that have yet to be associated.

Clicking on one of those objects in view isolates it, and gives you the opportunity to associate it:

Click the “Add to this app” link, and now the object is associated:

That’s all there is to it!   Now your pipeline will be available to this application.

Further reading:

The Object Explorer:

https://doc.lucidworks.com/fusion-server/4.0/concepts/object-explorer.html

Cause: