An incident that originated in Marh 2023, does not show all the history
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-01-2025 01:20 AM
An incident that originated in Marh 2023, does not show all the history. An incident was created in 2023. When I check in History, it shows as created in 2023 but under activities, it is captured from 2024. How to have the activities to be displayed from 2023.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-01-2025 01:27 AM
Hi @Raahul2
Are you abe to locate all the historical journal entries for that particular incident in the data base.
If not, just check that in the sys_journal_field table.
If it there in the database, then go to the below system property and update the value.
System properties: glide.history.max_entries
Maximum number of entries retrieved for display in an activity stream. The default number is 250. New entries do not count towards the max number until the form is refreshed.
Regards,
Siva
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-01-2025 01:38 AM
Hi Shiva,
Thank you for the quick response. Much appreciate it. I can find the entries in the database. Please suggest if I have to increase the default number from 250 to more for having these entries displayed in the incident activity section.
Best regards,
RB
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-01-2025 01:44 AM
Hi Shiva,
We have recently cloned our prod to one of our lower envs. I have checked with the same INC in the lower env. In that env , I see that the activity section has activities captured from 2023, from the day INC was created. But somehow thats not the case in Prod. In both the envs the system property has same 250 as value.
Regards,
RB
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-01-2025 01:55 AM
Hi @Raahul2
While cloning, we typically don't import attachments, email logs, etc., from production to lower environments, depending on the configuration. In production, if a particular incident has more attachments and email logs, those items won't be moved to lower environments. Consequently, the entry count will be lower compared to production. This is why it might not be showing up in production but is visible in non-production.
Just increase the count by 10-15 (anyways you can revert) and check if it's showing more entry.
Regards,
Siva
