Hi,
I have created a new field on incident form, its a normal date/type field called "callback due date", the only thing customized by me with it, is 2x UI Policy: one to make it mandatory field when status is awaiting, the other to prevent date to be in the past; and also a business rule which prevents this date to be in the past on a list view. There are no ACLs on that field.
The problem that i have, is that a non-admin users (service desk mainly) cant select this field on a list view from personalize list slushbucket. Its not there on available list.
So, i have added that field as an admin, on the views they are using, by List Layout. Its there now, for them, in selected list. But, whenever they remove it from selected, its not appearing back on available slushbucket, it disappears again and adding it by themselves is no longer possible. So i have to add it again as admin.
Hence my two question:
1) why this field is not on available slushbucket list for non-admins?
2) why when admin adds it by list layout, for service desk views they are using, and when they remove it from selected, it disappears entirely and is no longer there on available list?
Anyone here have a clue why is that?
KINGSTON version
Picture: Callback due date was added by me to list layout.
Picture 2: as service desk agent. I have removed that field from selected and its not longer even on available list.
Hi Szymon,
Check the Security Rules for the Incident table. Probably there is an add_to_list rule that prevents this field to be visible in the slushbucket for users.
Open any incident, then click the Additional actions menu and go to Configure>Security Rules
Group the list by Operation to see if there are any add_to_list rules.
There are a few options to check:
1. Check if you have any .* or .none overall rules on the Incident table or on the Task table. If yes, then this is the rule that prevents this field to be visible in slushbucket.
2. If point 1 is yes, then either deactivate this rule or create a field-specific rule to mask the overall one. This way you will enable this field to be available in slushbucket. Create this rule without any role so that it will not be filtered out.
Hope this helped.
Best regards,
Łukasz
Hi,
You will find Reset columns to default option in area from the screenshot below. Click it once & that may solve the issue.
Thanks,
Jaspal Singh
Hit Helpful or Correct on the impact of response.
Hi Szymon,
Check the Security Rules for the Incident table. Probably there is an add_to_list rule that prevents this field to be visible in the slushbucket for users.
Open any incident, then click the Additional actions menu and go to Configure>Security Rules
Group the list by Operation to see if there are any add_to_list rules.
There are a few options to check:
1. Check if you have any .* or .none overall rules on the Incident table or on the Task table. If yes, then this is the rule that prevents this field to be visible in slushbucket.
2. If point 1 is yes, then either deactivate this rule or create a field-specific rule to mask the overall one. This way you will enable this field to be available in slushbucket. Create this rule without any role so that it will not be filtered out.
Hope this helped.
Best regards,
Łukasz
