Bixby Developer Center

This guide assumes familiarity with the following information:

• Basics of the editor (How to Use Bixby Home Studio)
• Metadata

In this guide, you'll learn about the following:

• How to create a Bixby Home Studio (BHS) Metadata Submission
• Submission States
• Submission History

You can add or edit voice actions for devices with metadata submissions. Once you create a new metadata file or update an existing one, you can submit your metadata file for publishing and release approval, and track its progress.

Submitting BHS Metadata

BHS enables you to create new metadata or update existing metadata with the icons in the metadata sidebar.

New Metadata: used to create new metadata for a device.

Load Metadata: used to update existing metadata of a device.

Once you load a new or existing metadata file, this file will have a list of voice intents, as shown below. In this example, the editor shows the metadata file generic-dimmer with three voice intents.

Editing Voice Intent Options

You have three options for editing voice intents. Once you've done at least one of the following, you can submit your metadata for approval:

• Add a New Voice Intent

• Update an Existing Voice Intent

• Delete an Existing Voice Intent

Adding a New Voice Intent

To add a voice intent, click the Add Voice Intent icon to the right of Voice Intents in the Metadata profile section.

A pop-up appears, as seen below. Select a category from the menu, and then select a voice intent from the list that appears. Click ADD.

The added voice intent appears in the list under Metadata profile in the metadata sidebar.

After adding the new voice intent, you can update the graph for this voice intent and then proceed to submitting it. For more information on adding to this graph, see Creating an Action Flow in the Bixby Home Studio Basics guide.

Updating an Existing Voice Intent

To update an existing voice intent, click a voice intent under Metadata profile to open its metadata information.

To make changes to the capability information for a device, click Property under the selected voice intent.

To make changes to a graph directly, click Graph under a voice intent.

To make changes to the JSON for a graph, click RAW in the top right corner.

In the pop-up, make changes to the raw JSON and click ADD.

Deleting an Existing Voice Intent

To delete an existing voice intent, right click the voice intent. Then, click Delete "%voice intent%". The below example deletes the "powerSwitch-turnOn" intent.

Preparing Metadata Submissions

Now that you've created new metadata or updated existing metadata, you can submit your metadata for approval for publishing and release:

1. Click Metadata profile in the metadata sidebar. You can view the current version (the version before you applied updates) on the left of the upload button. In this example, it's 0.0.1. The Metadata profile tab opens, and you can view the Meta Profile (Name, Version, MNID, VID). The Meta Profile version number shows the current version.

2. Update the version to the next version number. In this example, you can use 0.0.2. Confirm that the updated version number shows in the metadata sidebar, as shown below.

   Alternatively, you can click the Upload button in the metadata sidebar. In the Metadata Submission Message pop-up, you can update the metadata version. You can also compare changes between your new metadata file and the original one you updated by clicking COMPARE WITH 0.0.1.

3. Use the Metadata Submission Message pop-up to add a Submission Message that states the changes you've made to the metadata. Click SUBMIT.

4. The Submission Tab opens. As shown below, your metadata moves from the Local submission state to the Private submission state. Click SUBMIT.

Next, you'll decide whether to test your metadata or skip this step before submitting.

Testing Submissions

A pop-up appears that shows the steps to submit your metadata. You have two options:

• Skip Testing and Submit Metadata

• Test Metadata Before Submission

Skipping Testing Before Submission

To submit metadata without testing it, click SKIP TESTING AND SUBMIT.

A Metadata Submission Message pop-up appears. Add a message about the submission that explains what has changed since the last transition in submission state. Click SUBMIT.

A confirmation screen appears, stating that you successfully submitted your metadata.

The metadata will be forwarded to the release manager. If your metadata submission gets approved, the release manager releases it to the public per the deployment schedule.

Testing Metadata Before Submission

You can verify the metadata before submission:

1. Select the location and device to test the metadata. Click NEXT.
2. Click the TEST buttons against the action flows to test the metadata.
3. You can review the test results, as shown below. Click DONE.
   • The Execution Ratio shows how many voice intents were successfully executed.
   • The Success Ratio shows how many of those voice intents successfully reached their goal.
   • The Time Average shows how quickly each action flow completed, and if it completed in a reasonable amount of time.
4. A Metadata Submission Message pop-up appears. Add a message about the submission that explains what has changed since the last transition in submission state. Click SUBMIT.

A confirmation screen appears, stating that you successfully submitted your metadata.

The metadata will be forwarded to the release manager. If your metadata submission gets approved, the release manager releases it to the public per the deployment schedule.

Comparing Metadata Changes

Before submission, if you'd like to compare your current file to a previously-submitted one (or if you'd like to compare two versions of files), you can use the compare metadata changes feature.

Submitting Messages

Whenever a user changes the submission state of the metadata, a message (log) prompt appears. When you're changing the status of your submission, the message you submit should give information on what has changed in the metadata.

The recipients of your message will also differ depending on the transition state:

• Local to Private: members of the device manufacturer's team
• Private to Submitted: the release manager

The release manager writes a message to the members of the device manufacturer's team for the following transition states:

• Submitted to Private - This message should explain why the submission was rejected.
• Published to Released - This message lets the device manufacturer's team know that their submission was approved.

Submission States

There are five submission states:

• Local: The metadata file is stored locally but hasn't been uploaded.

• Private: Your metadata file has been uploaded. However, it hasn't been submitted to the release manager.

• Submitted: Your metadata file has been submitted. The release manager reviews the metadata for any issues. Reviews usually take about 2 to 3 days. When they've completed the review, the status can have two outcomes:

  • If the release manager doesn't find any issues with the metadata, it moves to Published status.
  • If the release manager rejects the file, the submission reverts to Private status.

• Published: Your metadata submission has been submitted and published on the Bixby Home Platform (BHP) server. However, it hasn't been released publicly to end users.

• Released: Your metadata submission has been publicly released to end users, and other BHP developers can view and use it.

Submission History

To view metadata submission history and state transition details, click the Submission icon in the activity bar on the left, which opens the submission sidebar. Click on a device from the list to open its entire submission history. Then click a version to view that submission's history.

To view submissions in specific states, select one or more states at the top of the submission sidebar. You'll see a check mark on the selected states.