- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-09-2023 01:08 AM - edited 11-09-2023 01:15 AM
Hello,
We have a problem with all our Playbook Experiences not displaying the buttons (action configurations) on the activity cards:
The problem seems to be related to the "Associated Record" field on the Activity Execution (sys_pd_activity_context) record. The field is not populated with any Flow Data (sys_flow_data) record (which it is in my PDI):
When I populate the field in the image above with the correct Flow Data record using background script, the buttons are displayed...
According to this post, missing Playbook buttons might be related to ACLs. However, I have checked and compared ACLs on all the relevant tables (sys_pd_context, sys_pd_activity_context, and sys_flow_data) with ACLs in my PDI, but everything seems OK.
I have also tried repairing all relevant applications (Playbook Experience, Playbook Components, Process Automation Designer etc.), but nothing seems to fix the problem.
Does anyone have any idea what could be causing this?
Thanks!
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-09-2023 11:53 AM
I've found the solution!
The issue was related to the language setting of our ServiceNow instance. We had set Norwegian ("nb") as the default language, which caused the problem. After reverting the default language back to English ("en") and then reinstalling the "Process Automation Designer Core" plugin, everything started functioning correctly again. Basically, I believe there are some translation challenges that occur when installing new plugins when the default language is not set to a "widely used" language package. We noticed the problem due to log messages and Flow Context records not being executed correctly..
P.S. The customer's requirement is to have Norwegian as the default language for all users. To achieve this without changing the entire instance to Norwegian, we're creating a global User Preference setting that establishes Norwegian as the default language for all users: Users not able to change the language in the login page. - Support and Troubleshooting (servicenow.c...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-09-2023 11:53 AM
I've found the solution!
The issue was related to the language setting of our ServiceNow instance. We had set Norwegian ("nb") as the default language, which caused the problem. After reverting the default language back to English ("en") and then reinstalling the "Process Automation Designer Core" plugin, everything started functioning correctly again. Basically, I believe there are some translation challenges that occur when installing new plugins when the default language is not set to a "widely used" language package. We noticed the problem due to log messages and Flow Context records not being executed correctly..
P.S. The customer's requirement is to have Norwegian as the default language for all users. To achieve this without changing the entire instance to Norwegian, we're creating a global User Preference setting that establishes Norwegian as the default language for all users: Users not able to change the language in the login page. - Support and Troubleshooting (servicenow.c...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-17-2024 07:14 AM
Do you know if in the mean time, there is any other solution then change the platform language?