- My View
Could anyone please help me on the below query?
When creating a Resource Plan request in the resource_plan form, the Members list doesn't gets cleared on change of 'group_resource' field. Please have a look at the screengrab below, where the Group Resource is - 'Database Atlanta', but the Members list also has members from the previous selected Group Resource. So, there is no validation or check on the Member's list based on the Group Resource and doesn't clears the members from the previously selected Group resource.
Is this a bug or any valid logic behind it? (OR) Is there any fix for the below issue?
Users screengrab shows the Members who belongs to 'Database Atlanta' - Only 2 members ('Bow Ruggeri','Miller Andrew') ! But the Members list has other users too, which was selected from the previous Group Resource. The below screenshot is after saving the changes in Group Resource.
Thanks & Regards,
Probably you would need an OnChange Client script to empty the member list once the group is changed.
Thank you for your reply. Yes, if there is no fix in the future releases, then we would plan to make customizations.
As this is really an important feature and supposed to work on base configuration.
Have a Good Day !
Thanks & Regards,
FYI it looks like there is a good Out of Box (OOB) example of this type of onChange client script on the alm_entitlement table. That OOB client script is named "Null out assigned_to".
So you could easily use that as a guide to do something like the snippet below. That will yield the behavior where changing the Group resource entry will clear out the Members list. And because that field is mandatory, the user will then be forced to pick new members, which are restricted based on the new group selection: