Nexus Settings

There are setting within the software under Enterprise, Enterprise Configuration that you may wish to adjust. These are located in the Nexus section.

KEY	DESCRIPTION
Nexus_CutIDField	This option can be used to specify the automation ID to be used rather than the default MusicMaster Song ID.
Nexus_TranslateLegacyFieldIDs
Nexus_SkipDefaultMetadataPublish	When checked, this option will prevent a dump of all meta data from the automation system. This can be useful the first time a station receives a publishMetadata request as this would make it return no songs but it would update the last change tracking value. That means the next time publishMetadata is called, it would only return what has changed after the current time. This can also be done for an individual station in its Nexus settings.
Nexus User	By default this is set to the Admin user. With that setting, the API can do anything and any changes logged will be shown as performed by Admin. This can be changed to any user in the program allowing you to restrict the stations and functions as well as logging the changes as being performed by this user. When Nexus is called, it will have the rights and capabilities of the user selected. Changes made via Nexus will be logged as being made by this user.
Require authorization for Nexus requests	When checked you must have a MusicMaster CS user account and password to perform any actions via Nexus. This will require an authorization token to perform Nexus commands. Changes made by Nexus will be logged as being made by the user that you used to create the token. If you have multiple applications that use the Nexus API, you can now create multiple Nexus users that could all have different rights and see those changes logged as separate users.