View Rules not applied when opening a new record

[CharlesR1]

Hello,

We are having a few issues with View Rules when creating new records.

We have the following three Views for for our Release application: 'release', 'simple_release' and 'release_event'.

The views are determined by view rules, driven by a choice field 'Release Type'. This has three choices: Release, Simple Release, and Release Event.

The view rules work fine when opening current records.

However, the problem occurs when we open a new record. We have three modules, New Release, New Simple Release and New Release Event. before the new records save, the view shown is always 'release_event',

This is despite the view rules being in place and the views being called in the module arguments, as below:

New Release module: rm_release.do?sys_id=-1&sysparm_query=u_release_phase=In Progress^u_simple_release=Release&sysparm_view=release

New Simple Release module: rm_release.do?sys_id=-1&sysparm_query=u_release_phase=In Progress^u_simple_release=Simple&sysparm_view=simple_release

New Release Event module: rm_release.do?sys_id=-1&sysparm_query=u_release_phase=In Progress^u_simple_release=Event&sysparm_view=release_event

Does anyone know how we can see the correct view of the new records before they are saved?

Thanks,

Charles

[Kalaiarasan Pus · Accepted solution]

Fine print from Wiki link

"For example, if a user selects the Mobile view on an Incident record and then tries to open the following link, which specifies the visual task board view, the form still opens in the Mobile view: https://{instance}/nav_to.do?uri=incident.do?sys_id={sys_ID}sysparm_view=vtb.

The sysparm_view parameter specifies the view to be used for a list or a form, and can be overwritten by a user's stored preference for a view. You can override this behavior by setting the sysparm_view_forced parameter to true."

http://wiki.servicenow.com/index.php?title=View_Management#Switching_Views

[tamarasylte]

Have you had any experience trying to open a GlideDialogForm window with one view, while the base record has a View Rule to enforce a different view?

I tried adding the "sysparm_view_forced" parameter to the GDF but I still get the original view of the base form (not the one specified for the new GDF).

Any ideas?

[Kalaiarasan Pus]

Is the question answered? If so can you close this?

[johnnyjava]

one thing to note, if the users lack the view_changer role, they cannot actually see the View name. Watch for the Field changes to know if this is working.