Bixby Developer Center

Guides
References

value

optional

A signal that signifies the presence of a provided concept value that the plan must use.

You can use a value intent to assign an explicit concept value to a primitive concept as in this example:

intent {
goal: viv.uber.BookRideShare
value: viv.uber.ProductType(UberBLACK)
}

Make sure to explicitly declare the type when casting a concept value to a different role, as in the example below:

match: viv.time.DateTimeInterval(dateTimeInterval)

intent {
goal: viv.time.DateInterval
value: viv.time.DateInterval {
start:
viv.time.StartDate {
$expr(dateTimeInterval.start.date)
}
}
}

You can use a value intent to assign an explicit value to a structure concept as seen in below example:

intent {
goal: viv.time.DateInterval
value: viv.time.DateInterval {
start:
viv.time.StartDate {
year: viv.time.Year(2010)
month: viv.time.Month(11)
day: viv.time.Day(20)
}
}
}

Here is another example of a value intent to a slightly more complex structure concept:

intent {
goal: viv.geo.Address
value: viv.geo.Address {
locality: viv.geo.LocalityName(San Jose)
centroid: viv.geo.GeoPoint {
latitude: viv.geo.Latitude(37.7749)
longitude: viv.geo.Longitude(-122.4194)
}
}
}

Child Keys

@prompt-behavior
optional
Enables you to prompt at a signal node, regardless of whether an input min- or max-cardinality constraint has been violated