Skip to main content
Package a VividCharts Asset into an Update Set

How to create an update set using the VividCharts Update Set Packager

Stephen Schwab avatar
Written by Stephen Schwab
Updated over a week ago

Step 1: Check that the VividCharts Update Set Packager update set is committed in “Retrieved Update Sets”

Step 2: Add app picker and update set picker to header through gear icon

Step 3: Change Application scope to VividCharts

Step 4: Go to “Local Update Sets”

Step 5: Create New update set

Step 6: Give it a relevant name, keep state as "In progress"

Step 7: Submit and Make Current. Keep this tab open.

Step 8: Open a new ServiceNow tab. Copy 'sp?id=vc_update_set_packager' and paste after your instance url so the url reads: 'hostname.service-now.com/sp?id=vc_update_set_packager'. Note, "hostname" is usually replaced by your company name.

You will be directed to a page that resembles this:

If you are having trouble accessing the VividCharts Update Set Packager, please reach out to VividCharts for support.

Step 9: Choose the asset you want to package. In this example, we are going to package a Summary Template.

Step 10: Select the elements to include by clicking the checkbox on the far left column.

Step 11: Confirm Current Update Set is correct

Step 12: Click Package to Update Set

Wait until the message appears: " '...' successfully packaged to the '...' update set"

From here, either add additional assets by repeating steps 9 - 12, or close this tab and move on to step 13.

Step 13: Go back to “Local Update Sets”. Click into the current update set

Step 14: Open “customer updates” in new window by right clicking on the filter

Step 15: Click the gear icon and add Application as a column

Step 16: Change application scope to VividCharts for all rows by right clicking on Application and choosing "Update All". In the Application field, type "VividCharts", then click Update.

Step 17: Go back to the update set record. Change state to "Complete" and Save.

Step 18: Export to xml

Step 19: Change file name to name of update set.

Step 20: Commit the xml to a testing instance to confirm assets have been captured as expected.

Did this answer your question?