Copyright © Cloud Software Group, Inc. All Rights Reserved
Copyright © Cloud Software Group, Inc. All Rights Reserved


Fulfillment Provisioning Modules : Sequencing Customers Service Orders

Sequencing Customers Service Orders
A provisioning flow might receive several service orders for the same customer. To avoid getting these service orders mixed up, you can sequence their flow through Fulfillment Provisioning.
Figure 29. Sequencing Modules
Sequencer
The Sequencer module detects whether there are any other service orders for the same customer in the provisioning flow. If multiple orders for a customer exist, the module serializes them so that the system is provisioning only one service order per customer. When the current service order reaches a TokenRemover module, the service order at the top of the queue is allowed to continue in the provisioning flow.
Sequencers automatically checkpoint the incoming service orders (see also Checkpointing Service Orders). Therefore, it is never necessary to place a checkpoint module immediately before or after a Sequencer.
You can extend the Sequencer module to provide sequencing by other criteria than customer ID.
Type
sequencer::Sequencer
For more details about this module, refer to the component documentation
TokenRemover
The TokenRemover module pops the service order off the top of the customer's queue in the Sequencer module if there is one.
TokenRemovers automatically checkpoint the incoming service orders (see also Checkpointing Service Orders). Therefore, it is never necessary to place a checkpoint module immediately before or after a TokenRemover.
Type
sequencer::TokenRemover
For more details about this module, refer the component documentation

Copyright © Cloud Software Group, Inc. All Rights Reserved
Copyright © Cloud Software Group, Inc. All Rights Reserved