Display connect Estimated Delivery Date

Brian Lancaster
Tera Sage

I have multiple request items using the same workflow. Each one has a different delivery date. How can I show the correct estimated delivery date on the portal without having to create workflow for each different time frame?

13 REPLIES 13

No I'm says they all use the same workflow because it is a very simple workflow that all our items follow. Example: Order > Manager Approval > 1 catalog task.

But each specific catalog item has a different delivery time frame.

Hi Brian!

I realize this thread is a couple of years old, but I was wondering if you came up with a solution for this? We're in the same exact situation--we reuse simple workflows for multiple items and have set the delivery_time on them to reflect how long each one actually takes to deliver. The one idea I had was to add a custom widget to the portal cat item pages that displays the delivery time and turn off the OOB display of it.

Thanks!

So what we ended up doing was hiding the estimated delivery time. Then in the description of the catalog item we add info on if it needs approval and once its approved we stated something like this item is usually deliver in 3 days. Since we have the SLA attached to the RITM is set to approved I then use this script to set the due date (this runs in the workflow). Then that is sent out in a notification letting the user know when to expect that item to be delivered.

var gr = new GlideRecord('task_sla');
gr.addQuery('task', current.sys_id);
gr.query();
if (gr.next()){
	var dueDate = new setDueDate().CalculateDueDate(gr.sla);
	current.due_date = dueDate;
}

 

Thank you, Brian! We're doing the same with due dates, which is definitely helpful. We'd love to be able to display that estimated delivery time from the sc_cat_item.delivery_time on the catalog item itself in the portal. I think maybe we'll come up with a way to automate appending the delivery time in the description of the item, taking a tangent of the suggestion you made. Thanks!