Designing options for invoice case handling
2 Tasks
45 mins
Scenario
The Accountant system is a separate system dedicated to invoicing. PKM agency is an expert organization that provides accounts-related support to MDC and has access only to the invoicing process of MDC. Currently, PKM has one accountant for each city.
PKM Accounting specializes in providing accounts-related support to various clients in the market. PKM is flexible and can support the accounting workflow defined by its clients or build workflows for them if requested. In the current scenario, MDC designs, defines, and develops the accounting workflow required for product delivery. However, PKM accountants maintain and validate the payments and receivables.
The following table provides the credentials you need to login Delivery Service application. However this challenge is mainly meant for evaluating the design options. There are no specific implementation tasks.
| Role | User name | Password |
|---|---|---|
| Admin | admin@deliveryservice | rules |
Detailed Tasks
1 Identify design options
Consider the following points while designing a solution.
- PKM has a dedicated Pega workflow built by PKM.
- PKM has no Pega workflow application available; it has a system built in legacy technologies.
- PKM has a dedicated website built using the latest UI technologies; implement Pega UI into PKM by using DX APIs.
- Embed the Invoice Case in the PKM dedicated website
Option 1
If PKM already has a Pega workflow established in its accounting and invoicing processes, expose the Invoice Case from the delivery service as a remote Case to its existing workflow.
Prerequisites
The remote Case Type works well if the delivery service and PKM are built on Constellation only. Trust (certificates) between the delivery service and PKM must be frequently updated for maintenance activities.
For more information, see Implementing remote Case Types.
Option 2
Interact with the delivery service application from the legacy built PKM application using Pega standard REST services. The following table includes a few out-of-the-box REST services that can be used to create a case, get case details, and perform an assignment action.
Prerequisites
- Enable security between the delivery service and the PKM application by registering an OAuth 2.0 client.
- Update the trust (certificates) between the delivery service and PKM as required for maintenance activities.
Although you can use basic authentication, it is not a best practice for production applications for security reasons.
| Service | Method | Description | Comments |
|---|---|---|---|
| https://pegahost/prweb/api/application/v2/cases | POST | Create Case | Creates a Case in the PKM application. |
| https://pegahost/prweb/api/application/v2/cases/{CaseID} | GET | Get Case details | Get Delivery Request and Truck Request Case details. |
| https://pegahost/prweb/api/application/v2/assignments/{assignmentID}/actions/{actionID} | PATCH | Perform an assignment action. | Perform assignment action on the Delivery Request and Truck Request Cases. |
Option 3
Integrate the PKM website with the Pega application built by the delivery service by using the DX APIs and Pega React SDK.
Prerequisites
- The delivery service application must be built on Constellation.
- Enable security between the delivery service and the PKM application by registering an OAuth 2.0 client.
- Update the trust (certificates) between the delivery service and PKM as required for maintenance activities.
Option 4
Embed the Invoice Case on the PKM website.
Prerequisites
- Web-embed requires the use of cookies for authorization code redirect to implement the Pega Infinity Authorize Grant flow, because it relies on the Pega-RULES cookie.
- If the web-embed is on a different domain than the main document site, use a proxy server to proxy these transactions to the Infinity server in case the browser blocks third-party cookies.
For more information, see Creating web embed.
Benefits with this approach:
- Data is secured within the delivery service application.
- The delivery service application owns the workflow, actions, security, and so on.
- The delivery service team controls what data to share, view, and so on.
2 Recommended design option
Based on the technology available with PKM, you can apply the best-suited option within the scope of the listed prerequisites, considering available resources, maintainability, security, and effort.
Confirm your work
Available in the following mission:
Want to help us improve this content?