Uh oh! We couldn’t find any match.

Please try other search keywords.

Bixby Developer Center

Guides

activity-support

required

Determines concept state after a transactional workflow is completed (meaning that the activity has started). Also determines how the system reacts during any user interactions for the given activity.

You define this key and its children in a *.activity.bxb file.

activity-support {
match {
Receipt (this)
}
states {
if (orderState == 'Ordered') {
state (Scheduled) {
expires (statusRefreshTime)
summary-view {
message {
template ("#{value(orderState)}")
}
title {
template ("#{value(order)}")
}
details{
template ("#{value(price)}")
}
}
detail-view {
layout-match (this) {
mode(Details)
}
}
}
} else-if (orderState == 'Shipped') {
state (Relevant) {
expires (statusRefreshTime)
summary-view {
message {
template ("#{value(orderState)}")
}
title {
template ("#{value(order)}")
}
details{
template ("#{value(price)}")
}
}
detail-view {
layout-match (this) {
mode (Details)
}
}
}
} else-if (orderState == 'Delivered' || orderState == 'Cancelled') {
state (Recent) {
summary-view {
message {
template ("#{value(orderState)}")
}
title {
template ("#{value(order)}")
}
details{
template ("#{value(price)}")
}
}
detail-view {
layout-match (this) {
mode (Details)
}
}
}
}
}
}

Child Keys

time
required
A required field that represents the point in time where you want to "anchor" the activity
match
optional
Use match patterns to dynamically lookup an appropriate root type for the current context
states
optional
Declares conditional mappings for various states of a transaction, which executes the first state that it finds