Community - About gauri

gauri · ‎10-27-2020

Callout will offer more flexibility to build the Request payload than the CRUD update task. Update task is SOAP API and I would rather use the REST callout over it anytime.

gauri · ‎10-27-2020

Yes, Assuming you are updating the custom field using the api callout on that object, you can certainly use the liquid expressions in the Request body and able to conditionally set the custom field.

gauri · ‎10-27-2020

@karuv Start with building a data query to get the sum total amount of the invoices with the criteria you have. Use the Data query UI to test this part. Once you have the query finalized, test it in a workflow by adding - 1) Retrieve: Data query task - use your query 2) on success of step 1 add Logic: Liquid task to read the cumulative sum value from the Data.LinkRun to a Liquid variable. (do not prefix the variable name with an underscore else the scope will be limited to this Logic task) 3) this custom variable will be available now these are a high level steps to get what you need. Hope that helps.

gauri · ‎10-27-2020

yes that should work.

gauri · ‎10-08-2020

yes, Make sure the Workflow is configured for a Callout and then you can trigger a workflow through API https://www.zuora.com/developer/api-reference/#operation/POST_Run_Workflow you should be able to set an event trigger on the object programmatically as well.

gauri · ‎10-07-2020

The data from the Callout needs to be evaluated first. so save the Callout results in a liquid variable before doing the check. try this - {% assign zRangeVar = Data.Callout[1].ResponseBody.ZRange__c | slice: 0, 12 %} {% if zRangeVar == 'Non-Embedded' %} "embeded": "Non-Embeded" {% else %} "embeded": "Embeded" {% endif %}

gauri · ‎10-07-2020

Then I suggest copy and paste the script into notepad and convert to plain text. There might be an invisible special character somewhere. Remove any newline, tabs. can you post the liquid code that's erroring ?

gauri · ‎10-07-2020

what's the error you are getting? Is the error occurring in Email Notification task or a different task ?

gauri · ‎10-07-2020

"Disable Editor" checkbox

gauri · ‎09-29-2020

This is very helpful. I have emailed you with a question.

gauri · ‎09-25-2020

@ bensmiles did your question get resolved ?

gauri · ‎09-25-2020

Late response but I would like to iterate the previous response. In workflows, always do any complex data manipulation and transformation using the Data Query task which is SQL based data extraction tool. In case you haven't used already try it at Platform->Data query to play with the the query, save it if needed. Its a great, handy tool. Once you have retrieved the what you need, transform using the JSONTransform. If you need to get an ancillary effect on the data then Liquid expressions (Liquid task) can also be beneficial to get the same custom JSON that you are looking for.

gauri · ‎09-06-2020

I suggest you achieve the cumulative sum of invoice items by using a Logic (Liquid) task and iterate through the collection of the data objects.

gauri · ‎08-05-2020

we need to be able to filter the credit memos by the source. but the API doesn't let you. Is it possible to have the Get Credit memos API accept the "source" as filterable query parameters? Having this filter will allow the workflow to filter the response payload than having to shift through the records via custom code. The other option was to use data query but the data query on the credit memo doesn't work well as it can not be joining to the Invoice object but can only be joined by the accountid. so whats the best way to sort the response from the GET credit memo api call? how can the api accept a filter such as - referredInvoiceId is not null ? https://www.zuora.com/developer/api-reference/#operation/GET_CreditMemos

gauri · ‎06-23-2020

Is there any update on this ? We have a similar requirement and will lile to overwrite the exisitng workflows which will allow the ids to be the same . Importing the JSON as a new workflow is not the best route.

gauri · ‎06-11-2020

I have a JSON data that I am tryign to write to a csv file. but keep receiving this error - The custom liquid terminates in an object of class String.. The "test_array" is set to "test1":123, "test1", 456 Here's the settigns of the task: Processor: CSV Liquid Input: {{Data.Liquid.test_array | to_json}}

gauri · ‎05-26-2020

Check the "Skip Validation" option on the task and then click Update.

gauri · ‎04-01-2020

The GET https://rest.apisandbox.zuora.com/workflows/<workflow_id>/} returns a basic information of the workflow - id/ name created at etc The same GET call provides more data when it's given a task id of an execution run. My question is how to get this task id of a execution run number form a workflow id ? From the Run History UI , its possible but how can we programmatically ? So essentially trying to know if it is possible to query - 1) the Execution Run number and 2) the TaskId of this execution Run Any ideas?

gauri · ‎03-10-2020

Any update on this idea? we have a similar need and looking for options are available.

gauri · ‎03-01-2020

API documentation says the Custom Objects service in In Development. Any ETA when this feature will be released ?

gauri · ‎02-26-2020

Any update on the implementation of the enhancement to not create billing documents if all items are 0.? I had posted a similar question on the API side - Is there any option to avoid the zero dollar charges getting invoiced when an invoice is generated by the Billing Generate REST API ? https://www.zuora.com/developer/api-reference/#operation/POST_GenerateBillingDocuments

gauri · ‎02-26-2020

https://community.zuora.com/t5/Billing-Payment-Ideas/Option-to-Do-not-generate-invoices-with-0-Invoice-Total/idi-p/24250 @nharlow you had replied in the above thread that " We're considering an enhancement to not create billing documents if all items are 0...". Any update on the implementation of the idea ? I had a similar question on the API side. See the original post above.

gauri · ‎02-24-2020

Given a account id and subscriptionId(s) to the POST httpRequest, the billing generate API invoices zero dollar charges on a subscription. Is there any option to avoid the zero dollar charges getting invoiced ? https://www.zuora.com/developer/api-reference/#operation/POST_GenerateBillingDocuments

gauri · ‎02-18-2020

yes you will be able to access the columns in the downstream Email task. Inside the "Body" you would be able to iterate through the Data using liquid syntax. for example - {% for acc in Data.Account %} Account Name is {{ acc.AccountName }} Account Id is {{ acc.AccountId }} {% endfor %}

gauri · ‎02-18-2020

change this line - WHERE Subscription.Name = {{Data.Subscription.Id}} to WHERE Subscription.Name = '{{Data.Subscription.Id}}'

gauri · ‎02-17-2020

yes, if you want to access the variable across tasks. assign tag saves the value in the payload under the Liquid key.

gauri · ‎02-17-2020

use the assign liquid tag {% assign my_variable = 'the value' %}

gauri · ‎02-17-2020

Old thread but just want to add my observations to anyone who runs into these validation errors while using liquid variables - 1) while using liquid variables across the downstream tasks in a workflow click the checkbox to "skip the validation". 2) Use Swimlane on the tasks to debug and test the liquid variables. 3) If using liquid variables inside an "Email" task, then check the "Disable Editor"

gauri · ‎02-14-2020

Hello https://www.zuora.com/developer/api-reference/#operation/GET_Workflow after a workflow is kicked off (on demand/ callout) we are making an API call to report the tasks count - success/ failed. When we run the GET call we are not seeing the same datafields in the response as the example states in the API documentation. No status or the Tasks is returned. Any ideas?

gauri · ‎01-31-2020

🙂

Happy Business Starts Here