Bypassing workflow

For performance reasons, batch processes in Operations and Regulations Billing and Meter Management will bypass any personalized workflow for the affected business objects.

For example, some billing batch processes create or update service requests for billing accounts, but Operations and Regulations won't execute any personalized methods or formulas on the CRM.ServiceRequest object while completing these processes.

Billing batch processes will bypass any workflow formulas or methods for these objects:

Billing.Account
Billing.AccountActivity
Billing.AccountAlert
Billing.AccountDelinquency
Billing.AccountTradeWaste
Billing.AccountTransaction
Billing.AccountTWField
Billing.AcctHistUsageDetail
Billing.AddressService
Billing.ArrangementTransaction
Billing.Bill
Billing.BillMessages
Billing.BillRun
Billing.BillRunActivity
Billing.Collections
Billing.CollectionsRun
Billing.DelinquencyHistory
Billing.DelinquencyRun
Billing.DepositCharge
Billing.DepositTransaction
Billing.DirectDebitRun
Billing.DirectDebitRunActivity
Billing.LineItem
Billing.LineItemImperviousArea
Billing.LineItemPenalty
Billing.LineItemPenaltyStage
Billing.LineItemRate
Billing.LineItemTrackedRead
Billing.Log
Billing.OneoffCharge
Billing.Payment
Billing.PaymentBatch
Billing.PaySpecificBill
Billing.PenaltyRun
Billing.PostPaymentsRun
Billing.ProcessLog
Billing.RebateTransaction
Billing.SewerTrackedReading
Billing.StormTrackedReading
Billing.TradeWasteSample
Billing.WaterTrackedReading
core/.BatchProcessing.UserExceptions
CRM.ServiceRequest
Property.Addreslien
Property.ParcelLien
Resources.CreditHistory
Resources.IdentityBanking
Resources.RateTable.CalculationDetail
Resources.TimeSchedule