Community - About JamesQSR

vivianzhang2021

Hi it seems like we can create the customized event trigger now. It is actually a flexible and powerful design for many integration/interface design. But I have two questions for this wonderful feature: after a quick test, it is interesting to find the event trigger like changeType = 'INSERT" works well, but the changeType = 'UPDATE' works a little bit weird with custom fields' conditions.For example, in the following condition, I expect the update is triggered only when the custom field "external system" is "salesforce", but actually the system behaves that only when the external system custom field is updated from null to "salesforce", as a quick example.... "CONDITION": "CHANGETYPE == 'UPDATE' && PRODUCTRATEPLAN.EXTERNALSYSTEM__C == 'SALESFORCE' && PRODUCTRATEPLAN.NAME != PRODUCTRATEPLAN.NAME_OLD" Another question is, do we have any plan to design the event trigger like changeType = 'DELETE"? similar to Salesforce's trigger like beforeDelete, afterDelete... which would be another powerful subset... Looking forward to master's reply.

msonsma · ‎03-15-2021

Hi, There is a much easier way to do this by using two undocumented workflow objects that exist when a workflow is executed: The WorkflowInstance object represents a workflow execution. This object is NOT documented yet. The attributes listed in the following table are obtained from either Zuora support and/or by trial and error. Attribute Description Id The workflow identifier number. This is the xxxx in the WF-xxxx-yyyyyyyy name. Name The instance name: WF-xxxx-yyyyyyy name. Status The status of the execution. ErrorTasks Collection of tasks that failed PendingTasks Collection of tasks that are pending The TaskInstance object represents the current task that is executed. This object is NOT documented yet. The attributes listed in the following table are obtained from either Zuora support and/or by trial and error. Attribute Description id The task's id number name The name of the task. status The status of the task: success, error The Workflow.Name is an unique identifier for the workflow instance. You use this value to mark entity as being been processed by a given workflow run. In our workflows we set-up a global payload variable JOBID that is initialized with: "{{WorkflowInstance.name}}-{{ "now" | date: "%Y%m%d%H%M%S" }}" to get a reference to both the workflow run instance and datetime. BR Manfred

JamesQSR · ‎12-05-2019

Thanks @ehavens I'm testing that this morning, and the invoices are good, just need to see how it also syncs to Netsuite, but its looking positive!

JamesQSR · ‎12-04-2019

What we do at the moment is create the product for 'Annual Billing', but we say that the billing period is limited (in our case 3years = 36 months) That way they will get billed every year, but then the subscription will expire after 3 years (or can then be renewed). Just be careful as depeding on what you put at the Billing Period, Zuora will then pro-rata the price based on the subscription length.

JamesQSR · ‎11-11-2019

It would be really useful to be able to re/arrange custom fields once created. At the moment they are shown on the Custom Field management page in reverse-chronological (newst >> oldest), but in the object they are arranged chronological (oldest >> newest) However, as business requirements change, its possible that enhancements are made out of order. Then when lookin in the UI for a particular field it would be good to place these together. Specific Example: On our Invoice Object we have added custom fields for: Service A provisioned (Y/N) Service B Provisioned (Y/N) Special Noted Service A Expiry (date) It would be handy to move the Service A Expiry field to be next to the other Service A field

JamesQSR · ‎10-20-2019

Hi @damonwitherick Did you get a response, or a working solution to this issue? We have just come up against a similar requirement. Thanks James

JamesQSR · ‎06-19-2019

So cribbing a few other posts I was able to come up with the following: Zuora Workflow Notification Callout HEADER Put: {{ Credentials.zuora.rest_endpoint }}object/invoice/{{Data.Invoice.Id}} (This is for to know if you are Sandbox or Production and send to the right place without modification) Key: Content-Type Value: application/json BODY { "objects":[ { "fieldsToNull":["transferredToAccounting"], "Id":"{{Data.Invoice.Id}}" } ], "type":"Invoice" } AUTHENTICATION Type : Zuora

JamesQSR · ‎04-28-2019

The alternative is that you use volume pricing, to build in this discount in the Product Rate Plan. Depending on your setup, your promocode could then make this volume price product available to your customers.

Happy Business Starts Here

Vision

Products

Zuora Central Platform

Products

Zuora Marketplace

Solutions

By Industry

By Role

Customers

Resources

Resources

Subscribed

Support

Company

Re: How We Implemented a Custom Event Framework

Re: Access to Run Number as a Workflow Data item

Re: Upfront Billing options

Re: Creating annual invoices when Billing Period is Three/Five Years

Ability to sort/arrange custom fields

Re: HPM and charging with URL on Invoice

Re: Set transferred to accounting flag to No via API

Re: Can a Promo Code be applied based on Qty of a specified RPCharge?