About sourak

sourak · ‎09-01-2016

Hi -- I was wondering if / when this was going to be fixed? If it's not going to be fixed for a long time I would need to manually correct this in my factories... Regards, KWS

sourak · ‎07-05-2016

Currently, if we're allowing Zuora to manage credit cards, transactions are posted as one-off rather than using tokenization. The real challenge begins when we consider the case of a client attempting to defraud checkout: the Stripe Fingerprint (a unique ID to the credit card itself regardless of tokenized or one-off processing) is not passed back through Zuora to the API / Interface. This means that we cannot see if someone is attempting to purchase multiple new subscriptions with the same credit card information. I would like to suggest that the fingerprint be associated with each PaymentMethod and that, like the rule of a PaymentMethod not being associated with more than a single billing account that you'll encounter, the fingerprint field can be set as "unique" and will throw an error if there is an attempt to create a duplicate PaymentMethod. Regards, KWS

sourak · ‎06-30-2016

Very excited to see this changed to UC.

sourak · ‎06-08-2016

@lukasz Thanks for the feedback. I'm also interested in similar behavior for standard fields, just to be clear. I'm assuming that's also not on the current roadmap but just wanted to make sure...

sourak · ‎06-08-2016

Custom fields already give us the ability to define defaults. I'd like to extend four abilities to all field types (custom and standard): Constraints (e.g. field input must match a certain regex) Required? (currently only available on custom fields) Dependencies (e.g. if this field is filled out, this other field must also be filled out, but if this field is nil, that field can also be nil) Update Options on standard picklist fields (for example IIA Reason) I know that some of these things already occur for standard fields but it would be nice to be able to have tighter control over them / make them customizable. For example: perhaps I want to force certain users to always fill out a field on an IIA if the reason is "Cancellation."

sourak · ‎06-01-2016

Thanks for the update, @lukasz...any way we could be a part of those limited customers? I can think of an entire room of engineers over here that would probably throw a party. KWS

sourak · ‎06-01-2016

Currently, there are c for many events on important objects (let's take, for this example, invoices) that allow timely callouts to external systems. Unfortunately, the current callouts are very limited and prevent a good implementation of an external service being synced in an efficient way to Zuora as they are lacking update and delete event notifications. For important objects, one should be able to set a callout on update or delete, not just insert. Having an insert-only callout doesn't enable efficient integration as it requires the receiving service to make many, many unnecessary queries to keep in sync with Zuora as it will never otherwise know if an object has been altered or deleted.

Happy Business Starts Here

Vision

Products

Zuora Central Platform

Products

Zuora Marketplace

Solutions

By Industry

By Role

Customers

Resources

Resources

Subscribed

Support

Company

Re: describe api - updateable flag on product rate plan charge

Add Stripe Fingerprint to PaymentMethod

Re: Export / Import configuration

Re: Custom Requirements and Contraints Settings for Fields

Custom Requirements and Contraints Settings for Fields

Re: CRUD Callout by Object

CRUD Callout by Object