Row-level security can be applied a number of ways. Assignee Group (Field 112) is common and easy. Add it to your form and populate it with the group(s) that you want to grant whatever access to. You'll obviously want to implement workflow to manage it - set it for new records, reset it on behalf of changes, whatever. Field ID 1 (Request ID) controls record access itself. Set Assignee Group View or Change to it. The target group will have the intended access on a per-row-basis.
Dynamic groups are another way. They provide much more granular control. Create groups with ids 60000 and higher. In your form, you add fields with the same ids. In your field permissions, such as Field ID 1, you assign the intended permission to whichever group name you used to provide the permission. This supports both groups and users (delimited with single quote). Also supports multiple fields/groups (many of them could introduce a performance issue based on total number of groups, number of fields in a form, etc.). Best to read-up on them in Remedy documentation. Mike White EMail michael.wh...@verizon.com Office 813.978.2192 -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Vikram Sent: Friday, August 26, 2011 10:49 AM To: arslist@ARSLIST.ORG Subject: Re: Row Level Security What if we dont have any ITSM solution implemented and have home grown system for Customer support and ticketing? in that case we wont have any company created and hence no group for that company.. _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are" _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are"
