- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-02-2022 07:57 AM
Hi,
For a task extended custom table, if we use the parent field to mark any other task as parent does it inherit any functionality as part of this field? We are planning to create a new field specific to it as our task table also is custom one. But also looking at possibility to reuse parent field. But we dont want any additional overhead to manage states or closure scenarios.
Functionalities like parent cant be closed when child is open or any such OOB functionalities etc.
Any feedback here is appreciated.
Regards
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-02-2022 08:22 AM
Hi,
My 2 cents would be to use the oob parent field. There is no overhead as you have a custom table.
-Anurag
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-02-2022 08:22 AM
Hi,
My 2 cents would be to use the oob parent field. There is no overhead as you have a custom table.
-Anurag

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-02-2022 08:27 AM
Hi,
Parent is just another reference field. You can disable the BR that auto closes the child task if you feel this feature is not required.
Thank you,
Palani
Palani