how to configure Actions set in constellation
Hi,
I traditional section based UI, we have multiple actions set for on-click, On-change of cell properties,like run data transform, refresh the section, open assignment, open workitem by handle, launch Local action. But in constellation, I am not finding those features, is there any alternate way to do this actions?
Accepted Solution
Updated: 18 Jan 2024 6:32 EST
Pegasystems Inc.
US
@Rakeshr7 Excellent question!
Our vision includes:
- Drastic reductions in development time
- An OOTB UX, optimized for efficiency and "guided workflow" -- with Accessibility and front-end best practices built-in.
- Seamless UI upgrades
- Consistency across the application stack
- Extensibility
This enables designers, the business, and engineering to work shoulder-to-shoulder, focusing on the outcomes they want to achieve instead of heavy design and development of a highly customized UI.
Most of common patterns developers were building (often repeatedly) with UI controls and Action Sets are offered OOTB, configurable in App Studio.
When used in a View, Data Reference and Case Reference field types automatically render links to the preview panel or a case, so you don't need to call open work or open assignment. The ability to expose Local Actions can be configured in App Studio.
Here's a write-up on why you likely don't need Action Sets in Pega Infinity Constellation UI:
https://community.pega.com/blog/goodbye-action-sets-cosmos-react-yes-good-reason
You might also be wondering how you achieve dynamic form behavior without manually specifying on change event handlers. That is described here:
@Rakeshr7 Excellent question!
Our vision includes:
- Drastic reductions in development time
- An OOTB UX, optimized for efficiency and "guided workflow" -- with Accessibility and front-end best practices built-in.
- Seamless UI upgrades
- Consistency across the application stack
- Extensibility
This enables designers, the business, and engineering to work shoulder-to-shoulder, focusing on the outcomes they want to achieve instead of heavy design and development of a highly customized UI.
Most of common patterns developers were building (often repeatedly) with UI controls and Action Sets are offered OOTB, configurable in App Studio.
When used in a View, Data Reference and Case Reference field types automatically render links to the preview panel or a case, so you don't need to call open work or open assignment. The ability to expose Local Actions can be configured in App Studio.
Here's a write-up on why you likely don't need Action Sets in Pega Infinity Constellation UI:
https://community.pega.com/blog/goodbye-action-sets-cosmos-react-yes-good-reason
You might also be wondering how you achieve dynamic form behavior without manually specifying on change event handlers. That is described here:
For the best value, we encourage clients to leverage our OOTB patterns where possible. Of course, for advanced, app-specific use cases, Constellation is also extensible where you can build a custom component using React and the web technologies, where you programatically assemble Constellation's presentational components to build something new; in that scenario, you can define on click and other event logic.
Again, I urge caution. Only leverage custom components for advanced, app-specific use cases. My favorite example of when a custom component is reasonable is a Pega workflow app that interfaces with a finger print reader attached to the computer which captures a finger print and saves it into the case. Obviously, we do not ship a "finger print reader" component. For this advanced, app-specific use case, you'd build a custom component, programmatically assembling a Constellation Button (to initiate the scan) and a Constellation field to hold the image. In the click action on the Button, you'd use the JS api to the finger print reader, capture the image, and then set the image in the field.
Hope this helps.
Sam
Pegasystems Inc.
CA
@Sam Alexander Thank you for your detailed comments!!!
Just curious to know about the below use cases,
1) if there are requirements to display Product-related information based on the Product ID. For example: In Traditional UI, the user will input Product ID as an input, and we trigger the data page on the change event to get the Product Model#, Product Name, Product Description, Product Family, etc... and it will be auto-populated on the screen.
2) Cascading drop downs - In traditional UI, we load the subsequent dropdown on the change event baed on the input selected for the current dropdown and refresh this section to show the updated results on the screen.
Could you please share your thoughts on how these can be implemented using Constellation?
Appreciate your help!
Thanks,
Updated: 5 Dec 2023 15:11 EST
Pegasystems Inc.
GB
On point 2 you may find the following documentation of interest. No explicitly defined on change event is needed in constellation.
Pegasystems Inc.
US
@RameshSangili for scenario 1 - this is achieved by using a single reference field - the user will see a dropdown / combobox of the available case types - the 'show as a picker' option will let you select a view that will render other info about the case (Product name, product description...)
Virtusa
IN
@RichardMarsot I have Requirement .. in View i am using a Table with 6 columns and second column should be a link on click of that link i have to should Display all dataobject of the respected record other than the 6 details 1) How configure popup on link in table as i could not see any option.. 2) How to pass param of specific record to datapage to load specific record. Thanks & Regards