Bixby Developer Center

Guides
References

confirmation-view

optional

Determines the confirmation prompt being created, namely through what dialog and content are displayed to the user and how to handle confirm or abort responses. There must be a corresponding transactional action asking for confirmation with the confirm key. For more information, see Confirmation Views in Building Bixby Views.

You can change the color of the confirmation button in the capsule-info.bxb file using the action-fg-color and the action-bg-color.

Note

If the message key is missing, Bixby shows no confirmation dialog by default.

This key and its child keys must be defined in a *.view.bxb file. This file must be in an appropriate locale-specific resources folder or the base folder.

Note

Be aware of which components you are adding to your layouts and layout macros, because different components are available under different views. If you call a layout or layout macro in a view and that layout specifies a component that the view does not support, Bixby Developer Studio will throw an error. Similarly, you should consider which layout macros are being called within a layout itself. The same layout macro invoked in one component might not be valid if used within a different component, as the list of supported child components could differ.

You can read the Designing with Bixby Views design guide and the Building Bixby Views (UI) developer guide to check if your layout is using the correct components for that moment and that view.

Example

// resources/en-US/views/ConfirmHotel.view.bxb
confirmation-view {
match: core.Confirmation {
confirming: Action2 (action)
}
mode (NegativeEmphasis)
message ("Continue?")

render {
// `layout-match` or `layout-macro` or `nothing`
layout-match(action.input) {
mode (Detail)
}
}

confirm-options {
label ("Book")
on-confirm {
// allows user's to do post-confirmation validation
if (false) { // only `halt` and `replan` effects are supported
halt
}
}
}
abort-options {
label ("Keep looking")
on-abort {
intent {
goal: AvailableHotel
value {$expr(request.when)}
value {$expr(request.hotel.address.centroid)}
}
}
}
conversation-drivers {
...
}
}

Child Keys

match
required
The match pattern evaluated to decide which action is being confirmed
abort-options
optional
Container for the abort options, determining what happens if a user aborts a choice
confirm-options
optional
Container for the confirmation options, determining what happens if a user confirms a choice
conversation-drivers
optional
Provide convenient shortcuts to related actions in the form of buttons that appear at the bottom of the screen
message
optional
Message to display to users
mode
optional
The mode in which to render the confirmation decision
refresh
optional
Allows for the results to be periodically refreshed, as long as the UI remains open
render
optional
Renders the specified view for users