We have a requirement to allow users to update a specific business field in their operator record. To achieve this, we need to build a UI layout that displays the operator’s basic details along with a radio button to change the value and save the update.
Please note that we only need to update the single, currently logged-in operator record..
Sample UI Layout (Show the operator basic details and a radio button to change values and save)
We tried to leverage the CRUD operation approach shared in the thread below (CRUD Operations for Operator Records via Landing Page). However, that solution only works with list-type data structures, whereas we need to update only the current operator’s record.
While the other approach shared in the forum is close to what we need, it requires custom development
Could you please advise if there is a more standard way to achieve this?
As of now, the out-of-the-box (OOTB) approach remains the list-based method shared in that first approach. You can technically configure the list to filter and return only a single record—matching the currently logged-in operator—and allow the user to edit it there. However, this means compromising slightly on the UI, as it will fundamentally still be a list layout displaying a single result.
If maintaining a strict, seamless user experience is your top priority for this requirement, implementing a custom DX component is going to be your best path forward.
We have a similar use case for the business users to update the skills/Access groups for a specific operator. We have used Case Type to accomplish this behavior. We used the Post Processing Activity in the Flow action to update the Operator record.
Hi, two options as properly called out already either, custom DX component that will give you freedom to design UX or wrapper case type to mange the update process.
If you use a card/gallery view for your “list of one” then you can show the current operator record in a nicer way (than table)
This has the added advantage of being reusable for managers who may want to manage their team (its a list, so will expand based on your definition of the list shown for each persona)
Use a case to manage the operator record (with the saveable datapage approach). You can improve the UX by using the “quick links” case launcher to make it a button on your desired landing page. This also has the advantage:
Is a process, so can include things like approvals
Is a case, so can include showing other details and contextual guidance on the screen
Is a case, so contains an audit history of changes for that operator record
Thank you all for the suggestions. CURD operation landing page with Gallery view, Case Type or Custom Component. Lets us try and see which we can convivence the business.
