Re: Workflow - Mid-tier vs Client
Hi, You need to delete the .arf files and .arv files from the AR System Home directory which will delete the cache for the user and mid-tier. You also need to check for the permissions for the columns and the workflows for the user for which you need to hide the columns on the user tool or the mid-tier. Hope, this wil help you to resolve your problem. Thanks, Sonal -- [EMAIL PROTECTED] www.vyomlabs.com Consulting | Oursourcing | Training || BMC Remedy BSM | ITIL | IT Governance Axton wrote: If you are using the advanced features of workflow on the mid-tier, I know they warned that it would not always work properly. If not, check the permissions on the columns you are trying to unhide and make sure that your users have permissions to view the columns. Axton Grams On 4/26/07, Eli Schilling [EMAIL PROTECTED] wrote: ** Hello listers! Recently I built some add-on workflow (Remedy 6.3) for the support console to allow people to show or hide certain columns. For the first several days it worked great; each person gets a single record in a seperate preference form; these preferences load when they open the support console. I have validated permissions on active links, fields, etc; I even have log files SHOWING that the active link fired to make a particular field visible. However, the fields are no longer becoming visible. This is the behavior in the client application. I had a user open the mid-tier and launch the support console and the selected columns DO appear. So it worked for a few days...then stopped working on the user tool...but a user can launch mid-tier and their preferences load just fine. I get this: ACTL - Passed qualification -- perform if actions ACTL 0: Set Characteristics ACTL For field -- Case Type (536880915) ACTL Change field to visible Yet the field does not appear Any thoughts? This is the strangest thing. P.S. as admin, it has not stopped working for me...yet... Thanks! Eli __20060125___This posting was submitted with HTML in it___ ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:Where the Answers Are ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:Where the Answers Are
Workflow - Mid-tier vs Client
Hello listers! Recently I built some add-on workflow (Remedy 6.3) for the support console to allow people to show or hide certain columns. For the first several days it worked great; each person gets a single record in a seperate preference form; these preferences load when they open the support console. I have validated permissions on active links, fields, etc; I even have log files SHOWING that the active link fired to make a particular field visible. However, the fields are no longer becoming visible. This is the behavior in the client application. I had a user open the mid-tier and launch the support console and the selected columns DO appear. So it worked for a few days...then stopped working on the user tool...but a user can launch mid-tier and their preferences load just fine. I get this: ACTL - Passed qualification -- perform if actions ACTL 0: Set Characteristics ACTL For field -- Case Type (536880915) ACTL Change field to visible Yet the field does not appear Any thoughts? This is the strangest thing. P.S. as admin, it has not stopped working for me...yet... Thanks! Eli ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:Where the Answers Are
Re: Workflow - Mid-tier vs Client
Did you verify that there isn't some workflow after this point that re-hides the field? From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Eli Schilling Sent: Thursday, April 26, 2007 10:34 AM To: arslist@ARSLIST.ORG Subject: Workflow - Mid-tier vs Client ** Hello listers! Recently I built some add-on workflow (Remedy 6.3) for the support console to allow people to show or hide certain columns. For the first several days it worked great; each person gets a single record in a seperate preference form; these preferences load when they open the support console. I have validated permissions on active links, fields, etc; I even have log files SHOWING that the active link fired to make a particular field visible. However, the fields are no longer becoming visible. This is the behavior in the client application. I had a user open the mid-tier and launch the support console and the selected columns DO appear. So it worked for a few days...then stopped working on the user tool...but a user can launch mid-tier and their preferences load just fine. I get this: ACTL - Passed qualification -- perform if actions ACTL 0: Set Characteristics ACTL For field -- Case Type (536880915) ACTL Change field to visible Yet the field does not appear Any thoughts? This is the strangest thing. P.S. as admin, it has not stopped working for me...yet... Thanks! Eli __20060125___This posting was submitted with HTML in it___ ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:Where the Answers Are
Re: Workflow - Mid-tier vs Client
Hi Eli, I had something like this happen to me just the other day. What I finally did to make it work, was to go in and delete the .arf and .arv files. After I did this, it started working. Hope this helps! Greg Donalson Entaq, Inc. _ From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Eli Schilling Sent: Thursday, April 26, 2007 12:34 PM To: arslist@ARSLIST.ORG Subject: Workflow - Mid-tier vs Client Hello listers! Recently I built some add-on workflow (Remedy 6.3) for the support console to allow people to show or hide certain columns. For the first several days it worked great; each person gets a single record in a seperate preference form; these preferences load when they open the support console. I have validated permissions on active links, fields, etc; I even have log files SHOWING that the active link fired to make a particular field visible. However, the fields are no longer becoming visible. This is the behavior in the client application. I had a user open the mid-tier and launch the support console and the selected columns DO appear. So it worked for a few days...then stopped working on the user tool...but a user can launch mid-tier and their preferences load just fine. I get this: ACTL - Passed qualification -- perform if actions ACTL 0: Set Characteristics ACTL For field -- Case Type (536880915) ACTL Change field to visible Yet the field does not appear Any thoughts? This is the strangest thing. P.S. as admin, it has not stopped working for me...yet... Thanks! Eli __20060125___This posting was submitted with HTML in it___ ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:Where the Answers Are
Re: Workflow - Mid-tier vs Client
If you are using the advanced features of workflow on the mid-tier, I know they warned that it would not always work properly. If not, check the permissions on the columns you are trying to unhide and make sure that your users have permissions to view the columns. Axton Grams On 4/26/07, Eli Schilling [EMAIL PROTECTED] wrote: ** Hello listers! Recently I built some add-on workflow (Remedy 6.3) for the support console to allow people to show or hide certain columns. For the first several days it worked great; each person gets a single record in a seperate preference form; these preferences load when they open the support console. I have validated permissions on active links, fields, etc; I even have log files SHOWING that the active link fired to make a particular field visible. However, the fields are no longer becoming visible. This is the behavior in the client application. I had a user open the mid-tier and launch the support console and the selected columns DO appear. So it worked for a few days...then stopped working on the user tool...but a user can launch mid-tier and their preferences load just fine. I get this: ACTL - Passed qualification -- perform if actions ACTL 0: Set Characteristics ACTL For field -- Case Type (536880915) ACTL Change field to visible Yet the field does not appear Any thoughts? This is the strangest thing. P.S. as admin, it has not stopped working for me...yet... Thanks! Eli __20060125___This posting was submitted with HTML in it___ ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:Where the Answers Are
