Events: Following events are available in the system:
Account Usage Limit Exceeding: This business function takes place when you want to disconnect the account if usage limit is exhausted.
Confirm Request: This business function takes place whenever provisioning requests are confirmed in the system.
Create Prospect: This business function takes place when a prospect is created in the system.
On Bulk break down closure: This business function takes place when a bulk break down is closed.
On Payment Request Failed: This business function takes place when a payment request fails.
On Vacation End: This business function takes place at the end of a vacation.
On Vacation Start: This business function takes place at the start of a vacation.
On Creation of Bulk break down: This business function takes place when a bulk break down is created.
On new order: This business function takes place when a new order is booked.
On order approval: This business function takes place when an order is approved.
On order reject: This business function takes place when an order is rejected.
On Suspending Agreement:
Payment: This business function takes place when a Payment is done through Payment screen or Payment upload.
Service Usage Limit Exceeding: This business function takes place when you want to disconnect a particular service if usage limit is exhausted.
When Closing Work Order: This business function takes place at the time of closing work orders.
When Contract is Disconnected: This business function takes place when a contract is disconnected from Disconnection screen.
When Contract is Reconnected: This business function takes place when a contract is reconnected from Reconnection screen.
When One Time Sale is created: This business function takes place when one time sale is done through One Time Sale screen or through One Time Sale upload.
When New Work Order is Created: This business function takes place when a new service request is created from Work Order screen.
When New Customer is Created: This business function takes place when a new customer is created. Send mail action can be mapped to this event to send a mail to the concerned person when a new customer is created in the system.
When New Order is Initiated: This business function takes place whenever new orders are booked in Service Order screen.
When New Service Request is Created: This business function takes place when a new service request is created from Service Request screen.
When Password is Changed: This business function takes place when the user changes the password. This is used to inform the external provisioning system on changing the password in the application.
Whenever a Service Request is Closed: This business function takes place when a service request is closed. This can be used to inform the customer or the service provider regarding the closure of the ticket.
When Service Request is Modified: This business function takes place when a existing service request is modified from Service Request screen.
Whenever a Service Request is Escalated: This business function takes place when an existing service request is escalated.
Whenever a Work order is Escalated: This business function takes place when an existing work order is escalated.
Whenever a Workorder is Modified: This business function takes place when an existing work order is modified. This can be used to inform the concerned person regarding modification of the customer.
When user is activated: This business function takes place when a user is activated.
Actions: Following actions are available in the systems:
Approve Provision: This action is used to approve provisioning actions.
Assigning Team or Employee: This action is used to assign a team or employee when a service request or work order is created.
Change Network Account Password:
Change Start Date: This action helps to update contract and billing start date.
Collection: This action is used to follow-up for the customer.
Create Service Request: Through this action service requests are generated implicitly
Create Work Order: Through this action work orders are generated implicitly.
Custom Action:
Disable Billing: This action is useful to stop billing a customer contract.
Disconnect Contract: This action is used to disconnect a contract.
Enable Billing: This action is required to start billing a contract.
Escalate Document: This action is used to escalate a work order or service request.
Generate Bill: This action is used to generate bill.
Generate Credit Note: This action is used to generate credit note.
Generate Debit Note: This action is used to generate debit note.
Increase Adhoc Limit: This action is used to increase usage limit of a plan.
Inform External: This action is used to inform external system.
Modify Service Request:
One Time Sale: This action is used to sale an item.
Send Bulk Email: This action is used to send e-mail in bulk.
Send Bulk OSD: This action is used to send OSD messages in bulk.
Send Bulk SMS: This action is used to send SMS in bulk.
Send Email: This action is used to send Emails to the customers' Email Ids.
Send OSD: This action helps to send OSD messages to the customers' TV sets.
Send SMS: Mobile SMS are sent to the customers through this action.
Send STB Mail: This action is used for the purpose of sending STB mails to the customers' Set Top Box.
Suspend Process: This action is used to suspend provisioning and billing.
Suspend Provisioning: This action is used to suspend a service.
You can select any of the event-action combinations and define action guidelines.
For example:
If a service provider wants to generate installation work order and approve provision whenever a new service order is booked. To achieve this business requirement, following two action guidelines should be defined in the system:
Action Guideline1: When New Order is Initiated (Event) 8 Create Work Order (Action1)
Action Guideline2: When New Order is Initiated (Event) 8 Approve Provision (Action2)
If a service provider wants to inform the customer through Email and SMS whenever work orders are closed, then the following action guidelines can be set in the system:
Action Guideline1: When Closing Work Order (Event) 8 Send Email (Action1)
Action Guideline2: When Closing Work Order (Event) 8 Send SMS (Action2)
When a new contract is booked and work order is generated to install necessary hardware at the customer's place, then contract and billing start date should be updated with the work order closing date. In this case, following action guideline can be set in the system:
Action Guideline1: When Closing Work Order (Event) 8 Change Start Date (Action1)
If a service provider wants to bill a contract immediately after service activation, then following action guideline can be set in the system:
Action Guideline1: Confirm Request (activation request) (Event) 8 Enable Billing (Action1)
When a new contract is booked and work order is generated to install necessary hardware at the customer's place, then billing should be disabled till the work order closing date. To achieve this business requirement, following three action guidelines can be set in the system:
Action Guideline1: When New Order is Initiated (Event1) 8 Create Work Order (Action1)
Action Guideline2: When New Order is Initiated (Event2) 8 Disable Billing (Action2)
Action Guideline2: When Closing Work Order (Event3) 8 Enable Billing (Action3)
Likewise, you can map actions with events and define action guidelines for conditional execution of the action when an event is fired.