Anyone edit the project go lives widget?

[jonathan_luste]

So I was adding widgets to a dashboard, and saw the Project management type, and there was a Go Lives thing to add.   I love it, but it shows too much and I want it to be filtered.   But I cannot find where it lives / is editable or clonable.

What I found is this:

Briefly mentioned on the docs site : CIO Dashboard

UI page is called projectGoLives.

UI page script contains "iframe src="/$project_go_lives.do""

And that's all I can find.   No where do I see source data controls or filters.

Anyone have a clue?

[Robert Chrystie]

Hi Jonathan,

Unfortunately, this is not a configurable widget as it references a page that ServiceNow does not expose to customers.

[jonathan_luste · Accepted solution]

Not by default it isn't.   That's true.   However we were able to do it, and I want to share that.

The project go lives as I see it is a UI page that runs .js.   The location of the js is here: /scripts/project_go_live_widget/get_project_go_live.js.   (Note, there is also a css that is needed, but we didn't mess with this, located here: styles/project_go_live/project_go_live.css)

Now, us mortals cannot edit this, but we can see it, and copy it.

What we did was to copy it, and create a new UI page "tps_go_lives_code" and insert the js copy into the client script section.   (we did make one change to line 44 (inner html) to make the projects URLs that open in a new window).

As far as the data filter, that's driven by a timeline (for roadmap). So we made one and edited the lanes and panels to be what we wanted.

To be able to render the widget AND have the widget render the data, we needed to have two UI pages, one for the code, and one for the widget.

so, tps_go_lives, which basically calls the tps_go_lives_code in a frame

[jonathan_luste]

Forgot to mention (and attach our ui pages as examples) that you will also have to edit the project management Widget to include the new go lives UI page in the drop down.

[Earl L]

This is awesome news. We're looking at the same thing right now, but perhaps for a slightly different reason. For us, we love the idea of a go-live schedule, but the OOB widget is using the project planned end date as a proxy for the go-live date. That's ok for some projects, but for many it's not. Especially if your project methodology requires some sort of post-implementation quality assurance or monitoring of metrics established during the project. In these cases the go-live date is not the same as the planned end date of the project. In fact, the go-live date could be much sooner than the project end date, so in those cases this widget fails.

Our approach is going to be to add a custom date field for the go-live date and we want to include that date as the basis for the go-live reporting. Thanks to your work (which I haven't had a chance to dig into just yet) I'm more optimistic that we can make this work. So, thanks for the post and the content.

Earl