- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-15-2023 09:55 PM
Hi,
In customer environment, project workspace is taking time to load all projects. (around 20-25 seconds)
1. If I make 'Audit' checkbox to true on sys_dictionary for pm_project table, Does it give performance issue on project workspace?
2. what If I do this on field level does that make any difference on project workspace performance?
also when project has 0(zero) project tasks, its not taking much time to load but when project has more than 10 project tasks, its taking time around 20 seconds.
what could be the other reasons of project workspace slowness?
Thanks in advance.
Solved! Go to Solution.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-17-2023 05:59 AM
-
Enabling the 'Audit' checkbox on the sys_dictionary for the pm_project table could potentially impact the performance of the project workspace. Auditing records all changes made to a table, increasing the amount of data stored and processed. This additional overhead might slow down the performance of certain operations, such as retrieving and displaying data on the project workspace.
-
If you enable auditing on a field level, it will still have an impact on performance. However, the impact might be less significant compared to enabling auditing for the entire table, as it will only track changes to specific fields. Nonetheless, it's essential to carefully assess whether the benefits of auditing specific fields outweigh the potential performance impact.
As for the project workspace slowness when dealing with projects that have multiple project tasks, there could be several reasons:
-
Complex or inefficient filters and queries: The project workspace might be using complex filters or queries to fetch and display project information. Examine the filters and queries to ensure they are optimized for performance.
-
Large volume of data: If there's a large volume of data associated with projects and tasks, it could impact the loading time of the project workspace. Consider implementing data archiving strategies or reducing the number of records displayed at a time to improve performance.
-
Client-side scripting or customization: Any client-side scripting or customization in the project workspace can impact its performance. Review any customizations, including client scripts or UI policies, to ensure they are efficient and not causing performance issues.
-
Server performance or resource constraints: The overall performance of the ServiceNow instance, including server resources such as CPU, memory, and network, could be impacting the loading time of the project workspace. Monitor the instance's resource usage and performance to identify any bottlenecks or resource constraints.
-
Browser performance: The client browser's performance can also impact the loading time of the project workspace. Ensure users are using a compatible and up-to-date browser and clear browser cache if necessary.
To address the performance issues, consider the following:
- Optimize filters, queries, and scripts to reduce the amount of data fetched and processed.
- Implement pagination to limit the number of records displayed at a time.
- Review and optimize any client-side scripting or customization.
- Monitor server performance and allocate additional resources if needed.
- Ensure users are using compatible and up-to-date browsers.
---------------
Regards,
Rajesh Singh

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-21-2023 06:37 AM - edited ‎03-21-2023 09:25 AM
Yes, you can write a Script Include for GlideRecords and call it in a Business Rule. This is a common practice in ServiceNow scripting to promote code reusability and maintainability.
Regarding rule execution time, there is generally no significant difference in using a Script Include compared to writing the GlideRecord code directly in the Business Rule. ServiceNow efficiently handles the execution of Script Includes. However, it's essential to optimize your GlideRecord queries and scripts to ensure the best performance.
---------------
Regards,
Rajesh Singh
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-22-2023 11:36 PM
Thank you @Rajesh_Singh for reply.
I will try to optimize GlideRecord queries.