One of our program managers identified an issue where the program manager is unable to change the planned end date. I found this thread on the issue, but the answers provided were focused on projects not programs.
Here is the message:
When looking at the program, the no dates match up from program tasks or projects under the program. As an admin, I can change the date. I've made it as far as seeing that the 'rollup' field is true and that there is not parent on the program.
My questions:
- What drives changes to the planned end date on the program?
- How can I unlock this field for our program managers to edit it?
Thanks for any help you may have!
Hi
This is an expected behavior and is working correctly as per OOB scripts.
"'Planned end date' is calculated based on the 'Estimated start date', 'Estimated duration', and the 'Schedule' (optional), and therefore cannot be manually modified."
If this is allowed to be modified by any user manually then it may affect other calculation logic as well which is happening as per OOB standard and can be a risky one to be modified.
In order to understand which ServiceNow component is controlling this is there are two Write Operation ACL on Program and Planned task table which restricts this.
Posting the link of both the ACL below:
https://instance.service-now.com/nav_to.do?uri=sys_security_acl.do?sys_id=63e00f137f000001436da4b3faabf6ac
https://instance.service-now.com/nav_to.do?uri=sys_security_acl.do?sys_id=4533d5e69320120064f572edb67ffbcc
Replace "instance' with your instance name.
There is a field named as "Rollup " which let the child task which comes under Program to get rolled up to program level and if the value of Roll up is true then no one except admin will be allowed to modify an existing date.
Only for New records user will be allowed to update the Planned End Date field.
This is the logic which is restricting currently you in your instance from updating Planned End Date field by any other user except admin.
Below is the link from ServiceNow which will explain how the Roll up field is set for these tables:
https://docs.servicenow.com/bundle/quebec-platform-administration/page/administer/task-table/task/t_ConfiguringRollupForPlannedTask.html
Also attaching screenshot of the ACL which shows what I have shared above:
Hope this helps. Please mark the answer as correct/helpful based on impact.
Regards,
Shloke
Hi
The program planned end date is governed by the program tasks, project, demands associated with that program. The program end date automatically extends if the newly added program task/ project / demand end date is outside the program's planned end date.
However, the program's planned end date never shrinks automatically in case you remove the added item.
IMO and also as per the documentation (refer below doc screenshots), the persona with it_program_manager should be able to manually update the planned end date of the program.
You may want to create a ServiceNow support case to get more clarification.
Feel free to mark the answer as correct / helpful if this response is able to resolve the query.
Thanks,
Namita Mishra
Hi
This is an expected behavior and is working correctly as per OOB scripts.
"'Planned end date' is calculated based on the 'Estimated start date', 'Estimated duration', and the 'Schedule' (optional), and therefore cannot be manually modified."
If this is allowed to be modified by any user manually then it may affect other calculation logic as well which is happening as per OOB standard and can be a risky one to be modified.
In order to understand which ServiceNow component is controlling this is there are two Write Operation ACL on Program and Planned task table which restricts this.
Posting the link of both the ACL below:
https://instance.service-now.com/nav_to.do?uri=sys_security_acl.do?sys_id=63e00f137f000001436da4b3faabf6ac
https://instance.service-now.com/nav_to.do?uri=sys_security_acl.do?sys_id=4533d5e69320120064f572edb67ffbcc
Replace "instance' with your instance name.
There is a field named as "Rollup " which let the child task which comes under Program to get rolled up to program level and if the value of Roll up is true then no one except admin will be allowed to modify an existing date.
Only for New records user will be allowed to update the Planned End Date field.
This is the logic which is restricting currently you in your instance from updating Planned End Date field by any other user except admin.
Below is the link from ServiceNow which will explain how the Roll up field is set for these tables:
https://docs.servicenow.com/bundle/quebec-platform-administration/page/administer/task-table/task/t_ConfiguringRollupForPlannedTask.html
Also attaching screenshot of the ACL which shows what I have shared above:
Hope this helps. Please mark the answer as correct/helpful based on impact.
Regards,
Shloke
shokle04-
Thanks for the response. ServiceNow support also sent me to the two ACLs which only open up the field. If I disable the ACLS the field is editable, but that does not get to the second part as to why the field isn't editable by our program managers.
My question now is about the rollup. On my instance I only see a single program related rollup (which appears to be set to rollup = 'false'). All other rollup values are false.
If there are no "true" records in the rollup table, then why is the field not editable by our program managers (per the second ACL above) which condition is "!current.rollup && current.canWrite();"? Shouldn't the program be set to rollup = "false" as there are no active rollups?
Thanks again for your help on this. I'm getting closer to an answer.
-Trevor
