Display only form with fields

[Geeky]

I have a requirement to create a form where it will have a user id field and a multi-line text box to populate user details from LDAP.

Initially I though to create a table and add this fields to it but there is no need to add any records in the table. User needs this form for reference purpose only. They enter the data and click on fetch button and multi-line text box will have the values returned.

Can this be achieved in servicenow? Any help would be appreciated.

[Jaspal Singh]

Hi Srini,

You can get an onChange() or onSubmit() client script created accordingly.

Thanks,

Jaspal Singh

Hit Helpful or Correct on the impact of response.

[Chuck Tomasi]

To make the form, you're going to have to create the table and fields anyway. Why the aversion to saving the form data in that table? It seems like a good logging mechanism at least. What is the business case for making this a "customized" solution?

[Geeky]

We are not managing user details in the instance hence there is a need to provide an interface to the support agents where they can enter user id or email and in return get the details from LDAP. There is no need to save the data in that interface, that data which is fetched from the display only form will be used in the ticket work notes or any field as per process set up.

I don't want to save the data on that interface, that is why I am not convinced with creating a table for this purpose.  

[Allen Andreas]

Perhaps I'm not fully understanding the whole thing, but if you have the data coming across, mapped from LDAP (to your sys_user table), and you want your techs to be able to access some of that, I would try to create a check-box on the form (called like Additional User Info), if it's changed to true (checked) (by UI Policy or even client script), the other relevant fields pop-up on that very same form. Containing everything you need.

I'm assuming you need stuff like EMP ID or items along those lines, so you'd design/edit your current form, dot-walking to that information with those fields, leave them hidden, and use a UI policy to then flip those fields on.