Input parameters
Input parameters use interfaces to access the data in your database. To add
an input parameter, specify the fully qualified name of the interface and an alias that will
be used to represent the interface in the template. For example, you would use an input
parameter such as Hansen.CRM.IServiceRequest SR
to get
service request properties. You can enter multiple input parameters, separated by commas. The
alias can be any value you choose.
Hansen.Resources.Notifications.INotificationMessage message
must be the first
input parameter. This can be used in the template to represent all or part of the text of the
message, rather than hard-coding it.After you define your input parameters, the available properties are shown in
the {{SR.Comments}}
for service request comments.
Because a workflow formula will be used to send notifications, your template
must include an input parameter matching the signature of that formula. You can use the
Workflow Manager to look up the signature. For example, when you add an AfterAdd formula for
the ServiceRequest object, the Signature field in
the Formula Editor shows that the interface to use is
Hansen.CRM.IServiceRequest
.
These are some of the most common interfaces:
- Notification message: Hansen.Resources.Notifications.INotificationMessage
- Service request: Hansen.CRM.IServiceRequest
- Application: Hansen.CDR.IApplication
- CDR inspection: Hansen.CDR.ICDRInspection
- Account: Hansen.Billing.IAccount
- Bill: Hansen.Billing.IBill
- Contact information: Hansen.Resources.IContact
- Contact: Hansen.Resources.IContactIdentity
- Address: Hansen.Property.IAddress
- Parcel: Hansen.Property.IParcel
- Portal account (for Rhythm for Civics): Hansen.Portal.IMembership