Recreating Case Creation process for my service catalog
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-20-2022 09:44 AM
Hi,
I installed HR app in my PDI and saw a feature/customization I liked. When I click on Create New Case, I am presented with a screen that shows verification. (I skipped it since I don't' care for this screen.) The next screen, shows the Case Details. This screen has 4-5 fields. Once the user fills in the mandatory fields and click create case, the form will be redirected to whatever HR service form was selected. (Looks like each HR Service is its own record producer.).
How do I replicate these forms and process (not including the Verification check form)? I attached 3 screenshots of the forms I want to create.
Can someone break this down for me in simple explanation and show me how this was created so I can create the same for my custom service catalog?
My requirement:
I have 3 custom tables. 2 are child tables of the parent. When I create a record from child table, the same record shows in the parent table (once), which is fine. However ,when I create a table from parent record, it does not create the same in child table. So, I created a flow to handle this part. The flow is creating a record in the child table, but this child record also shows up in the parent table list view, so now there are 2 records in the same parent table list view. IF I can replicate the feature explained above, I will have 1 simple form to intake data for 4-5 fields, then submit the record and show the other fields that pertain to that HR service form.
How can I do this??

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-20-2022 03:49 PM
The HRSD case creation form uses a custom UI page to handle the creation process. It's bespoke to the HRSD application and would require you to have jelly/angularJS knowledge in order to create something similar that works for a custom-non HRSD application.
A simple solution is to use a record producer to do the work with the necessary script logic to generate the records you want.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-21-2022 05:26 PM
Hi Kieran,
When you say to use a record producer and a script logic, do you mean to script something in the Script section of the record producer? How would this work if I use my record producer (parent table) as the main area where the logic lives? Can you elaborate on your answer a bit more? Are there any sample codes to you provide?

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-22-2022 01:01 AM
You can run any server side logic in that script box, so if you're wanting to create child records based off information provided in the record producer, you can reference it in there at the same as the main "parent" record is being created.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-25-2022 06:31 AM
As of right now I have 3 tables. 2 of those tables are children of the 1 parent table. Are you saying that I can add script to the parent record producer to create child records in the other 2 table? If so, do you have an example script? When I create a record in the child table, it automatically shows up in the parent table. So, if I create the record in the parent table, will it show up in the child table?