Mig to 4.0.11 - process acl's quit working

[kruegerM]

We are migrating from 3.3.11 to 4.0.11
We have one process, all activity dialogues have a pull-down list whose values are controlled using ACLs.
Everything work great in 3.3.11.

The ACLs for the process are not working in the migrated system.
My ACLs that control Services per Queue are working great.
I've looked for errors during the migration, or in system log or httpd log - not finding anything.
I verified the Activity Dialog Entity IDs in the process match what's called out in the ACLs

I have run this scenario three times now, same results each time. I take a clone of our production system and migrate it to 4.0.11 from rpm.

Any suggestions appreciated. With 5 coming out, I feel myself slipping further behind.

M

[crythias]

Process Activity Dialogs (et al) now have GUIDs as EntityIDs so you'll need to check your ACL's and adjust accordingly.

[kruegerM]

Maybe I used the wrong nomenclature?
An example ID:
ActivityDialog-0a441a84398f230fc7b21970c0df0f4a

[crythias]

I can't know what wrong means without an example. But the docs do indicate how to provide ACLs for v4.

[kruegerM]

reading manuals

there are 16 possible choices, activity dialogues should be showing 2 or 3 - they are showing all 15
here is an ACL example:

[kruegerM]

From what I read on page 202 of the Admin Manual for 4 - my acls are correct.

# the current Activity of the ticket
ActivityDialogEntityID => ['ActivityDialog-aff0ae05fe6803f38de8fff6cf33b7ce'],

[kruegerM]

This was an interesting hunt.
The fix: Remove the Process item within PropertiesDatabase

Where the ACL was:


It is changed to:


With that removed, my ACLs are now working within the process.

Found thanks to crythias -- I compared the Admin manual against my ACL.pm file.