Security (ACLs) for Archived Tables - assistance needed

[Rob Sestito]

Hey SN Comm Team,

I am running into an issue/security restraint with archiving tables.

I have created Archiving Rules for each COE/Table we have. Now that I have rules in place, I see all the Archive HR Table Applications through my filter navigator:

The Highlighted tables however are giving me a security message:

Doing some research, I landed here: Data archiving - specifically, the information regarding Archive tables and ACLs.

Our system did not have the system property 'glide.security.enable_archive_table_acls' - I have created this.

I am able to get to where the archived tables are to attempt to create ACL(s) to give me access. However, they do not show up for selection when on the ACL form.

Anyone know about this security restraint and how I can fix?

Cheers,

-Rob

[Allen Andreas]

Hi,

I'm unsure what you mean in your last part as your screenshot shows the archived tables there for selection?

But you're saying they're not?

Please mark reply as Helpful/Correct, if applicable. Thanks!

[Rob Sestito]

Hey Allen,

It is not showing the tables I highlighted in the first screenshot for selection for me to create any ACLs.

As the highlighted tables from the first screenshot are the ones giving me the Security Access message.

While the last screenshot does show archive hr tables that I can create ACLs for, the ones giving me access issues are not.

[Allen Andreas]

Hi,

You'd need to ensure you're in the right scope and also double check the name of the actual table.

I believe these won't show if they're associated to a specific scope unless you also check the can configure box on the table, but unsure if archive has this as well.

Please mark reply as Helpful/Correct, if applicable. Thanks!

[Rob Sestito]

Hey Allen,

Yes I am in the correct scope. I also went to a couple of the archive tables and was able to make Allow Configuration active. However, that did not change anything for me.

Edit: Even when I go to a table like ar_sn_hr_core_case_workforce_admin that I have access to, that application access does not have Allow Configuration set to active. So, I feel that this might not be the issue: