Not able to create Archive Rules.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-16-2022 12:05 AM
Not able to select the Table Name (Both OOB and Custom tables) while creating Archive Rules. Few tables are showing Greyed out and not able to select those. Do we need to enable some functionality in Table to allow creating Archive rules.
- Labels:
-
Customer Service Management
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-07-2022 02:16 PM
Hi @Karthika K1
Are you ADMIN in your instance?
If I helped you with your case, please click the Thumb Icon and mark as Correct.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-10-2022 06:43 AM
I'm facing the same issue, and I'm admin in the instance.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-10-2022 07:04 AM
As far as I know, it would only be grayed out if there is an archive rule in that table already.
The screen below is an out of the box developer instance. While trying to create a new archive rule for "incident", it shows incident as grayed because there is an out of the box archive rule for it and cannot have two archive rules on the same table. It still allows me to select incident_task for example.
Check ALL archive rules by removing the filter
If I helped you with your case, please click the Thumb Icon and mark as Correct.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-10-2022 09:06 AM
It will only block if it has for the same table? Or it applies for child/parent tables as well?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-10-2022 09:25 AM
What do you refer when you say parent/child tables? That one EXTENDS from the other?
Like incident extends from the task table?
Or you are thinking about incident_task being a child (which is wrong) of the incident table?
I am trying to understand so I can help you better.
For example, I can create an archive rule on the TASK table. I guess it is because there would be overlap if I do that since incident, problem, change_request, etc. extend from it.
If I helped you with your case, please click the Thumb Icon and mark as Correct.
