Loading...
Loading...
The out-of-box Business Rule "Flows and Subflows" for certain use cases returns NullPointerException in the system logs when playbooks are in custom application scope. This is a query business rule on the [sys_hub_flow] table which has records of flows and subflows in the instance. This query business rule is based on condition if it is interaction session. "An interactive session is one that involves an end-user interacting with a user interface that then retrieves information from a server. An example of this type of session is when a user logs in using the log-in screen or uses a form to query a data store. A non-interactive session is one that only involves programmatic interaction with a server such as a SOAP request to retrieve data." It will then check the sysparm_view value from the URL it gets as an input, if it is a flow or a subflow, and based on that will add the query for flow type field.
This issue is use case dependent, as it was reported when executing playbooks in custom applications, but unable to reproduce out-of-the-box.
This problem s targeted to be fixed in an upcoming release. Subscribe to this Known Error article to receive notifications when more information will be available. As a workaround, try adding a condition to the business rule "Flows and Subflows" as shown in the screenshot:
PRB1640856
Click on a version to see all relevant bugs
ServiceNow Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.