API for Update Sets

naokihada
Kilo Contributor

Hi,

Is there API for System Update Sets?

I could transfer workflow to other server by following instruction on web UI.

Moving Workflows with Update Sets - ServiceNow Wiki

Is there any API available for following steps?

1) Load XML for System Update Sets

2) Preview imported Update Set.

3) Commit imported Update Set.

Thank you,

Naoki

1 ACCEPTED SOLUTION

Hi Naoki,



The code which is written in the UI actions I send you can be used to create the appropriate logic in an inbound web service. Which logic would go in those web services would depend a lot on the process / features of the automated deployment that you will like to implement.



http://wiki.servicenow.com/index.php?title=Web_Services#Inbound_Web_Services



Thanks,


Berny


View solution in original post

22 REPLIES 22

Hi ,

 

The URL mentioned is not valid anymore. Can you please share the URL which we can access ?

 

Regards,

Dhyanendra

bernyalvarado
Mega Sage

In case it helps, you can also take a look to use Team Development for your deployment process.



Team Development - ServiceNow Wiki



Thanks,


Berny


Hi Berny,



I need your help to manage the defect fixing throughout the instances where we push Update Sets from one instance to another. This is basically SDLC project.



We have dev1, dev2, shared dev, test, prod instances and I need to define a release approach for product delivery.I have been told by the Dev team that once code is pushed to   dev1 from dev2, some defects are being fixed in dev1 directly as the defects are being instance specific.   We have multiple products being planned for a single release.



How do you suggest we need to have a robust set up for SDLC keeping the above instances?


When do we go for team development?


how do we plan to push code to client env?



Thanks,


Sug


Hi Sughosh,



Great question!



I believe you have two options:



a) Team Development


b) Git Integration



Go through the documentation and comments from others in the community to assess which option works best for you. I personally like our development teams to use GitHub but the last downside from it that I recall is that it used to overwrite all of the object history (previous versions) when doing a deployment from it to an instance so I prefer to still move changes upstream through the environments using update sets. Yet, either option will be a good fit to support your developers to keep their environments in sync. Just keep in mind... these are just tools; the team's discipline on following the process is what truly ends up making the difference.



Thanks,


Berny


Git Integration: Source control integration


Team Development: Team Development



Thanks,
Berny