Consultor Eletrônico

Status: Unverified

FACT(s) (Environment):

Dynamics 2.1A

SYMPTOM(s):

Security changes in Security Allocation/actions is ignored for menu items until AppServer is restarted

Thin client session

CAUSE:

Known issue with thin client, development aware.

To make a restricted sub-menu/menu-item, we can either use Security Allocation/Menu items ,or Security Allocation/actions with an action defined for the wanted menu-item(s). Note this last option offers to define the security of multiple menu items at once if they share the same action.

Now, with thin clients, this last option requires the AppServer to be restarted to make changes in Security Allocation/actions be taken into account. In other words, for menu items, security actions are cached on the AppServer.

Note that another type of action like 'add' (add button in toolbar) does not suffer from this problem. (re-logon is enough to make the changes be taken into account)

FIX:

Start new AppServer agents (with progress explorer) then trim them to restart the agents one by one. (a way to restart the AppServer without restarting it). With this trick, re-logon is not enough, but restarting the client session makes the new security be taken into account.

or

Use Security Allocation/Menu Items instead of Security Allocation/Actions. But you cannot define the Security for multiple items at once.