Best Practice Solution on Adding Additional Custom Fields to the Delivered HR Case Table
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-13-2020 09:13 AM
In 2018, we had to redesign our delivered HR Case [hr_case] table, adding additional fields based on Category [category] and Subcategory [u_subcategories] fields, toggled by UI Policies.
As an example, here in DEV I created a ticket for one of our categories and subcategories. These fields I have circled get toggled depending on what you select in the “Category” and “Subcategory” fields.
Since the original upgrade, we have a total of 76 custom fields in the HR Case [hr_case] record in production.
According to the official "Custom Table Guide", the official threshold for “Now Platform® App Engine Enterprise” is 100 fields.
The needs of our HR department continue to grow, and we need more support for more fields. Right now we have two new requests to add 40 additional fields.
So my first question, will the system continue to allow us adding fields after reaching the "threshold."
If so, what would be the impact on our system if we continue to add these fields.
Finally, what other alternatives could we explore to meet our customer's needs?
- Labels:
-
Now Platform App Engine
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-14-2020 09:41 AM

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-14-2020 10:15 AM
No, You need to navigate to form layout. please find the screenshot below for reference.
Select the reference field click on the expand selected reference field icon highlighted and you will be able to see the fields from reference table in the available slush bucket. Select the field and with the help of arrow bring that in selected bucket and save the form. For you reference I selected the parent description and you can see the highlighted field in the selected bucket that it shows "Parent.Description" so not the description of the parent field will be available on the catalog task form. Also, OOB the "Requested for" field available on the catalog task form is a field from Request table.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-14-2020 10:16 AM
This dot walking can be done for any of the reference field. I used parent field just for an example to show you how this could be done.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-14-2020 11:33 AM
Ok so in the sc_task, I dot walked a "requested item" (there is no "parent" field in the form layout tool) and added "Duration" field to a catalog task.
One thing I noticed that the field was "read-only." This could be a problem in some of our applications where the HR team has to set the values.
Although this is good to know, unfortunately I am trying to add fields to the HR Case [hr_case] table, and not Catalog Task [sc_task].
There is no "parent" field in the hr_case. Also I am pulling data from the record producer, not a "parent." So what field would I use in hr_case?

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-14-2020 12:26 PM
I referred catalog task table and parent field just to give an example.
Since, we do not know what reference fields you have on the HR Case table and what you want to get populated on the new custom field. It's really difficult to say.