Loading...
Loading...
When Teamspace and custom Phase Flow formatters are used, the base formatters for Process flow are seen in the Planning Console > Analytics tab. In other words, two flows will be seen and this will be disruptive to any user who accesses the Analytics tab in Teamspaces. This issue is only applicable when using Teamspaces and custom Phase flows*
When Phase Dictionary entry is defined differently for both tsp1_project and pm_project: 1. Navigate to System UI > Process Flow 2. Search for table "tsp1_project" 3. Change the name of the flow formatters and conditions as per the new phases on tsp1_project 4. Go to any record on tsp1_project 5. Go to Planning console related link > Analytics tab 6. Notice the Flow on the top > It has both pm_project phases and tsp1_project phases that are defined.
While this known PRB is fixed in our upcoming Quebec release, you may - in the meantime - import the resolved/modified UI Macro (which will be included in Quebec). Note: if you do import this XML and wish to keep the record open to system upgrades, you will need to navigate to the sys_update_xml table (sys_update_xml.list), find this record (name=sys_ui_macro_cadf29f18740330047d84c2c59cb0b15) and ensure that it shows 'Replace on upgrade= true' Navigate to any table list or UI Macros Right-click any column header and select 'Import XML' Import the attached XML: sys_ui_macro_cadf29f18740330047d84c2c59cb0b15.xml This will remove the base process flow in your Teamspace Analytics tab (if you have a custom flow introduced already)
PRB1422790
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.