- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-23-2023 05:55 PM - edited 11-23-2023 05:56 PM
Could someone please give me a list of all the tables necessary to create a scoped custom application that needs to implement Incident and Change Management?
I need to know which all tables should be inherited and be part of this application's scope for it to work properly.
Solved! Go to Solution.
- Labels:
-
Change Management
-
Incident Management
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-23-2023 07:04 PM - edited 11-23-2023 07:05 PM
Hi @Navaneeth1
Are you trying to re create the full Incident and Change management are just extend the existing functionality?
If you want to have list of tables that are dependent used, you can open the schema map of the Incident table and can see all the tables related to Incident table and Change table.
1. Navigate to System Definition -> Tables, then in the list opened, Search for incident tableusing name field and open the incident table record.
2. Scroll down to the Related Links section and click on Show Schema Map related link.
3. In the Page opened, enable all 4 check boxes, Show Referenced fields, Show Referencing Fields, Show Extended Tables and Show Extending Tables.
4. You can see all related tables to Incident module and you can decide what are all needed based on your requirements.
Follow the same approach for change_request table.
Please mark my answer helpful and accept as a solution if it helped 👍✅
Anvesh
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-23-2023 07:04 PM - edited 11-23-2023 07:05 PM
Hi @Navaneeth1
Are you trying to re create the full Incident and Change management are just extend the existing functionality?
If you want to have list of tables that are dependent used, you can open the schema map of the Incident table and can see all the tables related to Incident table and Change table.
1. Navigate to System Definition -> Tables, then in the list opened, Search for incident tableusing name field and open the incident table record.
2. Scroll down to the Related Links section and click on Show Schema Map related link.
3. In the Page opened, enable all 4 check boxes, Show Referenced fields, Show Referencing Fields, Show Extended Tables and Show Extending Tables.
4. You can see all related tables to Incident module and you can decide what are all needed based on your requirements.
Follow the same approach for change_request table.
Please mark my answer helpful and accept as a solution if it helped 👍✅
Anvesh
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-23-2023 09:48 PM
Hi @AnveshKumar M,
Thank you for the response! I would love to get the functionalities in a scoped manner so that only the users who have that particular scoped application's role can create incidents and change requests.
Could you please let me know what the best approach would be for that purpose? Is it better re-create the functionalities of incident and change management or somehow extend the existing functionalities by creating tables that inherit incident, change_request, etc?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-24-2023 12:02 AM
@Navaneeth1 I'm not sure of the motive behind this requirement.
But if you want this to be done, I will go with extending the existing existing functionality instead of re creating the entire application.
Anvesh
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-24-2023 12:07 AM
@AnveshKumar M I have a client requirement where they are providing me with a shared instance and other departments are already using the incident and change management on that instance.
The client wants us to develop incident and change management for another department and wants all the information to be accessible only by that particular department. I thought creating a scoped custom application extending the existing functionality would be the best option as I can create custom roles and just assign read access accordingly.
Please let me know if you think there's a better approach to my problem. I'm open to suggestions. Thank you!