Order Fulfillment Application Accelerator

Implementation Guide
24.1
©2024 Pegasystems Inc., Cambridge, MA. All rights reserved.

Trademarks
For Pegasystems Inc. trademarks and registered trademarks, all rights reserved. All other trademarks or
service marks are property of their respective holders.
For information about the third-party software that is delivered with the product, refer to the third-party
license file on your installation media that is specific to your release.

Notices
This publication describes and/or represents products and services of Pegasystems Inc. It may contain
trade secrets and proprietary information that are protected by various federal, state, and international
laws, and distributed under licenses restricting their use, copying, modification, distribution, or transmittal
in any form without prior written authorization of Pegasystems Inc.
This publication is current as of the date of publication only. Changes to the publication may be
made from time to time at the discretion of Pegasystems Inc. This publication remains the property
of Pegasystems Inc. and must be returned to it upon request. This publication does not imply any
commitment to offer or deliver the products or services described herein.
This publication may include references to Pegasystems Inc. product features that have not been licensed
by you or your company. If you have questions about whether a particular capability is included in your
installation, please consult your Pegasystems Inc. services consultant.
Although Pegasystems Inc. strives for accuracy in its publications, any publication may contain
inaccuracies or typographical errors, as well as technical inaccuracies. Pegasystems Inc. shall not be liable
for technical or editorial errors or omissions contained herein. Pegasystems Inc. may make improvements
and/or changes to the publication at any time without notice.
Any references in this publication to non-Pegasystems websites are provided for convenience only and
do not serve as an endorsement of these websites. The materials at these websites are not part of the
material for Pegasystems products, and use of those websites is at your own risk.
Information concerning non-Pegasystems products was obtained from the suppliers of those products,
their publications, or other publicly available sources. Address questions about non-Pegasystems
products to the suppliers of those products.
This publication may contain examples used in daily business operations that include the names of
people, companies, products, and other third-party publications. Such examples are fictitious and any
similarity to the names or other data used by an actual business enterprise or individual is coincidental.
This document is the property of:
Pegasystems Inc.
1 Main Street
Cambridge, MA 02142, U.S.A.
Phone: 888-PEGA-NOW
[Link]
Document: Order Fulfillment Application Accelerator Implementation Guide
Publication date: October 9, 2024

Feedback
If you have comments for how we can improve our materials, send an email to AppDocBug@[Link].
ii | Order Fulfillment Orchestration Accelerator Implementation Guide
Contents

Contents
Document: Order Fulfillment Application Accelerator Implementation Guide ................................................................................ 2
Intended audience .................................................................................................................................................................................. 4
Prerequisites ............................................................................................................................................................................................ 4
Product overview ..................................................................................................................................................................................... 5
Communications features .......................................................................................................................................... 5
Specifications ............................................................................................................................................................... 6
Specification and Task Fulfillment Association ......................................................................................................... 7
Order decomposition .................................................................................................................................................. 8
Order orchestration .................................................................................................................................................... 8
Standard case types .................................................................................................................................................... 9
Order Fulfillment Application starter kit ............................................................................................................................................. 10
What is included .................................................................................................................................................................................... 11
Application rules ........................................................................................................................................................ 11
Rulesets ...................................................................................................................................................................... 11
Case types .................................................................................................................................................................. 12
Data models ............................................................................................................................................................... 14
Order Request.......................................................................................................................................................................... 14
Case type (Work) data elements ............................................................................................................................................ 14
Order Fulfillment Template .................................................................................................................................................... 15
Work groups and work queues ................................................................................................................................ 18
Access groups ............................................................................................................................................................ 18
Portals and dashboard .............................................................................................................................................. 19
Landing Pages ............................................................................................................................................................ 19
TMForum APIs ............................................................................................................................................................ 20
Product Ordering Management API (TMF 622)..................................................................................................................... 20
Service Ordering Management API (TMF 641). ..................................................................................................................... 23
Extending Order Fulfillment Application Accelerator ........................................................................................................................ 27
Implementation approach ........................................................................................................................................ 27
Team responsibilities .............................................................................................................................................................. 27
Roles and responsibilities ....................................................................................................................................................... 27
Creating a new operator ID ...................................................................................................................................... 28
Creating a new application ....................................................................................................................................... 28
Updating dynamic class referencing........................................................................................................................ 29
Updating the access group of the service package ................................................................................................ 29
Updating the fulfillment association data records ................................................................................................. 29
Creating new fulfillment tasks .................................................................................................................................. 30
Configuring a default email account ........................................................................................................................ 30
Appendix A Order Hierarchy Schema.................................................................................................................................................. 32
Appendix B Order fulfillment data classes and database mapping ................................................................................................. 36
Appendix C SpecificationDetail structure - Fulfillment template...................................................................................................... 37
Appendix D Defining additional dependencies at the top-level in Order Fulfillment template .................................................... 38
Appendix E Support of Modify, Change and Delete operations of OFA Accelerator ...................................................................... 39

Order Fulfillment Orchestration Accelerator Implementation Guide | iii

 Order Fulfillment Application Accelerator implementation guide

Order Fulfillment Application Accelerator

implementation guide
This guide helps you to implement a solution that orchestrates the work of fulfilling product and/or
service orders using the Order Fulfillment Accelerator.

• Intended audience
• Prerequisites
• Product overview
• Order Fulfillment Application starter kit
• What is included
• Extending Order Fulfillment Application Accelerator
• Appendix A Order Hierarchy Schema
• Appendix B Order fulfillment data classes and database mapping
• Appendix C Specification Detail structure - Fulfillment template
• Appendix D Defining additional dependencies at the top-level in Order Fulfillment template
• Appendix E Support of Modify, Change and Delete operations of OFA Accelerator

Intended audience
This guide is intended for the following users who implement Order Fulfillment Application Accelerator
based solutions.

Business managers
Evaluate solutions.
Possess a general, non-technical understanding of the features and capabilities of the application.

Project managers or business analysts

Implement solutions that apply to specific business requirements to ensure compliance and
continuous improvement across their organization.

System architects or application developers

Build, maintain, modify, and extend the solution.

System and database administrators

Responsible for security and ongoing operational functions of the application, such as access, tuning,
and troubleshooting; experienced in system operations.

Prerequisites
Product Order or Service Order can either be consumed by customer based on requirements. They
are built on Order Fulfillment application which is shipped along with both the application. Customer
can switch between the applications according to the needs. Order Fulfillment Application Accelerator
24.1 requires Pega Platform 24.1.

Order Fulfillment Orchestration Accelerator Implementation Guide | 4

 Order Fulfillment Application Accelerator implementation guide

Product overview
The Order Fulfillment Application Accelerator provides a set of features designed to fast-track the
development of an order fulfillment application. This accelerator provides the latest technologies to
reduce the time to configure product hierarchy, enhance customer experience, and improve user
productivity. The optional Order Fulfillment template empowers product managers to define the product,
service, resource, and their dependencies for a fulfillment plan. These features accommodate
requirements for the telecom industry and can be adopted by any industry. Instead of a Pega developer,
a citizen developer can define a case workflow template for Service Order and Resource Order.

Order Fulfillment Application Accelerator process.

This section describes the following key capabilities and features provided by the Order Fulfillment
Application Accelerator.

• Communications features.
• Specifications (Order Fulfillment Template prior 8.7).
• Specification and Task Fulfillment Association.
• Order decomposition.
• Order reports.
• Order orchestration.
• Standard case types.

Communications features
Product Order services

The productOrderingManagement service package enables the application to integrate with

the upstream sales and order entry applications with REST Services. These REST services
provide robust data model that aligns with the TMForum's Open API TMF622 that provides
Order Fulfillment Orchestration Accelerator Implementation Guide | 5
 Order Fulfillment Application Accelerator implementation guide

industry standard objects and properties. All applications conforming to TMF622 use the same
API interface and make it easy to integrate. Product Order services include Create, Amend,
Delete and Retrieve in REST formats with json.

Service Order services

The serviceOrderingManagement service package enables the application to integrate with

the upstream sales and order entry applications with REST Services. These REST services
provide robust data model that aligns with the TMForum's Open API TMF641 that provides
industry standard objects and properties. All applications conforming to TMF641 use the same
API interface and make it easy to integrate. Service Order services include Create, Amend,
Delete and Retrieve in REST formats with json.

Specifications
The Specification case type represents how an order case will be traversed. It contains the fulfillment
plans available in the application and is populated by clients. The fulfillment plans define the entire order
life cycle.
The Order Fulfillment Template was a separate component prior to version 8.7 which provides a business-
friendly environment to manage the service catalog of a client. Some artifacts from Order Fulfillment
template are still in use, however there is a subtlety in the way the template works now. Fulfillment
Template is re-organized and managed by specifications. The specification type determines the type of
the specifications that can be created, where child specifications can be added to provide the fulfillment
structure for decomposition purpose. Here are the specifications.
• Product
• Service
• Resource
These specifications combine to make the product hierarchy for any customer-facing service. This
hierarchy includes the key capabilities: product specification, service specification, resource specification,
case dependency definition, and point of no return.
• The product specification in the application is a Specification case (S-XXXX created) which is present in
the same worktable. The product manager defines the product hierarchy aligned to the fulfillment
plan. This accelerates time-to-market because many product introductions are commercial in nature
and have no effect on the technical fulfillment.
• Fulfillment cases are defined in fulfillment plans to maximize reuse. For example, a move order can
simply be an add order (at the new location) and a disconnect order (at the old location). Because
these cases already exist, they simply need to be added to the fulfillment plan for the move order. This
accelerates time-to-value in many Fulfillments Control Center (FCC) implementations.
• Case dependencies are easily configured by using the fulfillment plan. Case dependencies define the
dependencies between service orders and the sequence of execution. For example, you want the ship
equipment case to be completed before the site installation case starts.
• The point of no return (PONR) feature is a configuration available in the fulfillment plan case. PONR
enables the user to configure the end point for the case after which the customer order cannot be
modified or amended. After the order reaches the point of no return, it can only be canceled.

Order Fulfillment Orchestration Accelerator Implementation Guide | 6

 Order Fulfillment Application Accelerator implementation guide

Specification and Task Fulfillment Association

The fulfillment plan is the combination of versions and the child specifications in the specification case.
The association of specifications with case type creates the final fulfillment plan. The technical tasks
translate to case types during the fulfillment association process. After the association is complete, all
tasks are created with dependencies specified and routed for completion. The categories of work cases
are defined in the following sections.
Operations are frequently referred to as Move, Add, Change and Disconnect (also referred to as MACD.
The Customer Service Professionals (CSPs also require in-flight operations such as amending or canceling
orders that are in-flight (or currently being processed). Order Fulfillment Application Accelerator supports
both MACD and in-flight Amend operations. Amending or canceling an in-flight order is different from
updating or canceling a service. While the order is still in progress e.g. a new order to provision internet
service, it can be amended to update speed as long as internet service has not been provisioned but once
service has been provisioned, new order is complete, no amending or canceling of this order is possible.
However, you can issue another new order to update the internet service till service is active.

Order actions.

Order actions determine the action at the customer order level. There are two types of order
actions: New and In-Flight. New order actions imply that the order is newly created for adding new
products and services or managing existing products and services. In-Flight order actions imply that
an order that is in progress needs changes. For in-flight orders, a fulfillment plan is not
recommended to be created. The productOrder/{id} and serviceOrder/{id} services
handle in flight order amendments.
The following new order actions have been defined out of the box. You can create additional order
actions as needed.
Order action Description Supported order item actions

ADD Add a new product or service. ADD

DISCONNECT Disconnect an existing product DISCONNECT

or service.
MOVE Move existing products or ADD, DISCONNECT, KEEP
services to new locations.
CHANGE Change existing products or ADD, DISCONNECT,
services. ADDUPGRADE, DISCONNECT-
UPGRADE, KEEP

Order item action.

Order item action determines the action to be taken on the line item of a customer order. The ADD
action is provided out of the box. You can create additional order item actions as needed.

Order item action Description

ADD Add a new product or service.

CANCEL Cancel an existing line item in an in-flight order.

DISCONNECT Disconnect an existing product or service.

Order Fulfillment Orchestration Accelerator Implementation Guide | 7

 Order Fulfillment Application Accelerator implementation guide

ADD-UPGRADE ADD-UPGRADE is the same as ADD, but it goes

along with DISCONNECT-UPGRADE of an existing
service in an order.
Order item action Description

DISCONNECT-UPGRADE Disconnects the existing service for upgrade. It

goes along with ADD-UPGRADE.

CHANGE Change existing line item or activated product or

service.

KEEP No change to the existing line item or product or

service.

Order decomposition
The fulfillment plan enables the user to define a unique scenario, for each product specification, when a
product order or service order is received by the application. The fulfillment plans include two key
capabilities: product hierarchy and fulfillment workflow for each node in the hierarchy. The order
fulfillment template contains the complete fulfillment process for every order action and order item
action.
During order decomposition, a product order is created based on product, service, resource specification
hierarchy, and fulfillment tasks association. A customer order has product order line items mapped to
line items defined in Order JSON, service and resource order mapped to service, and resource entities
defined in the hierarchy. The order also defines three types of dependencies:
• Parent child hierarchy dependency, that is, the Parent PO/SO can be proceeded only after the children
are completed.
• Dependencies among siblings based on dependencies defined in product, service, and resource
specification cases.
• Dependencies among product order line items based on order item relationship as defined in Order
JSON

Order orchestration
The Order Fulfillment Application Accelerator orchestrates an order based on the fulfillment plan
configured in the system.
On creation of the Product/Service order, Order Line Items cases and the Fulfillment cases are created
asynchronously through a Queue Processor “AsyncCreateOLICases”. It has dependency on these DSS
whether to create the cases asynchronously or sequentially. After all the child cases are resolved, the
parent case moves to the resolution stage. In addition to this child resolution dependency, the
ResolvePOLIcases queue processor, in the background, resolves the sibling dependencies defined in
the fulfillment plan. The queue processor runs the ResolveDependencies activity in the background so
that online users do not experience wait time as they complete fulfillment tasks. Here are DSS’ which are
responsible in asynchronous case creation:

• OrderFulfillment • OLI/AsyncProcessingSwitch
• OrderFulfillment • OLI/AsyncWaitTime

Order Fulfillment Orchestration Accelerator Implementation Guide | 8

 Order Fulfillment Application Accelerator implementation guide

Standard case types

Standard orders (also referred to as case types) are included with Order Fulfillment Application
Accelerator. Two separate applications are present Product Order, Service Order. Any one of the two
applications can be selected from New Application wizard when you create your own application. The
case types are available for selection within the New Application wizard when you create your fulfillment
application. Depending on the need of your organization, you can include all or a subset of these case
types in your application.

Product/Service order
A product/service order manages the end-to-end life cycle of a customer request for products. The
order can handle suspend, resume, amend, add, change, and cease existing ordered products and
services. This case type manages different stages of the product order and is the parent for product
line-item cases.

Product line items

Product line items correspond to each line item in the incoming customer order XML/JSON. Product
line items map to a specific top-level node specification.

Fulfillment cases
Fulfillment cases are service and resource orders. These cases contain the data required to fulfill the
product orders and are designed to manage different stages of orders. Specific service and resource
orders (for example, Configure Router) should be inherited from this base case type.
All fulfillment cases have been designed in a way that they are easily extended to meet
implementation specific requirements. Additional cases can be added by using Pega Platform case
management capabilities.
Order Fulfillment Application Accelerator provides the following Service and Resource fulfillment case
types out-of-the-box and can be selected while running the New Application wizard.

Fulfillment case type Description

ActivateSwitch Manages different stages of activation on the

switching equipment

AddAccess Manages different stages of adding access to the

network

AddEthernetService Manages different stages of adding and enabling

Ethernet services to the customer

AddLink Manages different stages for the process of

activating link to the network

AssignSwitchIPAndGateway Manages assigning the switch IP and gateways

to the network

ConfigureLoggingAndTraps Manages configuring the logging and traps.

Order Fulfillment Orchestration Accelerator Implementation Guide | 9

 Order Fulfillment Application Accelerator implementation guide

ConfigureTime Manages different stages for configuring time

CPE Manages different stages of procuring customer

premises equipment

EnableNeighbourDiscovery Manages different stages of enabling neighbor

discovery in a network

Fiber Manages different stages of activating a fiber

service

NetworkResources Contains different stages to manage network

resources

NotifyBilling Manages different stages to notify and activate

the billing

SetupLine Manages different stages for network line setup

TestingAndTroubleshoot Manages different stages for testing and

troubleshooting network issues
Fulfillment case type Description

UpdateGIS Manages different stages of updating

Geographical information systems (GIS)

VendorOrder Manages different stages for tracking and

processing third-party vendor activities
Vendor order
This case type manages different stages of vendor order and is the subcase of a resource order.

Specification
This case type contains the hierarchy of the fulfillment cases.

Order Fulfillment Application starter kit

The Order Fulfillment Application starter kit includes the following items that help you build your own
solution.

Order Fulfillment Application reference application

Order Fulfillment Orchestration Accelerator Implementation Guide | 10

 Order Fulfillment Application Accelerator implementation guide

The reference application includes rulesets that you reference when building your own solution.
Note: You build your solution on top of this reference application.

User experience video

The video provides details to demonstrate how fulfillment engineers step through the case types.

What is included
• Application rule
• Rulesets
• Case types
• Data models
• Work groups and work queues
• Personas
• Access groups
• Portals and dashboard
• TMForum APIs

Application rules
Product Order: The application rule is built on application OrderFulfillment 8. This application
contains the rules and classes specific to Product Order implementation layer. The application rule
is ProductOrder 8.

Service Order: The application rule is built on application OrderFulfillment 8. This application
contains the rules and classes specific to Product Order implementation layer. The application rule
is ServiceOrder 8.

OrderFulfillment : This application is built on Platform 8.24.1 using the Pega Constellation Design
system. This application contains the common functionalities of ProductOrder and ServiceOrder
applications. The application rule is OrderFulfillment 8.

Rulesets
The Order Fulfillment Application Accelerator consists of the following rulesets:

ProductOrder
Contains rules specific to ProductOrder application layer.
ProductOrderInt
Interface rules of Product Order.
ServiceOrder
Contains rules specific to ServiceOrder application layer.

Order Fulfillment Orchestration Accelerator Implementation Guide | 11

 Order Fulfillment Application Accelerator implementation guide

ServiceOrderInt
Interface rules of ServiceOrder.
Accel
Contains base class rules for Accel applications.
AccelInt
Contains base class rules for Accel applications. This ruleset contains the interfaces that all accelerator
applications share.

OrderFulfillment
Core rules of order fulfillment major functionalities and fulfillment tasks.
OrderFulfillmentInt
Interface rules for the OrderFulfillment layer used in both Product Order and Service Order layers.
OrderRequest
Contains the rules related to REST services of OFA application.
OrderRequestData
Contains the data structure for OrderRequest.

The Order Fulfillment Template component consists of the following rulesets:

Accel
Contains base class rules for Accel applications.
OrderFulfillmentTemplate
Rule for maintaining fulfillment templates.
OrderFulfillmentData
Data structure for the Order Fulfillment Template.

Case types
Reuse the following case types that are available in Order Fulfillment Applications(Product Order and
Service Order) Accelerator according to your specific business needs.

Case type Description

Product Order Top level case created for each Product order

Service Order
Top level case created for each Service order

Product Order Line Item Details of Product items.

Service Order Line Item Details of Service Items.

Order Fulfillment Orchestration Accelerator Implementation Guide | 12

 Order Fulfillment Application Accelerator implementation guide

Specification cases contains the hierarchy to

Specification
decompose an order.
Sample Fulfillment Case types Description

Accel-OF-Work-FulfillmentType Cases for fulfillment of product line items. Product

line items contain one or more fulfillment cases

Accel-OF-Work-FulfillmentType-ActivateSwitch Fulfillment task to activate the switching

equipment

Accel-OF-Work-FulfillmentType-AddAccess Fulfillment task to manage the process of adding

access to the network

Fulfillment task to manage the process of adding

Accel-OF-Work-FulfillmentTypeAddEthernetService
Ethernet service on the network

Accel-OF-Work-FulfillmentType-AddLink Fulfillment task to manage the activation of a link

to the network

Accel-OF-Work- Fulfillment task to manage configuring the logging

FulfillmentTypeConfigureLoggingAndTraps and traps

Accel-OF-Work-FulfillmentType-ConfigureTime Manages the different stages for configuring time

Accel-OF-Work-FulfillmentType-CPE Fulfillment task to manage customer-premises

equipment requests

Accel-OF-Work- Manages different stages for enabling the

FulfillmentTypeEnableNeighbourDiscovery neighbor discovery in network

Accel-OF-Work-FulfillmentType-Fiber Manages different stages for activating the fiber

service

Accel-OF-Work-FulfillmentType-NetworkResources Manages the network resources

Accel-OF-Work-FulfillmentType-NotifyBilling Notifies billing

Accel-OF-Work-FulfillmentType-NotifyBilling Manages different stages for the network fiber

line setup

Accel-OF-Work-FulfillmentType-SetupLine Manages different stages for the network line

setup

Accel-OF-Work- Fulfillment case for testing and troubleshooting

FulfillmentTypeTestingAndTroubleshoot the network issue

Order Fulfillment Orchestration Accelerator Implementation Guide | 13

 Order Fulfillment Application Accelerator implementation guide

Accel-OF-Work-FulfillmentType-UpdateGIS Fulfillment case for updating the geographic

information system (GIS)

Accel-OF-Work-FulfillmentType-VendorOrder Fulfillment case for tracking and processing the

third-party vendor

Data models
Data models describe the objects modeled in an application and their relationship to each other. A data
model is a collection of entities and attributes.

• Order Request
• Case type (Work) data elements
• Order Fulfillment Template
• Fulfillment Association

Order Request
The Order Request data structure is a core data model for the application. Inbound Product / Service
Orders are decomposed into this data structure. This structure is used to create the fulfillment plan, and
various case types also maintain elements of the structure.

Case type (Work) data elements

Each case type contains all or part of the Order Request data elements. The tables in this section list the
case types with a brief description of their purpose, and the Product / Service Order Request data that
each of them maintains and presents.

Product Order
The Product Order case maintains elements of the Product Order Request data structure as follows.
Page Data class

Order case Details Accel-OF-Data-OrderRequest-ExOrder

Party Details Accel-OF-Data-OrderRequest-ExOParty

Product Order Line item Accel-OF-Data-OrderRequest-ExOOrderItems

Product Order Line Item

The Product Order Line Item case maintains elements of the Product Order line item request data
structure as follows.

Page Data class

Order Line Item Case Details Accel-OF-Data-OrderRequest-ExOOrderItems

Product Accel-OF-Data-OrderRequest-ExOIProduct

Order Fulfillment Orchestration Accelerator Implementation Guide | 14

 Order Fulfillment Application Accelerator implementation guide

Product Characteristics Accel-OF-Data-OrderRequest-Characteristics

Product Offering Accel-OF-Data-OrderRequest-ExOIOffer

Product Order Item Relationship Accel-OF-Data-OrderRequest-ExOIRelationship

Service Order
The Service Order case maintains elements of the Service Order Request data structure as follows.
Page Data class

Order Case Details Accel-OF-Data-OrderRequest-ExOrder

Party Details Accel-OF-Data-OrderRequest-ExOParty

Service Order Line item Accel-OF-Data-OrderRequest-ExOOrderItems

Service Order Line Item

The Service Order Line Item case maintains elements of the Service Order line item request data
structure as follows.

Page Data class

Order Line Item Case Details Accel-OF-Data-OrderRequest-ExOOrderItems

Service Accel-OF-Data-OrderRequest-ExOIService

Service Characteristics Accel-OF-Data-OrderRequest-Characteristics

Accel-OF-Data-OrderRequest-
Service Specification
ExOIServiceSpecification

Service Order Item Relationship Accel-OF-Data-OrderRequest-ExOIRelationship

Order Fulfillment Template

The Order Fulfillment Template here is the functionality of how an Order case would traverse. An Order
Line Item can have many fulfillment cases, which can be services and resources. The services and
resources in turn can have one or more child services and resources. The Template is there to define that
tree structure which guides the case creation. In this version, one template for a single parent is a tree of
cases and related cases, which is defined by a Specification of Type Product. The Specification type
product can have multiple Service and Resource cases, which in turn can have multiple child service and
resource cases.

Order Fulfillment Orchestration Accelerator Implementation Guide | 15

 Order Fulfillment Application Accelerator implementation guide

A Specification case has Versions, each version defines a time frame within which a list of services are
applicable.

Specification case Data Elements

Versions Version, StartDate, EndDate, Defines time frames for which a

Description, Child Services list of child specifications are
applicable

Child Specs Name, DependentOn, Point of List of child Specification and its
No Return dependents.

Fulfillment Association

Fulfillment Association Defines the relation between a case type to a specification. When case is
decomposed, the specification case applicable for a fulfillment case hierarchy is determined from this
table. When decomposition, the current date is matched to get the version applicable, and the child
specifications are referred to create corresponding fulfillment cases.

Order Fulfillment Orchestration Accelerator Implementation Guide | 16

 Order Fulfillment Application Accelerator implementation guide

Runtime Fulfillment Template Process

Runtime processing utilizes data pages to retrieve order specifications. These data pages retrieve
specifications and dependency information from instances of the Specification case type. A
specification case has versions based on date range for which the child specifications are valid for
and each child specification can have dependent specifications.

Fulfillment Association
Fulfillment Association is the last step in the creation of a fulfillment plan and consists of a process of
identifying the cases that are required to complete a customer order. The sources for determining which
cases you need to create are the Fulfillment Association class instances.

Fulfillment Association data model elements

The following tables lists the classes that comprise the association table:

Element Class/Database table Purpose

Fulfillment associations Accel-OF-Data- Translate Request Hierarchy to

FulfillmentAssociation a Customer Fulfillment Plan.
pr_accel_of_
data_fulfillmentas

Specifications Accel-OF-Data-Specification Product, Service, and Resource

of_data_specification Specifications

Order Actions Accel-OF-Data-OrderActions Action definitions available

pr_accel_of_data_orderactions for defining service/resource
specifications. The default
values are Add, Change,
Disconnect and Move.
Fulfillment Association maintenance process
The following figure shows the maintenance process for adding and modifying the association
instances:

Order Fulfillment Orchestration Accelerator Implementation Guide | 17

 Order Fulfillment Application Accelerator implementation guide

The Fulfillment Association maintenance process

Work groups and work queues

A work group identifies the team, including the managing supervisor, workers, and work queues, that are
designated to a work group. The Order Fulfillment Application Accelerator contains the following work
groups and work queues:
Work basket / Work queue Work Group Work Group Manager

OrderFulfillment WB OrderFulfillmentGroup Administrator@[Link]

Pending Fulfillment OrderFulfillmentManagerGroup Administrator@[Link]

ProductManger WB ProductManagerGroup Administrator@[Link]

Integration Exceptions OrderFulfillmentGroup Administrator@[Link]

default@Accel default@Accel Administrator@[Link]

Access groups
You can restrict access to functionality within your application by using an access group. The following
default access groups are available after you install Order Fulfillment Application Accelerator:

Order Fulfillment Orchestration Accelerator Implementation Guide | 18

 Order Fulfillment Application Accelerator implementation guide

Access group Portal Purpose

OrderFulfillment:AppSetup pxAppConfig Initial implementation process,

or to run the New Application
Wizard. You must create an
operator in this access group.

UserPortal For end users

OrderFulfillment:
ProductManager

UserPortal For end users

OrderFulfillment:
FulfillmentManager

UserPortal For end users

OrderFulfillment:
FulfillmentEngineer

pxExpress For App Studio users

OrderFulfillment:
Designers

OrderFulfillment: Developer For developers

Authors

UserPortal For end users

OrderFulfillment:
Users

Portals and dashboard

Portals are workspaces that help developers with the Dev Studio, and users who manage cases with the
Case Manager and mobile portals. A dashboard is a web page that displays the current status and
trends in your organization. Order Fulfillment Application Accelerator provides the following portals
and associated dashboards:
Portal Ruleset Dashboard Work Group/Team
default*
UserPortal OrderFulfillment User
OrderFulfillment
Group

Landing Pages
There are a few landing pages that can be referred to various Functionality. The main landing pages in
this application are:
• Fulfillment Association – contains table to show the Fulfillment Association table.
• Specifications – contains the Specification cases that are created for the purpose of Fulfillment
template.

Order Fulfillment Orchestration Accelerator Implementation Guide | 19

 Order Fulfillment Application Accelerator implementation guide

TMForum APIs
Product Ordering Management API (TMF 622).
Pega Order Fulfillment Accelerator (OFA) is certified on TMForum Product Ordering Management API (TMF
622). These APIs are designed with REST webservices protocol. Pega Order Fulfillment Accelerator
provides GET, POST, PATCH and DELETE API operations for Product Order resource.
The following are the benefits of TMForum APIs:
• Standard interface to integrate with OFA
• Reduces time to implement
For more details about TM Forum, see TMForum Home and API Page TMForum APIs.
The dedicated Service Package for TMForum APIs is productOrderingManagement. The input request and
output response format for each API is as per standard resource defined for TMForum Specification guide
v4.0.0. The error codes were also defined as per TMF Specification guide.
Please find the specification document reference here.

OFA Entity API Operation Description Request Response

Product Order GET List It retrieves list of In URL few filters

all Product Order were passed as
entities present in Query string
the system parameters to
limit the response
data. They are:
• externalId*
• description*
• orderDate*
• fields*
• state*
• id*

OFA Entity API Operation Description Request Response

GET/{id} It retrieves single The Product

Product Order Order entity id
entity from whose details
system need to be
retrieved will be
passed as input
through path
parameter in URL.
In URL few filters
were passed as
Query string
parameters to
limit the response
data They are:

Order Fulfillment Orchestration Accelerator Implementation Guide | 20

 Order Fulfillment Application Accelerator implementation guide

fields*

POST It creates Product

order in OFA
Application as per
details passed in
the request JSON

PATCH/{id} It updates
existing entity in
the system with
details passed in
the input request.
The id of the
entity which is
being updated
needs to be
passed in the
path parameter
of the URL. The
data that needs
to be updated will
be passed in the
input request.
DELETE/{id} It moves existing The entity id
order in the needs to be
system to
passed in the
Resolved-
Cancelled state. path parameter
of the URL
while
performing this
operation

Note: In PATCH operation the updated JSON should contain all the line items as present in the
original creation request, even if there are no modifications done to those line items. To add a new
line item in PATCH request, add new line items in addition to line items in original request. If this is

Order Fulfillment Orchestration Accelerator Implementation Guide | 21

 Order Fulfillment Application Accelerator implementation guide

not done, there could be a mismatch between the clipboard structure of the amended order and
the case hierarchy. This is because the entire request data is copied to the CO clipboard structure
during amendment, but case hierarchy is altered only if there is a new line item to be added.
PATCH/DELETE operation cannot be performed once the order reached PONR
state/ResolvedCompleted/Resolved-Cancelled state.

API parametres

Parameter Description

externalId Holds externalId value and retrieves results that

matches

description Holds description value and retrieves results

that matches

orderDate Holds orderDate value and retrieves results that

matches

fields Comma separated property names of TMForum

need to be passed.

state Holds state value and retrieves results that

matches

Id Holds id value and retrieves results that matches

Note that when a Product order case is created using REST service and JSON input, the Product Order
case has a page property called PORequestInt which contains the entire input JSON as is. Certain critical
properties needed for case processing are copied over to .ExOrder page property in the Product Order
case using the data transform Accel-OF-API-CustomerOrder.CopyToCOReq_Rest. Extend this data transform
to complete the mapping of all properties. The following figure shows the clipboard structure for Product
Order case created using the REST service. Notice the presence of ExOrder and PORequestInt pages.
Ideally it is recommended only to have the ExOrder page with the mapping performed from the incoming
structure and not have a page property with an Int class structure in the work page.

Order Fulfillment Orchestration Accelerator Implementation Guide | 22

 Order Fulfillment Application Accelerator implementation guide

Service Ordering Management API (TMF 641).

Pega Order Fulfillment Accelerator (OFA) is certified on TMForum Service Ordering Management API (TMF
641). These APIs are designed with REST webservices protocol. Pega Order Fulfillment Accelerator
provides GET, POST, PATCH and DELETE API operations for Service Order resource.
The following are the benefits of TMForum APIs:
• Standard interface to integrate with OFA
• Reduces time to implement
For more details about TM Forum, see TMForum Home and API Page TMForum APIs.
The dedicated Service Package for TMForum APIs is serviceOrderingManagement. The input request and
output response format for each API is as per standard resource defined for TMForum Specification guide
v4.0.0. The error codes were also defined as per TMF Specification guide.
Please find the specification document reference here.

OFA Entity API Operation Description Request Response

Order Fulfillment Orchestration Accelerator Implementation Guide | 23

 Order Fulfillment Application Accelerator implementation guide

Service Order GET List It retrieves list of In URL few filters

all Service Order were passed as
entities present in Query string
the system parameters to
limit the response
data. They are:
• externalId*
• description*
• orderDate*
• fields*
• state*
• id*

OFA Entity API Operation Description Request Response

GET/{id} It retrieves single The Service Order

Service Order entity id whose
entity from details need to be
system retrieved will be
passed as input
through path
parameter in URL.
In URL few filters
were passed as
Query string
parameters to
limit the response
data They are:
fields*
POST It creates Service
order in OFA
Application as per
details passed in
the request JSON

Order Fulfillment Orchestration Accelerator Implementation Guide | 24

 Order Fulfillment Application Accelerator implementation guide

PATCH/{id} It updates
existing entity in
the system with
details passed in
the input request.
The id of the
entity which is
being updated
needs to be
passed in the
path parameter
of the URL. The
data that needs
to be updated will
be passed in the
input request.
DELETE/{id} It moves existing The entity id
order in the needs to be
system to
passed in the
Resolved-
Cancelled state. path parameter
of the URL
while
performing this
operation

Note: In PATCH operation the updated JSON should contain all the line items as present in the
original creation request, even if there are no modifications done to those line items. To add a new
line item in PATCH request, add new line items in addition to line items in original request. If this is
not done, there could be a mismatch between the clipboard structure of the amended order and
the case hierarchy. This is because the entire request data is copied to the CO clipboard structure
during amendment, but case hierarchy is altered only if there is a new line item to be added.
PATCH/DELETE operation cannot be performed once the order reached PONR
state/ResolvedCompleted/Resolved-Cancelled state.

API parametres

Parameter Description

externalId Holds externalId value and retrieves results that

matches

description Holds description value and retrieves results

that matches

orderDate Holds orderDate value and retrieves results that

matches

Order Fulfillment Orchestration Accelerator Implementation Guide | 25

 Order Fulfillment Application Accelerator implementation guide

fields Comma separated property names of TMForum

need to be passed.

state Holds state value and retrieves results that

matches

Id Holds id value and retrieves results that matches

Note that when a Service order case is created using REST service and JSON input, the Service Order case
has a page property called SORequestInt which contains the entire input JSON as is. Certain critical
properties needed for case processing are copied over to .ExOrder page property in the Service Order
case using the data transforms Accel-OF-API-CustomerOrder.CopyToSOReq_Rest. Extend this data transform
to complete the mapping of all properties. The following figure shows the clipboard structure for Service
Order case created using the REST service. Notice the presence of ExOrderand SORequestInt pages.
Ideally it is recommended only to have the ExOrder page with the mapping performed from the incoming
structure and not have a page property with an Int class structure in the work page.

Order Fulfillment Orchestration Accelerator Implementation Guide | 26

 Order Fulfillment Application Accelerator implementation guide

Extending Order Fulfillment Application Accelerator

Customize and extend the features of Order Fulfillment Application Accelerator to meet your business
needs.

• Implementation approach
• Creating a new operator ID
• Creating a new application
• Updating dynamic class referencing
• Updating the access group of the service package
• Updating the fulfillment association data records
• Creating new fulfillment tasks
• Configuring a default email account

Implementation approach
Learn about the required team members and effective planning strategy in a general Pega
implementation to ensure a successful implementation of your application.

• Team responsibilities
• Roles and responsibilities

Team responsibilities
Organize your implementation team to provide the knowledge and experience that application
development requires.
Ensure that the following roles are present in your team to develop the application and to use
the reference application as a guide: •Lead System Architect
• Four Senior System Architects
• Quality Assurance Tester
The team members must have at least three years of experience in their current roles. A business analyst
and product owner can address any Phase 2 work. The reference application provides the definition for
the process for your first release. Therefore, you do not need a business analyst or a product owner for
your first release. The business analyst and the product owner can address any work in the subsequent
release.
You can build your team with employees from your institution, partners, or Pega Consulting. f you want to
have Pega Consulting on your team, contact your Pega account team.

Roles and responsibilities

Understand the roles and responsibilities of the client and Pega employees for the implementation of
your application.

Client responsibilities

• Provide the environment for the solution.

• Ensure security is applied to the solution.
• Download the application ruleset and the related collateral.

Order Fulfillment Orchestration Accelerator Implementation Guide | 27

 Order Fulfillment Application Accelerator implementation guide

• Review the collateral that is provided with the reference application, including documents and
videos, to help you understand the application.
• Develop your own solution.
• Test for quality assurance.

Pega

• Provide the Order Fulfillment Application Accelerator application ruleset and supporting collateral.
• Provide guidance as needed through your account team.
• Provide technical support through the Pega Support organization for any issues with Pega Platform.

Creating a new operator ID

Create a new operator ID to run the New Application wizard. For an application user, an operator stores
the identifying information such as, user name, password, and so on. Each operator has a role that
determines the actions that the user can perform.

1. Log in to Dev Studio with an administrator account, for example administrator@[Link], and the
password for that operator.
2. Save a copy of the administrative operator record and give that entry a name that identifies the new
record as an application setup operator, for example, OrderFulfillmentAppSetup.
3. Add the OrderFulfillment:AppSetup access group to the new operator record, and then click the radio
button to the left of the access group to select that group as the default access group.
4. Optional: To update the password, ....
5. Save the new application setup operator.

Creating a new application

Create a framework layer and an implementation layer.
A framework layer contains reusable application elements and provides an application that you can use
as the base for several applications in production. To create a composite application that targets a specific
organization or division, the contents of the implementation layer extend the elements of the framework.

1. Log in with the new application setup operator ID.

2. On the New Application landing page, select the ProductOrder or ServiceOrder application, and then
click Continue.
All the built-in cases of the Order Fulfillment Application are displayed.
3. In the list of built-in cases, review and select the following case types for your application: Customer
Order, Product Order, and Product Order line items.
4. Click Continue.
5. Click Continue.
6. Enter your application name, and then click Advanced configuration.
7. In the dialog box with the implementation layer settings, update the division, unit, and class structure,
and then click Generate reusable division/unit records.

Order Fulfillment Orchestration Accelerator Implementation Guide | 28

 Order Fulfillment Application Accelerator implementation guide

Warning:
The data that you enter on this screen and in the advanced settings is important. Perform this
task with your Lead System Architect to ensure that you have the right starting class structure.
The New Application wizard validates the length of class names in the expanded Case class
structure section and generates error messages if the names are too long (56 char). There are
a few class names, such as Accel-OF-Work-FulfillmentType-AssignSwitchIPAndGateway that are 54
characters in length and may generate a warning when the New Application wizard generates
new class names for the application. Shorten the last segment of the new class name to meet
the required length of 56 characters. Review the Case class structure to view any exceptions.
8. Save the changes, and then click Create Application.
This action takes a while to complete. The New Application wizard updates the access group of the
current operator to include an administration access group of the new application. You can now create
a new administrator operator for the new application.
9. Open the new application by clicking Go to app.

Updating dynamic class referencing

Update the class references to reference the new application implementation classes. Various rules have
references to the accelerator application classes.

1. Update data transforms:

a. Save the [Link] data transform in the implementation ruleset, which is
created in the implementation layer.
b. Change the values in the data transform with the newly created implementation classes in the
implementation layer.
c. After you update the data transform, check the results and values validated to the latest
implementation classes by running the D_AppExtension data page.
2. Update the class reference or object type of the D_ProductOrderLineItem data page from Accel-OFWork-
ProductOrderLineItem to the new value that you created in the New Application wizard for a new
implementation layer.
3. Update the class reference or object type of the D_CustomerOrderDetails and D_ListPOFilteredData data
page from Accel-OF-Work-CustomerOrder to the new value that you created in the New Application
wizard for a new implementation layer.

Updating the access group of the service package

• Change the access group of the serviceOrderingManagement service package to the access group
of the new application.
• Change the access group of the productOrderingManagement service package to the access group
of the new application.

Updating the fulfillment association data records

Update any records that exist in the initial deployment, and then configure the Order Fulfillment
Application Accelerator classes to reference the new application classes. The fulfillment association data
records map customer order specification to the appropriate fulfillment case types.

Order Fulfillment Orchestration Accelerator Implementation Guide | 29

 Order Fulfillment Application Accelerator implementation guide

1. In the navigation pane of Dev Studio, click Data types.

2. Click the Records tab.
3. In the Fulfillment Type column, double-click each class name, and then replace the classes with the
classes that you created during implementation.
4. Confirm your changes by clicking Save.

Creating new fulfillment tasks

When you create a new service order or a resource order case, the class must have inheritance from
the FulfillmentType class in the implementation layer. The class Accel-OF-Work-FulfillmentType is the
corresponding class in the base application.

1. Copy the necessary stage rules to the new case type. The following stage rules
are required:
• Initialization
• Wait For Child Case Dependencies
• Resolution
• Wait for Dependency – Alternate Stage
The following figure shows a sample case type rule for Activate Switch. The business logic for the new
case type must go into the Configure Switch stage. You must copy the remaining stages over without
any changes for the order line item dependency and catalog dependency to work. You can extend the
Initialization stage to copy over any case-specific data from the order XML.

Sample case type

Configuring a default email account

Configure an email account that references the client-specific email server configuration to run the flows
in your application that require an account. Order Fulfillment Application Accelerator does not provide
any out-of-the-box correspondence templates.

Order Fulfillment Orchestration Accelerator Implementation Guide | 30

 Order Fulfillment Application Accelerator implementation guide

1. Log in to your implementation application.

2. In the navigation pane of Dev Studio, click Records.
3. Expand the Integration-Resources category, and then click Email Account.
4. Update the client-specific settings as necessary.
5. Save the changes, and then click Test connectivity.
If the connectivity text is successful, the application displays the status as Good.
6. After saving the rule, click Test Connectivity to check the rule.
7. Optional: Configure the Receiver settings.

Order Fulfillment Orchestration Accelerator Implementation Guide | 31

 Order Fulfillment Application Accelerator implementation guide

Appendix A Order Hierarchy Schema

Order Fulfillment Orchestration Accelerator Implementation Guide | 32

 Order Fulfillment Application Accelerator implementation guide

Order Fulfillment Orchestration Accelerator Implementation Guide | 33

 Order Fulfillment Application Accelerator implementation guide

Order Fulfillment Orchestration Accelerator Implementation Guide | 34

 Order Fulfillment Application Accelerator implementation guide

Order Fulfillment Orchestration Accelerator Implementation Guide | 35

 Order Fulfillment Application Accelerator implementation guide

Appendix B Order fulfillment data classes and

database mapping
Order fulfillment data class Data model component Database table

Accel-OF-Data-Customer Custom use pr_accel_of_data_customer

Accel-OF-Data- Fulfillment association pr_accel_of_data_fulfillmentas

FulfillmentAssociation

Accel-OF-Data-OrderActions Fulfillment association pr_accel_of_data_orderactions

Accel-OF-Data-OrderItemActions Fulfillment association pr_accel_of_data_orderitemacti

Accel-OF-Data-OrderRequest

Accel-OF-Data-SearchDetails Fulfillment template search

n/a
gadget
D_SearchDetails
D_SpecificationTypeList

Accel-OF-Data- Fulfillment template –

D_SpecificationHierarchy
SpecificationDetail maintenance
D_SpecificationList
D_SpecificationRowDetail

Accel-OF-Data-SpecificationType of_data_specificationtype

Order Fulfillment Orchestration Accelerator Implementation Guide | 36

 Order Fulfillment Application Accelerator implementation guide

Appendix C SpecificationDetail structure - Fulfillment

template

Property class Property Property mode Type Embedded class

Accel-OF-Data-
SpecificationDetail
Accel-OF-Data- CatalogDependencyListPage list Page list Accel-OF-Data-
SpecificationDetail
Dependency

Accel-OF-Data- SpecDescription Single value Text

Dependency

Order Fulfillment Orchestration Accelerator Implementation Guide | 37

 Order Fulfillment Application Accelerator implementation guide

Accel-OF-Data- DependentCaseID Single value Text

Dependency

Accel-OF-Data- DependentSpecID Single value Text

Dependency

Accel-OF-Data- DependentOn Single value Text

Dependency
Accel-OF-Data- Single value Text
Dependent
Dependency
CaseLabel

Accel-OF-Data- Single value True / False

Dependency
Dependency
Satisfied

Accel-OF-Data- ChildSpecification Page list Page list Accel-OF-Data-

SpecificationDetail SpecificationDetail

Accel-OF-Data- Single Text

Concatenated
SpecificationDetail value
DependencyList

Accel-OF-Data- Description Single Text

SpecificationDetail value

Accel-OF-Data- PONRIndicator Single Text

SpecificationDetail value

Accel-OF-Data- SpecificationID Single Text

SpecificationDetail value

Accel-OF-Data- SpecificationPath Single Text

SpecificationDetail value

Accel-OF-Data- SpecificationType Single Text

SpecificationDetail value

Appendix D Defining additional dependencies at the

top-level in Order Fulfillment template
This appendix describes how to enhance the fulfillment template feature to define additional
dependencies at the top-level nodes for the Product Manager. The out-of-the-box dependency
capabilities of the Order Fulfillment Template are described in earlier sections of this document.
The following are the topics covered:
• Cross-Product dependency enhancement
• Storing additional dependencies
• Retrieving additional dependencies
• Displaying additional dependencies

Order Fulfillment Orchestration Accelerator Implementation Guide | 38

 Order Fulfillment Application Accelerator implementation guide

Cross-Product dependency enhancement

Currently, Order Fulfillment Template allows defining dependencies only across siblings when defining a
certain specification. In certain industries there can be a requirement to define dependencies that span
beyond siblings. These dependencies are different for each top-level specification (for example, Product
in the case of Communications vertical). Some of the dependencies cannot be tied to an individual
specification but need to be defined when defining a product and can span across multiple levels in the
specification hierarchy.
In the example given below, for the top-level specification called Fiber Service, Order Fulfillment
Template currently allows you to define dependency on Add Access, Add Link, and Add Internet Service for
Notify Billing. However, it is not possible to define a dependency for Add Link on Procure CPE or Add
Internet Service on Procure Access. This cross, Product Line Item dependency could be a valid
requirement and this dependency might exist only for Fiber Service. When the same specifications are
added as child specifications to another top-level specification like Cable TV, these might not be required.
So it is necessary that these additional dependencies are linked to the specific top-level specification only.

Retrieving additional dependencies

The D_SpecificationDetail data page is sourced by the GetSpecificationDetail data transform.
Step 2.8 of the data transform has the logic to append any additional dependencies in
DependencyOverride data type to the CatalogDependencyList pagelist along with other catalog
dependencies defined against each child specification. Step 2.11 handles setting the property
ConcatenatedDependencyList. In the out of the box version, this only sets a comma separated list of
specification names. But in this case we need the entire path as well. Here the data transform needs to be
overridden so that the entire path can be set to this property. The DependentOn property contains the
specification ID path. The D_Specification data page should be used to fetch the specification names
from these specification IDs and a new comma separated string should be created from the specification
names.

Appendix E Support of Modify, Change and Delete

operations of OFA Accelerator
The order management capability of the current OFA application caters to the requirement of the
Communication service provider (CSP) for a fulfillment system that supports ADD operation at the
order level and the order item level. The other operations Move, Change and Disconnect can also be
configured in a few steps provided that the fulfillment cases with appropriate business logic is added
to the fulfillment type class.

Steps for implementation

Step-1: Fulfillment cases should be first added to the fulfillment type class as per the details outlined
in the section Creating new fulfillment tasks above. The Initialization, Wait and Resolution stages must
be copied to the new case to facilitate dependency logic to work.
Step-2: These new fulfillment classes should be associated to the existing fulfillment cases or optionally
define new cases (with class association) with appropriate combination of order action and order item
action. Fulfillment association landing page of end user portal can help in associating them. Refer to

Order Fulfillment Orchestration Accelerator Implementation Guide | 39

 Order Fulfillment Application Accelerator implementation guide

Specification and Task Fulfillment Association/Fulfillment Association/Fulfillment Association maintenance

process sections of this guide for more details.
Step-3: The CreateFulfillmentCase activity of the Accel-OF-Work-ProductOrderLineItem class has the
logic of creating the fulfillment case of appropriate class that was defined in the fulfillment association
data type.
The logic in the activity, step-1 handles support of case creation without any errors defaulting the order
action and order item action to ‘ADD’ if the XML/JSON input request sample does not have these
attributes (for example, ExOAction at Order level and ExOIAction at each item level for an XML input).
The logic in the activity step-4 also handles picking the right class for fulfillment case creation if present in
association data type. If not, it defaults to fulfillment type class (shell class with business logic of waiting
for a minute) defined from the application extension data transform ([Link]).
Above activity steps can be altered if custom exceptions to be thrown in case processing instead of
creating the fulfillment cases with default processing conditions.
Step-4: If there are any existing child relations defined in the local service catalog (child cases to be
created if defined in the Accel-OF-Data-CatalogEntry), the order action and the item action fields are
cascaded (along with dependencies) to these cases too to identify the appropriate fulfillment class with
respective combination.
Activity CreateChildFulfillmentCases of the class Accel-OF-Work-FulfillmentType has similar logic of step-3
stated above (at activity step-2 and 4.2) for child fulfillment case creations.

Known issue

Description Suggested resolution

The to-do list (pyAssignmentListGadget section) Install the OFA application on Pega Platform
in a case does not render when you install the 8.6.1 or upgrade to Pega Platform 8.6.1. The
OFA application on Pega Platform 8.6, or when issue is resolved in Pega Platform 8.6.1.
you upgrade from Pega Platform 8.5.1 to Pega
Platform 8.6.

Order Fulfillment Orchestration Accelerator Implementation Guide | 40