Menu Selections do not open

[ThunderForest]

Macola 7.5.103d

This problem only happens after adding a new user, using Visual Menu Builder, no matter what PC, and even if copying another users menu rights to the new user. No problem with existing users.

Problem:

IM Inventory Location will open normally (I notice this has the "folder" icon next to this menu item).

Anything under OE-Order View-View, or anything with the "hourglass" icon next to the menu selection, will not open, yet if I log in as another user who had not been added recently, those selections can be accessed.

http://www.thunderforest.bizland.com

 

[dgillz]

I have never heard of this problem before, but have you tried synchronizing security with the two-way arrow icon?

Try this on a user that is currently not working to your satisfaction and let me know the results.

Software Sales, Training, Implementation and Support for Exact Macola, eSynergy, and Crystal Reports

http://www.trianglepartners.com

 

[ThunderForest]

No, that didn't seem to do anything..but here's something interesting...

If I try to do anything in OE first, nothing opens in OE. But when I go to IM and open Inventory/Location (or anything there), then go back to OE, all the selections in OE will open.

http://www.thunderforest.bizland.com

 

[dgillz]

Thats way too wierd. I would work with your Macola reseller on this one.

Software Sales, Training, Implementation and Support for Exact Macola, eSynergy, and Crystal Reports

http://www.trianglepartners.com

 

[MacolaHelp]

Did you migrate to SQL when you were on 103.d? If so, there might be something "broken" in the code. Current rev most of clients are on is 7.6.100a, though I understand that 7.6.200 seems like we can install as they have fixed most of the problems. How big a task is it to get you more current on the code?

 

[kbieber]

Doesn't this sound like a security issue? Is it possible that a security level required by OE is obtained when the IM screens are opened? Does OE still work after the IM screens are closed again?

 

[MacolaHelp]

If you create a brand new user & set up new security yourself rather than copy from an existing user, do you have the same problem? If so, maybe you have some stray or corrupted records in the screens DB. Did you ever clarify if you were pervasive or SQL? The users can't be setup in Enterprise Manager before Macola. Macola does some sort of encryption thing that fights w/EM if you try to do it the other way.

If you open the screens or PWE DBs, you might find users who no longer exist. Even if you delete them from Macola, they stay in the PWE files for sure & maybe don't completely leave the screens DB. As far as I know, this is still a problem through 7.6.100a.

A corrupted screens DB could cause the permissions to be mixed up in other apps.

Did you try removing the view from an affected user & saving their user, then adding back the view menu tree structure from one that works? Highlight processes & make sure add to level above is selected & then drag & drop the good users menu from the customize menu screen to the user who is broken.

Do you use Best of OE from Peak? If so, they do make changes to the view menus. Maybe your screens options didn't complete update during your last update?

 

[ThunderForest]

We use Pervasive. Did try copying from an existing user that worked, as well as adding a new user, and either still did not work. Interesting that you mentioned if we use Best of OE. We don't, but do use IPS-SAS. We upgraded last January, and I do know the DDFs were updated as well as various OE screens. This is the first time I've added a user since that upgrade.

http://www.thunderforest.bizland.com

 

[stravis]

That is probably your problem. Macola has two tables that define your menu structure. The first table defines the underlying menu structure as you see it in Visual Menu Builder when you use the customize menu feature. The other is a listing of menu indexes that the user should be blocked from accessing. This block list is defined through the detail feature in Visual Menu Builder.

Now the reason that this could in fact be your problem, is that if you make a change to the menu structure in any way then you must change the menu tree indexes for all sub-nodes on the tree. This can be very complex. In addition, you must make sure that the second table, which defines menu security access, has its values changed to reflect the new menu heirarchy. Also, very complex to handle programmatically.

IPS-SAS install several new menu items and more than likely screwed this up. I myself have made this mistake before and introduced a real head scratcher in to a system and I saw the same results. I would suggest contacting IPS-SAS either directly (if you are able) or through your Macola Reseller to discuss this problem.

If experience serves me, you will probably have to nuke your menu security and rebuild. You can keep the menu structure, but attempting to fix this by hand may be more than our little minds can fathom.

As a second option I would offer to fix this problem for you for free by doing an export of these two files and sending them to me. I'm willing to do this for free, so that I could get an example of a real world broken menu structure. I would like to maybe add a utility for rebuilding broken menus for a set of Macola admin tools that I am building. If you are insterested please email me at scott@ nexosystems.com (please remove the space).