Strategic Planning Workspace New Modal Box

[juliebailey]

In Strategic Planning Workspace, from the Backlog when a new Planning Item is created (e.g., Epic, Feature, Story) from the button in the upper right corner it will display a modal box as pictured below.  We found documentation on how to use the out of the box view for "EAP New" to customize the modal box (the documentation is linked below).  We are hesitant to make the change this way, because it will affect everyone who uses EAP in our organization.  We would like to do something that will allow different teams to have certain fields available on the modal box based on their individual need.  Maybe a custom view that is linked to the modal box or some configuration that is done in UI Builder.  We would appreciate any advice that you may have.  Thank you.

Modal Box and New Feature button in upper right corner:

Link to documentation for create or update form views for EAP work items: 

https://www.servicenow.com/docs/r/zurich/it-business-management/enterprise-agile-planning/create-or-...

[alexankaras · Accepted solution]

You could make this work with UI policies as they work even on the modal. By using conditions in the UI Policy like "Team = Plant Portfolio Solution Train" or similar you can show/hide or make mandatory fields as expected based on the team that you're creating a feature, epic, capability, story etc.

[alexankaras · Accepted solution]

The tables are under the "Portfolio Planning Core" application scope. UI policies need to be created within the same scope of the respective tables.

[alexankaras · Accepted solution]

Hi Julie. UI Policies run on the client-side. The logic there would be that you had all the fields in the form layout already that the different teams would use so they're fetched to a user but then the UI policy could hide specific fields for specific teams.

[alexankaras · Accepted solution]

The tables are under the "Portfolio Planning Core" application scope. UI policies need to be created within the same scope of the respective tables.

[juliebailey]

Thank you, Alex.  That is working perfectly to remove fields.  It doesn't seem to allow me to add fields.  Is there a trick to getting that to work?  I tried marking the fields visible = true in the UI Policy Actions and also tried adding a script with g_form.setDisplay('field_name', true); but it doesn't change the model box form for me.

[alexankaras · Accepted solution]

Hi Julie. UI Policies run on the client-side. The logic there would be that you had all the fields in the form layout already that the different teams would use so they're fetched to a user but then the UI policy could hide specific fields for specific teams.

[juliebailey · Accepted solution]

Excellent!  We have confirmed that works for us.  Thank you for all your help, Alex. 

Here is a summary of the steps that we took to make this change:

1. Create a backup of the out of the box view (EAP New), which can be done from the Form Design tool.

2. Add all the potential desired fields to the original out of the box view, which can be done from either the Form Layout or Form Design tools.

3. Create a UI Policy that hides the fields (visible set to false under the UI Policy Actions) that are not needed based on conditions for Portfolio or Team or even Methodology (any condition that is desired).  Remember that you cannot add the sn_align_core_scrum_epic or sn_align_core_feature tables to the UI Policy from the Global scope.  You must be in the Portfolio Planning Core scope when you create the UI Policy.

[juliebailey]

Thank you for your responses, @Naveen20 and @alexankaras.  We will give these two options a try and let you know how things go for us.