Hi, 

hoping someone may be able to help me with a DX component configuration I am trying to do for my project. I am using pega 23.1.3 on constellation. I have a business requirement for having users to upload required documents that are dynamic base on information they provide on previous tasks. Due to the fact that pega 23 constellation does not support attachments in data types yet we are uploading the required documents to a child case and displaying the list of child cases on the parent case.  

From the parent case the user can create a new document child case, edit or remove the document child case from the parent. I got the DX component working for all the actions, but it refreshes the browser each time when the user edits or remove the document child case while on the parent case and takes them to the confirmation screen for the child case.

The edit and remove actions are casewide local actions on the child case and are being called by using the openLocalAction DX API. To prevent the browser from being refreshed my understanding is that I can set the param "type" to "express" for the openLocalAction DX API because it is a separate context from primary page. However, even when I do this the browser is still refreshing and taking the user to the child confirmation screen. 

Would anyone be able to provide any insight on why this may be happening? I am bit unsure what I am missing from either the DXAPI side or from the pega configuration. 

@Kamil Janeczek In constellation if a list view is defined for the case type classes then we get the option for setting up "Bulk Actions". But in the application we are displaying a list from the workbasket that does not allow to configure "Bulk Action" in the view wizard. If the requirement is as simple as show case the assignments from a pre-defined queue and allow the user to do bulk transfer of those assignments how should that be implemented using OOTB constellation options?

@Kamil Janeczek The case types allow us to add case wide actions as well as stage specific optional actions but if somebody wants to implement classical behaviour of one single assignment in a stage having multiple connectors based on likely hood how to implement the same using constellation OOTB options. 

use case: A stage has 2 steps to invoke API from 2 systems and client expects fall back management in case of functional exceptions as well. One simple way to implement fallback is to route the flow to a step/assignment tagged to operations queue and build a view to show the list in the portal. The admin can reassign these assignments to support user based on their skills. 2 different API steps should have 2 different fallback assignments so that it can be associated with different skills as well as the instructions can be different. In the flow the assignments are looped back to original integrator shapes. Each fallback assignments should  have Actions like - Manual resubmission, Update Data and submit etc.

@Kamil Janeczek - We were configuring a screenflow in constellation and realized that it is not possible to jump from one step to another and users need to use the Next and Previous button. Is there a way to achieve this in constellation so that users can jump to a step without having to move sequentially across the screens?

@Kamil JaneczekDo you know of a way to not show a column, but still bring over data from the data page?  This column is also derived from an association:

@Kamil Janeczek I am currently working on implementing a client requirement that involves file uploads, specifically image files. The goal is to allow users to upload an image file and then immediately display the uploaded image (i.e., render the actual picture) below the upload input. Could you please advise on to how achieve this ?