QAs in Moveworks

​@eberteo - You can get a sandbox instance provisioned. You’ll need to make that inquiry to your CSM to get that sorted out!

​@Kevin Mok do you know if that’s an extra price? or is included within the license?

Also what is the QA deployment like in Moveworks?:
Moveworks tenant QA ↔ ServiceNow tenant QA

Moveworks tenant PROD ↔ ServiceNow tenant PROD 

Additionally, how you serve deployment from one QA to another one in Moveworks’ side?

​@eberteo I don’t have an answer when it comes to pricing that’s going to something you need to discuss with your CSM or Account Executive as to what you are entitled in your contract.

A QA/Sandbox instance at Moveworks today, is just another individual instance, so you can connect it to any system whether that is your QA NOW instance or PROD.

Additionally, how you serve deployment from one QA to another one in Moveworks’ side?

I didn’t quite understand this part, can you expand there?

Good day ​@Kevin Mok,

Thanks for clarifying my queries. In regards to my last question, I’m trying to understand how you promote your changes worked in QA to PROD? Does Moveworks implement source control or some other workaround? - For example, my ServiceNow changes from QA are promoted to PROD using Update Sets or Source Control. In our standard web application we use Source Control. So I’m looking to know how does Moveworks handle this flow from QA to PROD. Please do let me know if you have more questions to clarify. 

​@eberteo Currently we don’t have a QA to PROD promotion method. With Agent Studio we do allow you to export a plugin and import it to your other instance, but when it comes to Moveworks Setup configurations you’ll need to manually do it. 

We are working on ideas on how to make this experience smoother

​@Kevin Mok  Ooh I see, that’s definitely a manual process even for Agent Studio and certainly I don’t know how efficient is this experience when doing collaborative working. Keep in mind, most enterprises have internal devs and external devs for all apps like in our case as organization, so that might be a grey area to discover in your end.

Moveworks should hire me, I’ll guide you with the best approach. I’ve seen promotions in multiple SaaS and APaaS applications.

Honestly as SWE is hard to get familiar with your Setup module. I’d do a flow approach for your Setup submodules and convert each submodule into a flow interface, and then provide the user the option to config them within the flow. Similar to Salesforce and SNow, the core config actions are following the same development approach like the OOTB and the customized ones. So anyone with the right access can modify them disregarding if they are high risk. So on, you can convert your Moveworks Setup to Workflow Studio and then bring into Moveworks Studio similar to ServiceNow Studio and then you have 2 in 1.

I believe the reason ServiceNow acquired Moveworks was because of the framework architecture in the AI pipeline (Compound Actions, Conversational Process, Plugins, Data Types) really smart. 

😩

Yeah, I agree there’s a lot of friction and risks when it comes to changing configs that could potentially make a skill not work. We are currently exploring ways to make these a lot smoother, thanks for the feedback, it’s something I can keep in mind for our future iterations.