ECC Pro: Estimated Delivery & Delivery Date

[Josh Pirozzi]

On the Request Summary page there are the options for 'Estimated Delivery' and 'Delivery Date' that we are trying to have display separate dates, but are running into difficulty locating and linking the HTML/Scripting to display the dates correctly. 

We're currently using the OOTB 'SC Order Status' Portal Widget and, because of the read-only policies, haven't made any adjustments to the widget functionalities. For our purposes, I'll be making a clone of the OOTB widget and only modifying the data that populates for the 'Estimated Delivery' and 'Delivery Date' fields. What we're trying to achieve is:

• On 'Estimated Delivery': Display the total number of anticipated days for completion of a request item. This is currently driving from the Days entered within the Flow, and is working as expected.
• On 'Delivery Date': Display the Date the RITM has been completed. What is currently displaying is the same data as on 'Estimated Delivery' and we're unsure what aspect(s) of the widget would need to be updated and how to pull the Date from the RITM Completed Date/Time field.

[Josh Pirozzi]

@RodGallegos @Mallidi Suma - Thank you both for the updates!

@Mallidi Suma - I've tried applying your Portal Widget, but it didn't pull the RITM Closed_at date through to the Delivery Date Column.

@RodGallegos Hey Rod!! I've added the line of script and reviewed the Restricted Caller Access List, but neither worked to pull the RITM Closed_at date through to the Delivery Date Column.

[Mallidi Suma]

Hi @Josh Pirozzi ,

I would suggest you work on your new PDI Once and check whether it is working or not. If it is not working only in your client instance then you can check for any customization.

Thanks & Regards,

Suma.

[RodGallegos]

The gs.addInfoMessgae is just there so you can check your system log to see if when the script runs, your code is doing what you'd expect;  like retrieving a given date. The Restricted Caller List would possibly show you a "Requested" record that might've been created when the widget tried to fetch the data and due to cross scoping, the widget was denied access. Typically I would open portal page with the new custom widget first because this will trigger your code to run (obviously), then head over to the Logs table and see if your info message appears. If the text of your logged message appears and not the data (i.e. closed_at_date) then the script isn't getting the data.