You would basically be creating a new widget from scratch if you wanted the same functionality as the sc_order_status widget, we just went through this same thing as we are now using order guides on HR Cases, here is what we did, which I think is simpler, a fair bit quicker & keeps it more OOTB:
- Add a new boolean field to the sn_hr_core_case table.
- In your order guide add a new variable boolean that is always set to true, have cascade variables on.
- On each of your record producers that are part of the order guide create a boolean variable of the same name, hide it and map it to the custom field you just created on the sn_hr_core_case table.
- This new variable will now only be populated when these producers are ordered as part of an order guide.
- Create a new record producer, this is going to be your parent (sc_request) that will hold all of the child cases that are part of the order guide, make sure to tick on "no search" and to add your order guide variable and requested for so these cascade down from the order guide.
- Configure a new HR Service for this record producer (not going to go through these steps as it's straight forward) but configure to your needs along with your template and link it with your record producer.
- Create a flow with the following steps:
- Trigger off of your HR Service you just created.
- Wait 10 seconds for the record producers to create the records.
- Lookup the created records using your is order guide field, hr service and any other conditions you want to add.
- Error handling if no records are found.
- For each record update the "Parent" field, we are using the task table as this relates to all our HR tables custom or not, use one that suits you. For record keeping you should change your HR Service fulfillment type to "Flow" and add the flow there (this field doesn't trigger anything, it just helps the next developer that comes along find your work, so be kind :))
This takes care of everything on the backend and your cases will now be linked to the parent case via the OOTB "Parent" field, we had the "Child Cases" related list already down the bottom of our cases and I'm pretty sure this is OOTB, if not setup the related list.
Now to the front end, setup a new page on your portal (not going to go through all the steps and plenty of video guides out there) but the main bit you have to do here is add the OOTB simple list widget, you can also add anything else you feel is good for the page, this will be the page the end user will see when they submit your order guide so we also opted for a bit of HTML to show that up the top.
Open up your custom page and ctrl right click on the simple list widget and click on "Instance Options", here is where the magic happens, add sn_hr_core_case as the table, your filter we opted for this
active=true^opened_atONLast minute@javascript:gs.beginningOfLastMinute()@javascript:gs.endOfLastMinute()^ORopened_atONCurrent minute@javascript:gs.beginningOfCurrentMinute()@javascript:gs.endOfCurrentMinute()^opened_byDYNAMIC90d1921e5f510100a9ad2572f2b477fe^u_is_order_guide=truewhat you want it to display in from the fields, linking behavior and anything else you want, which will look something like below when done.
12. We now need to redirect to this page after the user submits, the widget that does this is SC Order Guide you need to clone the widget, go into the client controller and search for
13. Almost there! Go to the default order guide page sc_cat_item_guide and edit it in page designer, remove the default widget SC Order Guide and add your custom one in it's place
14. Job done from that side of things! The My Requests widget won't show child tasks as a default behavior so only the parent case will show, as a nice to have we added a "Linked Requests" tab to the ticket view so that users can see exactly what's going on, again plenty of video's out there on how to achieve this but it looks like below
Hope this is helpful and happy to answer questions if I've missed anything out as there are quite a few steps, I believe this to be a better way of doing instead of recreating the whole widget from scratch.
