Each formula case comprises of Ingredients. Users typically work with 4-5 formulas at the same time mixing ingredients in different concentrations to create variants. One of them will eventually be sent for Compounding where a lab technician will produce the actual fragrance given the formula.
There is a requirement for users to work on multiple formula cases. Attached screen shot will give further insight into the problem statement.
@Salil thanks for asking the question.
Out of the box editing looks like this, which can be enabled on List Views or Insights.
You can see the design paradigm is very different to your screenshot from your DX Component. Even in the list context, the concept is to show the data and allow you to edit one by one, you can also edit inline if its a list view (though not immediately obvious).
In your example, you need a DX Component for a few reasons
In this case, the question isn’t really about Pega’s OOTB approach for editing multiple cases, now you are moving into the PCore/Pconnect and DX API space (maybe even SDK). The component would need to orchestrate the right calls to update each case as needed.
It should be stated this isn’t the fastest time to value, but one chosen to implement certain design and interaction patterns that are required.
Some resources that might help when it comes to DX Components.
