Another disturbing code issue for those of us working with multi-tenancy in 7.6.4 SP1. I was setting up a support company using the 'Support Company Access Configuration' form (as directed by the Multi-Tenancy doc):
I opened the 'Support Company Access Configuration" form. I clicked on 'Create' and set "Bowker" as the company and "ProQuest" as the support company - no problem. I used the search with "Bowker" set as 'Company' to confirm the relationship - successful, entry with Bowker and Proquest, enabled. Here's the problem - I used the 'Update' button as directed to update the people permissions, with the menu set to "Bowker" - The user tool locked and went unresponsive in a minute or so. On Task Manager, the memory displayed a constantly increasing number. After ten minutes or so, I stopped the task. I tried again, with logging running - again the tool locked and memory kept increasing. Again I ended the task. On the log, I found an infinite loop. The code is a set of active links prefixed "CFG:CCS:Update_", linked to the "CFG:SupportCompanyAccessSetup" form. The primary issue is that the code loops to generate a full list of companies that support the chosen company, but the link that is supposed to check (Update_025) only runs when 'z1D_Action' = "Yes". 'z1D_Action' is only set to "Yes" if there is an error found and the user confirms they want to continue in the dialog displayed (Update_020). So, when the links loop to Update_025, it does nothing, the links loop again, ad infinitum. As a workaround, I've updated the error link (Update_020) with an Else action to set 'z1D_Action' to "Yes" if no error is found. This seems to work, as using the 'Update' button now results in the 'Vendor Assignee Groups' field on the company's people entries being set. Looking at the code though, I do find it a bit concerning that the loop is done with Go To actions instead of using an active link guide, that the links proclaim that the "Update completed successfully" when there is no check for this, and that the filter on "SYS:Action" (SYS:ACT:PEOPLESUPPORTUPDATE_105_PPPL) uses an SQL command to modify the People entries. Combined with the original error, the entire section seems sloppy and not to Remedy coding standards. Has anyone else reported this? Is this a known issue? Kelly Logan, Sr. Systems Administrator (Remedy), GMS ProQuest | 789 E. Eisenhower Parkway, P.O. Box 1346 | Ann Arbor MI 48106-1346 USA | 734.997.4777 kelly.lo...@proquest.com<mailto:kelly.lo...@proquest.com> www.proquest.com ProQuest...Start here. 2010 InformationWeek 500 Top Innovator P Please consider the environment before printing this email. This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the sender, and delete the message from your computer. _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are"
