2018.1 Forms and Views

Question

Short Version:
Issue: Found that the form\view config under /AdaxesConfig does not match what is seen on the user modify page

Long version:
We upgraded from 2017.1 to 2018.1. Everything looked good, but my Help Desk reported that they are unable to browse our other domains when adding a user to a group. Steps would be that they would open the user object and scroll down to the group management, click add, and find the group to add the user to. They only see the domain that the user object is in and not able to drop down the domain selection to select another domain to search in.
I found that this issue happens to me as well when I am in the /HelpDesk page, but it does work in the /Admin page. I figured it was something to do with the user form, so I went into /AdaxesConfig and went to check the user form in Modify. Found that in /AdaxesConfig, it doesn't show the group membership section for the modify form for the user. Started to match up the fields with the page being shown and they don't match.

For instance:
/adaxesconfig#/EditConfiguration/HelpDesk

Management
-Forms and Views
--User
---Modify tab

Sections: General
Fields:
Account Type
First Name
Last Name
Legal First Name
Legal Last Name
Initials
Display Name
Email
Email Alias
Description
Office

Now if I log into the /HelpDesk page and Edit a user, I see the following fields in this order in the General section
Account Type
First Name
Last Name
Legal First Name
Legal Last Name
Initials
Display Name
Description <<-------
Employee ID <<--- This is not listed as a field in the general section in the config. Suppose to be in Other section
Employee Number <<--This is not even a field that we have being available in the Modify config for a user
Office
Email
Email Alias
Web Page
Notes

I did see that the Fields above that are showing when editing a user are configured for the View Form for User in the /HelpDesk page

Comments

Hello,

For troubleshooting purposes, could you send us (support[at]adaxes.com) a backup of your configuration? For details on how to make a backup, have a look at the following help article: https://www.adaxes.com/help/?HowDoI.Man ... ation.html.

Answer 1

Hello,

As we understand, you are using the Modify User action. The action is configured to use the default form which means that sections and corresponding properties of the Modify User form will be used by the action. In your configuration, the Modify User form does not contain the Employee ID and Employee Number properties. As a result, the properties are not displayed in the action form when modifying a user. Exactly as it should be.

Most probably, you did not refresh the Web Interface after updating the Modify User form. Or the fields were added to the General section of the form after migrating the Web Interface configuration. If you are not sure, provide us with a backup of your current Adaxes 2018.1 configuration.

Comments

Hello, I have a fresh installation of adaxes 2018.1 and have the same issue, trying to hide password option in user creation and this come up again.

Logged off twice from Config page and user page.

System is not yet in production, just started the config.

Mike

---

Hello,

After updating settings of a Web Interface, there is no need to sign out/in to Adaxes Web interface Configurator. All you need to do is save the changes in the configurator and then press Ctrl+F5 on the page of the corresponding Web Interface. Most probably, the changes were not saved in the configurator or were done for a Web Interface different from the one you are checking.

For details on updating forms and views in Adaxes Web Interface, see https://www.adaxes.com/tutorials_WebInt ... diting.htm.

---

The Modify form does not contain the EmployeeID and Employee Number under the General section in /AdaxesConfig, but when modifying a user in /HelpDesk, it did show up. It should not have. It was an incorrect showing f the form and was not what was shown in the configuration.

I did resolve this though. It did not make sense that the adaxesconfig was showing the correct setup and that the /HelpDesk page was not. I simply moved one field up and then down in the section. This prompted a save. After saving, the form now shows correctly. In detail, in the General section I have the Email field below Display Name. I moved Email up above Display Name and then I moved it back below DisplayName in /AdaxesConfig for the /HelpDesk page. The save check showed up and I clicked on it to save the change.

After upgrading, I had only changed the Common Sign in page in /AdaxesConfig and not any of the other pages. I provided the backup files during the install and did not execute the web UI migration exe. Maybe it correctly imported the configs, but did not correctly publish them at the time of the upgrade?

---

Hello,

As we confirmed in our previous post, the Web Interface configuration is exactly as you specified. However, we did not see the Employee ID and Employee Number properties in the form on the Web Interface. Most probably, the properties were displayed in the form because the page was not refreshed. When you make changes to a Web Interface configuration, you need to press Ctrl+F5 on the Web Interface (not the configurator) page to see the changes.

---

If you can help with one other thing. When going to a user object in the /HelpDesk page and attempting to add to a group, the option to select the domain to search for the group is greyed out. This is not the case on the /Admin page. In 2017,1, you could drop down to select the domain to search. I can't seem to find where this may be restricted in the /AdaxesConfig for the /HelpDesk. Where would the restriction to prevent searching domains other than the one the user is in when looking to add to a group be?

Oddly, if I go to a group and search for the user to add to the group, the drop down to select the domain is available.

---

Hello,

The option is greyed out because you have the Browse Dialog disabled for the Help Desk Web Interface. The dialog is enabled for the Administrator Web Interface and thus the option is available. For information on how to enable the Browse Dialog, have a look at the following tutorial: https://www.adaxes.com/tutorials_WebInt ... owsedialog.