Order operations & back office — found from sitemap — Spryker Commerce Platform

Cited by

Facts read from this source

• State machine definition Report an error

  “State machines help you define, execute and visualize predefined and automated processes. It can model events that involve performing a predetermined sequence of actions—for example, in the order process.”

• Xml modeling Report an error

  “Model and visualize the process as a state machine in XML.”

• Reusable subprocesses Report an error

  “Reusable sub-processes, such as return-process, programmable commands and conditions.”

• Manual or automated events Report an error

  “Events can be triggered manually or fully automated.”

• Timeouts Report an error

  “Timeouts.”

• Statemachine module capabilities Report an error

  “This module provides functionality for drawing the SM graph, triggering events, initializing a new state machine, or getting the state history for a processed item.”

• State flags Report an error

  “A state is defined by a name.”

• State flags query Report an error

  “You can query the state machine for items marked with specified flags by using StateMachineFacade::getItemsWithFlag() or vice versa StateMachineFacade::getItemsWithoutFlag().”

• Exclude from customer flag Report an error

  “We use the exclude from customer flag that skips all orders having ALL item states flagged with this flag. That means it’s not displayed on customer Yves order details and list pages.”

• Transitions conditions Report an error

  “The condition attribute allows you to add PHP code that double-checks if this transition can be fired or not.”

• Event onenter automatic Report an error

  “If an event has the onEnter="true" attribute associated, then the event is fired automatically when the source state is reached.”

• Event manual back office button Report an error

  “This adds a button in the Back Office → View Order [Order ID] page that allows you to manually trigger the corresponding transition by clicking the button.”

• Event API trigger Report an error

  “The triggerEventmethod allows triggering an event for a given process instance.”

• Event timeout trigger Report an error

  “By a timeout: Events are triggered after the defined time has passed.”

• Event commands Report an error

  “Events can have commands attached to it, which is logic that gets executed when that event is fired.”

• Timeout processor Report an error

  “Timeout processor is designed to set a custom timeout for an OMS event.”

• Subprocess reuse Report an error

  “the common parts of the processes can be extracted into subprocesses and reused.”

• Subprocess prefix Report an error

  “You might want to copy a subprocess over to consolidate process endpoints. To do so, define a prefix for a subprocess and use it for a target/source state or an event definition.”

• Sm storage location Report an error

  “Each state machine should have a folder created under the config/Zed/StateMachine/{StateMachineName}/ folder.”

• Condition plugin mapping Report an error

  “the mapping between a string linked to a condition and the implementation of the condition is also done through the state machine handler StateMachineHandlerInterface::getConditionPlugins().”

• Command plugin mapping Report an error

  “The mapping between this string and the actual implementation of the command is done through the state machine handler StateMachineHandlerInterface::getCommandPlugins().”

• Performance recommendation Report an error

  “To move high time cost operation from handling HTTP-request for order creation to the background, you can use timeout="1 second" instead of onEnter="true" for the event in transition from the first state of order.”

• Example statemachine module Report an error

  “There is already an example state machine implemented in Legacy Demoshop. Look for the stateMachineExample module. You can use it as a base for implementing your custom SM.”