Data360 Analyze: can legacy library nodes be changed in Analyze?

In LAE, if you have a "shared file" (for example, on a network drive), then if anyone makes a change to the file, BRE will detect that "the file has changed" and will prompt you to reload the Library BRG

In LAE, a group of nodes inside of a Library BRG is treated somewhat as a unit. Include the library, you get the all the nodes.  Make one change to any node, save the file, BRE considers the whole thing as new and will reload the whole file.

In Analyze, when you import a Library BRG, the various library nodes are imported as stand-alone units, and one of them could be modified without having any effect on the others.  In Analyze, they are now separate units.

In Analyze, when you import a Library BRG, all the internal library nodes are placed in some folder together.  If you want everyone to use exactly the same copy of the nodes, then they need to be a folder that each person can access, and that folder needs to be added to the LibraryPath (more on this issue below)

In Analyze, there is zero notification that a Library Node has been modified while you have a dataflow open.  That now requires coordination among the team.

Each time you open a dataflow in Analyze, the newest version of any library nodes will be brought in.

In Analyze, if you import the "same library BRG" twice to two different folders, then even though the nodes might have the same name, they will have different internal identifiers, and if you include both folders in your LibraryPaths, then you will see both nodes, and you will be unable to determine which is the 'new' one versus the old one

LibraryPathSearchFolders can be managed in 3 ways.
a) put the library node in the folder with the main dataflow
b) put the node in a folder and edit the SearchPath on the dataflow itself
c) put the node in a folder and edit the DefaultSearchPath in the system settings

Each new dataflow starts with the DefaultSearchPath from the system settings, but it is constant after creation.. you would have to edit the SearchPath within the dataflow itself to take advantage of any new folders that might contain library nodes