JourneyRecipeProblem
@gravity-rail/sdk / JourneyRecipeProblem
Interface: JourneyRecipeProblem
One reason a Journey is not a portable recipe, and where it is.
Definition names only: a step, a route and an action are named as their author named them. No condition, template or identity is carried.
Properties
actionName?
optionalactionName:string|null
actionType?
optionalactionType:string|null
code
code:
JourneyRecipeProblemCode
detail
detail:
string
enrollmentCondition?
optionalenrollmentCondition:number|null
enrollmentConditionName?
optionalenrollmentConditionName:string|null
formName?
optionalformName:string|null
nextStepName?
optionalnextStepName:string|null
routeName?
optionalrouteName:string|null
stepName?
optionalstepName:string|null