"State" field in custom table extended from task is read-only for custom-role end-users

[G Balaji]

Hi,

I have a custom table A  extended from OOB task table and access control specfic to custom role R. OOB state field in the custom table A is read-only for this custom role users. And when I checked the ACL, there was no write access defined on task table.  If I added ACL to task table with read access what would be the impact on other tables. 

How do I resolve this? 

Thanks.

[Allen Andreas]

You should need to add a write ACL for your custom table for the state field if you are wanting them to be able to write there (with your custom role in the role condition).

If you add your custom role as read to task...you're going to get in to license issues I would believe as now you're going beyond a runtime license (which is a cheaper license for just your custom table/role) and trying to allow them to see everything involved with task...which is a core table and could cost the fulfiller/ITIL license amount.

What exactly are you trying to do? You want your custom role to be able to change the state value? Then add a write ACL on your custom table for the state field.

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

[snowarchitech1]

Hi

I have a requirement, We are developing custom scoped application.  For that we have created Custom Table extended from Task.  We need to add the functionality of State and Status workflow.  User can keep it draft/new/open/reopen etc.,  multiple changes with corresponding workflow/notification .  Please advice what are the best practices for the custom application development and how to handle the state/status

[Allen Andreas]

Hi,

If you don't mind, please create your own question on the forums. Feel free to mention me @Allen Andreas and I'll get notified.

This allows your post to get it's own conversation and won't involve this thread that was answered and closed more than 3 years ago.

Please mark reply as Helpful, if applicable. Thanks!