Michael, From your description, you have a permission issue not a personal removal issue.
You state that only that one support team would ever use the fields so there is no reason for any other support team to see those fields. Whatever solution you choose should focus on having column fields that just that team can access in a controlled way. If you try and update people's table preference, what happens when a new person arrives? What happens if one of the people who are not supposed to see this column resets their preference and the three fields suddenly appear. It may not be an issue, or it may be. That is up for you to decide. If you want things controlled on an INDIVIDUAL level and there is no security, the best strategy is to add the fields and then let individuals remove them if they don't want to see them. If you are indeed controlling on the support team level, is there a group that all members of this support team are members of? If so, terrific. If not, you can create a computed group that includes this team list (so you don't have to update each person's group list individually and so you can manage group membership at the definition of the computed group level. Then, you can either add the fields and just give permission to the computed group (or the group they are all already a member of if there was one just for them already) OR you create an active link that makes the fields visible that has permission to only this computed group (of the existing group). NOTE: You always want to have fields Hidden and make them visible by workflow rather than visible and make them hidden by workflow. This is more efficient and it avoids any possibility of fields showing and then disappearing on the screen (and causing screen flicker). This is a general best practice for any fields that are not always visible – start hidden and make them visible vs. start visible and make them hidden. Of course, any changes to definitions would be made in the overlay layer so that they are retained across upgrades without issue. I hope this helps, Doug Mueller From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Jason Sent: Tuesday, November 27, 2012 9:44 AM To: [email protected] Subject: Re: Adding "removed" columns to a table ** You could limit the permissions of the 3 columns to a group that only that 1 support group is a member of. If you want to use the support group, you'll need to find it in the Group form and change the type to "Change", then it'll be available in Dev Studio. Then the only people that would see it are admins and members of that group. Jason ________________________________ From: "Nau, Michael" <[email protected]> To: [email protected] Sent: Tuesday, November 27, 2012 10:12 AM Subject: Re: Adding "removed" columns to a table ** Mark, thank you for your suggestion. I had thought of that, I just wanted to know if there was a clever way to do this without adding any new objects. I could, of course, modify all entries on the preference form… ;-) Regards Michael From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Walters, Mark Sent: Tuesday, November 27, 2012 4:04 PM To: [email protected] Subject: Re: Adding "removed" columns to a table ** The settings that control whether a field is present in a table are stored in ar.ini file for the User Tool. For midtier users they will have to be using a preference server to set/save those options. It’s not going to be easy to manage this directly so how about setting the column to HIDDEN in the field properties of the form and then using an active link, running for members of the group you’re interested in on form open, to change the visibility of the field to VISIBLE? Mark From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Nau, Michael Sent: 27 November 2012 14:35 To: [email protected]<mailto:[email protected]> Subject: Adding "removed" columns to a table ** Hi guys, one of our support teams has requested that 3 additional columns should be added to the main table on the IM Console. These columns will only be used by the requesting team, so I don’t want anyone to see them after I add them to the table. I’m looking for a way to add these columns in a “removed” state, by which I mean the state that a column is in after a user removes it via the table preferences. The result would be that I can add the columns and then tell the requesting team that they can make the columns visible via the preferences. Does anybody know how to achieve this? AR 7.0.01 Solaris 5.10 Midtier 7.5.00 RHEL Mit freundlichen Grüßen, Michael Nau IT Infrastructure & Customer Services ING-DiBa AG Theodor-Heuss-Allee 100 60486 Frankfurt am Main Telefon 069 / 27 222 66596 [email protected]<mailto:[email protected]> www.ing-diba.de<http://www.ing-diba.de/> ING-DiBa AG, Frankfurt am Main. Registernummer HRB 7727, Handelsregister Amtsgericht Frankfurt am Main. Vorstand: Roland Boekhout (Vorsitzender), Herbert Willius (stellv. Vorsitzender), Bas Brouwers, Bernd Geilen, Katharina Herrmann, Martin Krebs. Aufsichtsrat: Ben Tellings (Vorsitzender) Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich erhalten haben, informieren Sie bitte sofort den Absender und vernichten Sie diese Mail. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail ist nicht gestattet. This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden. _attend WWRUG12 www.wwrug.com<http://www.wwrug.com/> ARSlist: "Where the Answers Are"_ _attend WWRUG12 www.wwrug.com<http://www.wwrug.com/> ARSlist: "Where the Answers Are"_ ING-DiBa AG, Frankfurt am Main. Registernummer HRB 7727, Handelsregister Amtsgericht Frankfurt am Main. Vorstand: Roland Boekhout (Vorsitzender), Herbert Willius (stellv. Vorsitzender), Bas Brouwers, Bernd Geilen, Katharina Herrmann, Martin Krebs. Aufsichtsrat: Ben Tellings (Vorsitzender) Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich erhalten haben, informieren Sie bitte sofort den Absender und vernichten Sie diese Mail. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail ist nicht gestattet. This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden. _attend WWRUG12 www.wwrug.com ARSlist: "Where the Answers Are"_ _attend WWRUG12 www.wwrug.com ARSlist: "Where the Answers Are"_ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are"
