Welcome to Community Week 2025! Join us to learn, connect, and be recognized as we celebrate the spirit of Community and the power of AI. Get the details  

Problem in Form, List Layout, Module and Role relationships

Arthur Sanchez
Giga Guru

I created an application where the user sends a ticket to support and they resolve the ticket. My problem is, I can't establish a definition of how each role will access its given form and list layout

 

I have 2 users: test.user and test.support

When I'm inside the Now Platform I have administrator access and I can see everything in the correct order and with the correct forms, but when I log in with the users I created, they always, ALWAYS go to the default view of the record listing and creation system new records.

 

I need help, if I couldn't solve this I can't go to the works flows, My RELEASE is Washington DC

 

I tried to use this documentation but it didn't help me, I didn't find a part that explained where, how and when the parameters I mentioned are established for each Role

Creating and Configuring Modules | ServiceNow Developer

1.png2.png3.png4.png5.png6.png7.png8.png9.png10.png

2 REPLIES 2

sasi_v
Tera Guru

Hi @Arthur Sanchez  ,

 

Based on the view rule.  users are redirected to their respective views, I don't see any issues here and also as per the screenshots and problem statement, everything seems to be working as expected.
Would you kindly elaborate on this further?

So, I have no explanation, the problem was precisely that no one was redirected to their proper form and list layout, so today I killed the Washington instance and created another one from Utah, but in this one I created 1 form and 1 list layout and 2 modules , 1 for listing and another for creation, I added the view rule only for the user and entered just the user in an anonymous tab in service now, and for some reason it worked, I DON'T KNOW WHY, but it worked, then I added the support user and its modules and list layout and so far it is working.
I don't know why it was giving an error or why it worked with the Utah instance, but it's running so just continue with the application now