Editing in Ad Hoc roadmap of project / demand items in APW record page is not updating the data correctly due the client script type as desktopDescriptionSeismic form component does not fetch client scripts of Desktop UI type. In Ad Hoc Roadmap, for Project/Demand/Program/Epic/Safe Epic/Safe Feature tables, there are some client scripts of UI type as Desktop. In Roadmap page, side panel Full Details Record Page, some client scripts will not work if the source tables is one of the mentioned tables. The issue does not occur for planning hierarchy based roadmap, as no client scripts of Planning Item and its extensions are of UI type Desktop.Steps to Reproduce 1. Go to Ad hoc roadmap page.2. Click on any pm_project roadmap item, in the side panel click on edit record.3. In Roadmap page, side panel Full Details Record Page, try to update the actual end date. This is not updating the duration correctly because of the client script type as desktop.WorkaroundThis problem has been fixed in San Diego, where Client Scripts type was changed to All for PMO. In pre-San Diego instances, follow the steps below to change to use the platform form for project/demand record: 1. Open 'Base Roadmap Workspace' page, create a new client script with the below code and save: // If api.state.formDataBrokerInput.sourceTable is one of the tables mentioned in the description or not an extension of planning itemconst exclusionTables=['sn_align_core_planning_item','sn_align_core_project']; //add as per requirementif (exclusionTables.indexOf(api.state.formDataBrokerInput.sourceTable) > -1) return;const url = "/nav_to.do?uri=" + api.state.formDataBrokerInput.sourceTable + ".do?sys_id=" + api.state.formDataBrokerInput.itemSysID;api.emit('NAV_ITEM_SELECTED', { "external": { "url": url }}); 2. Inside the body, find the item detail button component, click that and go to that component Events. Handler 'Link to destination (UXR Blank AppShell)' is used to re-direct the link to APW Record Page. Please open the handler and add condition using table variable to restrict it for above mentioned tables. A sample: // If api.state.formDataBrokerInput.sourceTable not one of the tables mentioned or an extension of planning item const inclusionTables=['sn_align_core_planning_item','sn_align_core_project']; //add as per requirement if (inclusionTables.indexOf(table) < 0) return; Add the script created in step 1 as another handler . Related Problem: PRB1516479