Prev
Next
Forums Integration / Customization IPA/ProcessFlow

IE Error when clicking on inbasket

 11 Replies
 0 Subscribed to this topic
 52 Subscribed to this forum
Sort:
Author
Messages
mmanosca
Basic Member
Posts: 8
Basic Member
7/21/2009 4:01 PM
    Has anyone encountered this?  We get an IE error in Portal when clicking on an inbasket link that we use for Process Flow.  It's the generic  "IE has encountered a problem and needs to close" error message.  After the error pops up it kicks you out of the portal and closes your window.  However, it works fine when we log in with the Lawson Admin account.  I happens from time to time then starts working again.  Any idea?

    Thanks,

    Mike
    Michael Thedford
    Advanced Member
    Posts: 19
    Advanced Member
    7/21/2009 4:57 PM
      Do you have custom Display Execs defined in the UserActions? If so, what are they and what do they display when you click on them?
      mmanosca
      Basic Member
      Posts: 8
      Basic Member
      7/21/2009 5:16 PM
        No, we display what is on the action list.

        We have this in the Exec List field -  " "," "," "

        This is the Action List - Approve,Reject,Fix

        Those 3 options display when I click on a workunit,  once I'm in the inbasket.
        David Williams
        Veteran Member
        Posts: 1127
        Veteran Member
        7/21/2009 5:23 PM
          The value in the Display Exec can be either an HTML page to display in the Inbasket window or a Design Studio Portal Page. If you don't put a value there then the only thing that displays is your Work Title and you shouldn't get any errors. You don't have anything in the Pre Exec, do you?
          David Williams
          David Williams
          Veteran Member
          Posts: 1127
          Veteran Member
          7/21/2009 5:31 PM
            I would have the users clear their internet cache and for your admin to run the IOSCacheRefresh in Lawson Portal.
            David Williams
            mmanosca
            Basic Member
            Posts: 8
            Basic Member
            7/21/2009 5:36 PM
              That's correct. The Work Title is what displays. Nothing in the Pre Exec either. Could it be a limitation on the number of workunits allowed in the inbasket? We have 97 workunits in the inbasket now.
              David Williams
              Veteran Member
              Posts: 1127
              Veteran Member
              7/21/2009 5:53 PM
                Are you running the Move WorkUnits to History job to clean up your WORKUNIT table? This job moves the Completed WorkUnits to the historic tables - too many WorkUnits in the active tables can cause problems.
                David Williams
                mmanosca
                Basic Member
                Posts: 8
                Basic Member
                7/21/2009 7:27 PM

                  Tried clearing IOS cache, but no luck.  We are not moving workunits to history, I'll look into getting that going.  There are 4000 records in WFWORKUNIT right now.

                  Gary Davies
                  Veteran Member
                  Posts: 248
                  Veteran Member
                  7/21/2009 7:28 PM
                    That volume would not be a problem at all.   Do you have any tools like Fiddler that you can use to see what is happening.
                    mmanosca
                    Basic Member
                    Posts: 8
                    Basic Member
                    7/21/2009 7:34 PM
                      I have it running now. Do I look at the last web session entry at time of error?
                      Gary Davies
                      Veteran Member
                      Posts: 248
                      Veteran Member
                      7/21/2009 7:48 PM
                        Yes, that should say what was failing
                        mmanosca
                        Basic Member
                        Posts: 8
                        Basic Member
                        7/22/2009 9:23 PM
                          After testing several machines we found that running a windows update fixed the issue. Thanks for all the help!

                          Mike