Support for plugins with optional parameters & user-based defaults

Yes @ashokmoorthy you can use both 1. the Queries keyword (provided by the user) + 2. the user attribute ingested from ServiceNow in your Query API configuration.

Check out the documentation here: https://developer.moveworks.com/creator-studio/integrations/outbound/api-configuration/#using-queries-keywords-as-variables-in-your-api-request

Thanks @yagarwal for the input.

I understand that we can get the input from the user via utterance (explicitly) or using ingested attributes(implicitly) . But consider my above use case where API is not from SNOW but from application like Splunk where we have mandatory field user location. Splunk doesn’t aware of user location like SNOW so we always have to pass the parameter.

But in this case,

1. If user asks “Show my network status in Bangalore” → I can pass the location to the API
2. If user asks “show my network status” → Assume user asking for his/her location, where he based out of - here the bot know the user location and we have to have pass implicitly.

Is there a way where I can build a use case with explicit param and if not take it internally.  Let us know your thought.

@ashokmoorthy are there specific benefits to building a shared API for both actions rather than splitting them out?

Yes, Development and operation cost from API side. And w/o this, we may need to build 2 different use case in CREST for single idea. 

Got it. @ashokmoorthy, so this is essentially support for Plugins with optional parameters that have defaults based on the user’s identity. 

This is actually already on our roadmap. It’ll be a part of our Workflows feature here and only available on the next-gen copilot: