Opening data record from semantic URL and editing it

User Experience
1

Hello,

I have a requirement where a user clicks on a link from an external (non-Pega) application, and it should open a screen in Pega Constellation. The URL contains parameters, and based on those parameters, we need to fetch data via an API and render a UI.

:small_blue_diamond: How This Was Done in Theme Cosmos

In Theme Cosmos, this was straightforward using URL Mappings:

  • Capture URL parameters

  • Use an activity to initialize data

  • Launch a landing page directly

:small_blue_diamond: Approach Taken in Constellation

Since Constellation is data-model driven, I changed the approach:

  1. External system calls an API → Creates a record in a Data Type

  2. I generate a link like: sampleURL/prweb/PRAuth/app/dmt/data/document?dataViewName=D_DocumentDMT&pyGUID=dc086956-f155-46e7-b352-ac3ddb46142f&portal=WebPortal

  3. When the user clicks the link:

    • The record opens correctly in Full Page View

  4. From the Actions menu, the user clicks Edit

    • On Edit, I call an API to fetch details and display them

    • On Submit, I call another API to push changes back to the external system

Problem

The Full Page View renders correctly, but:

:magnifying_glass_tilted_left: My Questions

  1. In Constellation, is directly opening a Data record using dataViewName + pyGUID via URL officially supported?

  2. Is there a recommended pattern in Constellation for:

    • Launching a record from an external URL

    • Enabling full CRUD behavior (including Edit)

Any guidance on the recommended architectural pattern in Constellation for deep-linking into editable records would be highly appreciated.

Thanks in advance!

2

@VVNagaSaiN have you read this article from our Constellation 101 series?

it outlines how the semantic URL works and the example for data instances. It also talks about the routing table, which you might have to regenerate.

Actions on data, would come from your configuration on the actions for that data object?

“data view not found” i think the problem with actions not showing etc. are coming from this error, i’ve commonly seen this in versions before 25, where the datapage for the data object was not set to “api” but it can also be something to do with another permissions. I would raise an incident with My Pega Support to get that investigated.

3

@VVNagaSaiNIf you see the same behavior directly inside Pega, I would suggest to start by looking at the data object and confirming you have a default savable data page configured.

4

@MarcCheong @LantzAndreas

I have generated the routing table again and yes the actions are configured in the actions of data type. Attaching a video recording that shows the behavior.

In the video, first, I have clicked on data record directly from table in portal and clicked on Edit in actions - It worked.
Next, From the table, I have opened that data record in new tab (which opens a tab with a link that is required in my use case) and then clicked Edit - It failed.

I will raise an incident with the Pega Support for further analysis as suggested. Thank you for the response.

ScreenRecording.zip.zip (1.6 MB)

5

@VVNagaSaiN definitely a support ticket - they would need to see more of your configuration.

I’m leaning towards the edit action not having a View attached to it? The action/view is not marked as a relevant record? Or the action has preprocessing in it (which is not supported on data). Lots of config to look at, Pega Support are the right people to help there.

Please share your INC or the outcome, would be good to have if others find this post in the future and have same issue.

6

@MarcCheong Created support ticket with Pega with ID INC-D7766. Seems like it is existing behavior and team is investigating it.

7

image
image1395Ă—336 56.1 KB

This is the solution given by Pega support. Seems like we need to edit the full page view of the data type at least once after creating the data type for it to work correctly.

1 Like