Replace Mobile App Binary using QaCONNECT REST API
Before reading this you might want to see:
Main Article
Your application may have builds and updates that come in regularly, this might be a worrying factor if you have uploaded the Mobile App Binary to Secure Worksoft SaaS Storage. Well, Worksoft SaaS has a feature to replace the existing Binary with the latest one.
This process is very similar to Uploading the Mobile App Binary into Worksoft SaaS storage. By default, the service prevents overwriting files previously stored in the temporary sauce storage with a specific customerIdentifierForMobileApp.
- If you want to replace the previously uploaded app binary with a new binary, you must explicitly pass a value of 'R' for the parameter 'actionTypeCode'.
The valid values are 'N' for new or 'R' for replacement. The default value is 'N'.
To find more details on replacing Mobile App Binary using QaCONNECT REST API, click here and refer to the example, Replace a Mobile Application to Worksoft SaaS in the POST method.