publishSchedule

This example will detail the steps required in the API to allow a user to publish an updated log to the automation system.

Message Received always means the message Nexus received and Message Sent is always the message Nexus returns.

Scenario

The station is known for being on top of all the news and information in your format. Listeners turn to the station because it delivers. When there is a new concert announcement or a tragic death by one of the artists, the air staff scrambles to add that music to the play list.

 

Nexus Solution

This feature does require the station to set up a special database.ini so the Publish button will appear on the tool bar in the Schedule Editor. Information on what the station needs to do is in the Installation section of the Installation

 

The station user will make whatever changes they'd like to the log. They will then "publish" a new or updated schedule directly to the automation system. This is sent as this command:

<mmRequest command="publishSchedule" station="TestStation" mode="queue">
	<contents>
		<startTime>2016-09-02 00:00:00</startTime>
		<endTime>2016-09-02 23:00:00</endTime>
	</contents>
</mmRequest>

Nexus then replies with its status="ok" message.

Reply Message: 
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<mmReply command="publishSchedule" station="TestStation" messageId="2" status="ok"/>