Is there a special ACL for Work Notes and Additional Comments?

[mark141230]

Hi Everyone,

I created a new application and was extend to task table.

I created a table with the generic ACL.

I noticed that after granting a read-only role to a use. The Work notes and Additional Comments didn't show while others are okay.

is there a special ACL for those to fields?

Many thanks

[cdaller]

Hello Brian,

thanks for comming back.

I have a scoped application in Istanbul.

The role has write access to the record (e.g. myTable),

as well as to myTable.comments and myTable.work_notes.

Comments is showing, worknotes is not, even with same setup.

Hence I wondered if there is something special.

Christian

[Brian Dailey1]

Hi Christian,

There may be another ACL providing the access to Comments, perhaps the one that is role-based just like your work_notes ACL is not working (i.e., they may both not be working) ?

It's just a guess because the Additional Comments field is made visible to the end user as well based on them being the task's originator, is it possible this is how you're seeing the comments and the role-based ACL is actually failing?   It would be better if you could post the details/screenshots of your ACLs in question... you might also want to screenshot the list of ACLs that are applying, just for reference.

Thanks,

-Brian

[jasonkist]

Has anyone been able to figure this out? I'm in the same situation, our problem management team want the records read-only to users not in the assignment group but would like all itil users the ability to add updates to the journal. I've been making role based changes to the system and have had success, but this work notes field has been trouble. I have followed all recommendations above.

[Brian Dailey1]

Hi Jason,

In your case, I do not think you can make the record read-only for itil users if you want them to be able to write to the one field.   You would need to manage the read-only security with the field level ACLs instead, and still give them write access to the record.

1. Give itil a record-level write ACL.

2. Create a field-level ACL for (table name).*, include the itil role, and add a script to return true only if the current user is a member of the Assignment Group.

3. Create a field-level write ACL for (table name).(journal field name) that includes the itil role.

You might have to add some other ACLs depending on your requirements, but that should cover the basics of the scenario you had laid out.

Let us know if you have questions.

Thanks,

-Brian

[jasonkist]

I have tried as you suggested but something is still blocking the work notes field for an itil user to add to the activities. I have 4 ACL's in place on my brand new personal environment:

1. Problem with write operation, itil role, and condition assignment group is dynamic one of my groups
2. Problem.* with write operation, itil role, and condition assignment group is dynamic one of my groups
3. Problem.comments and work notes with write operation, and itil role
4. Problem.work notes with write operation and itil role

While impersonating an itil user, when accessing a record that is assigned to another user in another assignment group, the work notes field is not there. We are now on the Kingston release. I have reviewed other client scripts, UI Policies, UI Actions, and business rules but not seeing what else might be affecting. Your assistence is greatly appreciated.