- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-28-2022 05:45 AM
Hello Community,
I've noticed a strange issue in my personal developer instance and wanted to ask if anyone else can reproduce it or knows why is it not working.
In normal cases, when a project is closed, the "Closed" and "Closed by" fields are auto populated with the logged in user and the current date/time. This is the expected behaviour.
On projects, when all the underlying tasks are set to completed state, the state of the project also changes to Closed Complete automatically, therefor the "Closed" and "Closed by" fields should be populated as well.
If the tasks are updated directly on their form layouts or in the related list on the project, everything works well: Tasks are closed --> Project is closed --> Closed fields are populated.
However,
When the tasks are updated on the Planning Console of the project, the Closed fields are not populated at all.
I tried to create a workaround with a business rule, which is triggered AFTER update when the project state changes to "Closed Complete" and sets the closed fields accordingly, but the business rule is not triggered at all when the tasks are closed on the Planning Console and therefore the Project state is set to Closed Complete (so it's not an end user action, but a series of business rules in the background).
It looks like saving the changes on the planning console does not trigger the necessary business rules on the corresponding project.
Do you know any good workaround for this?
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-04-2022 03:28 AM
If anyone faces the same problem, here is the solution provided by SNOW Support:
Solution Proposed:
This is expected when Client-Side Planning is enabled (there is a Save button on the Planning Console.)
Business Rules will not run when set in this mode.
Make them fire when the State is changed by performing the following:
1. Go to Project Administration > Settings > Planning Console
2. Expand the Default Context and go to the one for pm_project
3. In the "Planning Console Display Columns" Related List, personalize the list to add the "Fire BR on Save" field
4. Find the record for "State" and set the field to true for that one
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-30-2022 11:48 AM
hmm im reaching here but i think i remember about asynchronous and synchronous modes in planning console- also it has had bugs before you may have to check KBs with ServiceNow for known issues or open an incident.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-03-2022 03:30 AM
I've created an incident, so let's see what SNOW has to say. In the meantime if anyone has any suggestion, please share it!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-04-2022 03:28 AM
If anyone faces the same problem, here is the solution provided by SNOW Support:
Solution Proposed:
This is expected when Client-Side Planning is enabled (there is a Save button on the Planning Console.)
Business Rules will not run when set in this mode.
Make them fire when the State is changed by performing the following:
1. Go to Project Administration > Settings > Planning Console
2. Expand the Default Context and go to the one for pm_project
3. In the "Planning Console Display Columns" Related List, personalize the list to add the "Fire BR on Save" field
4. Find the record for "State" and set the field to true for that one