Designing options for invoice case handling
2 タスク
45 分
シナリオ
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 MDC's invoicing process. Currently, PKM has one accountant for each city.
PKM Accounting specializes in providing accounts-related support. PKM is flexible and can either support the accounting workflows defined by its clients, or build workflows for them upon request. 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 log in to the Delivery Service application. However, note that this challenge is mainly designed for you to evaluate the design options and has no specific implementation tasks.
| Role | User name | Password |
|---|---|---|
| Admin | admin@deliveryservice | rules |
詳細なタスク
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 that was built on 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 into the PKM dedicated website
Option 1 - Remote Case Type (PKM has an existing Pega Constellation workflow)
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 - REST API Integration (PKM has a legacy, non-Pega system)
Interact with the delivery service application from the legacy built PKM application using Pega standard REST services. The following table includes several out-of-the-box REST services that can be used to create a Case, get Case details, and perform assignment actions.
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, for security reasons 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 an Invoice Case in the delivery service application. |
| https://pegahost/prweb/api/application/v2/cases/{CaseID} | GET | Get Case details | Retrieves Invoice Case details including status and related data. |
| https://pegahost/prweb/api/application/v2/assignments/{assignmentID}/actions/{actionID} | PATCH | Perform an assignment action. | Executes actions such as approve, reject, or validate on Invoice Case assignments. |
Option 3 - DX APIs and React/Constellation SDK (PKM has a modern web application)
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 - Web Embed (PKM has a dedicated website, no Pega environment)
Embed the Invoice Case directly on the PKM dedicated website using Pega's Web Embed capability.
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 of 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, apply the best-suited option by weighing the following dimensions: available resources, maintainability, security, and implementation effort.
General LSA principles
-
Adopt a Constellation-first architecture for new implementations. This approach unlocks the full capabilities of Pega GenAI, Pega Process Fabric™, and the Pega SDK.
-
Plan for hybrid UI coexistence when PKM is in mid-migration. Pega Platform makes this approach more viable and cost-effective than before.
-
Prioritize security from the start. Address OAuth 2.0 registration, certificate management, and SSO federation during the architecture stage, not as post-implementation tasks.
-
Design for scalability and maintainability. Use these as primary selection criteria. Remote Case Types and web-embed solutions require ongoing maintenance, such as certificate updates and cookie policy changes. REST and SDK-based approaches can better abstract these complexities.