Activity Actions

For each transaction listed on the Activities tab, an Actions menu () lists every action available for user selection. This menu varies according to persona and transaction type. For abbreviation descriptions, see Transaction Types. The possible actions include the following options:

Conflict resolution. For multiple service order transactions. Takes you to a page with available actions for multiple transactions. For more information, see Conflict Resolution.

Note: When the system detects multiple service orders for a given activity, a reason code of SO_MULTIPLE is displayed. In this case, a Conflict resolution option is available from the Actions menu (). Select this option to view or edit the activities related to the outstanding service orders.
Assign activity to myself. Assigns the activity to the current user. Valid for any transaction type for the Market Transaction Operator and Billing Operator personas.
Assign activity. Displays a user drop-down menu. Valid for any unassigned transaction type and available to the Market Transaction Analyst, Managed Service Operator, and Billing Analyst personas.
Re-assign activity. Displays a user drop-down menu. Valid for any transaction type for the Market Transaction Operator and Billing Operator personas. For Market Transaction Analyst, Managed Service Operator, and Billing Analyst personas, the activity’s Assigned to value cannot be blank.
Edit status/note. Opens a dialog box that displays editable Status and Note fields. Valid for any transaction type for the Market Transaction Operator, Market Transaction Analyst, Managed Service Operator, Billing Operator, and Billing Analyst personas.

Tip: In the dialog box, the Note preset field contains a drop-down menu with previously saved notes. For future reuse of text in the Note field, select Save current note text as a preset.
View history. Valid for all transaction types and personas. Takes you to the Activity ID page with all historical activities displayed in table format.
Set transaction status. Valid for SOR, VMDR, PMDR, CDR, CDN, LSN, and SAR transactions for which the status is not CLOSED and the reason code is not SO_FAILED_TO_REVERSE.

Note: In some cases, additional rules may apply.

Opens a dialog box with a Transaction status drop-down menu and a selection menu of common use cases. Upon submission, the activity status is set according to the selected case. Some cases require a reason code.
Auto-raise. Valid for SOR transactions for which the status is not CLOSED and the reason code is not SO_FAILED_TO_REVERSE.

Note: In some cases, additional rules may apply.

Opens a dialog box allowing you to edit the Scheduled date and Special instructions for the parent transaction. These fields are prepopulated with values found on the General tab (see the Timeline and Note panels). The auto-raise action sends a service order request to the customer information system (CIS). Upon submission, the activity status is set to CLOSED.
Cancel in CIS. Valid for SOR transactions for which the status is not CLOSED and the reason code is not SO_FAILED_TO_REVERSE.

Note: In some cases, additional rules may apply.

Opens a Work order details dialog box for Event Code and Special Note (required fields). Sets the status of the service order to CANCELLED and cancels the activity in the customer information system (CIS). Upon submission, the activity status is set to CLOSED.

Tip: You may also need to manually close any related SOR cancellation activities.
Not completed (from activity). Valid for SOR transactions for which the status is not CLOSED and the reason code is not SO_FAILED_TO_REVERSE.

Note: In some cases, additional rules may apply.

Creates an SOR and opens a dialog box for Event Code and Special Note (required fields). Sets the status of the service order to CANCELLED and cancels the activity in the customer information system (CIS). Upon submission, the activity status is set to CLOSED.

Tip: You may also need to manually close any related SOR cancellation activities.
Resubmit to external system. Valid for all transaction types. Resubmits a transaction that has already been sent but now contains an error reason code. No additional input is needed. Upon confirmation from the external system , the activity status is set to CLOSED.

Note: For SAN transaction types, if the update to the customer information system (CIS) is unsuccessful, a new activity entry is created for the SAN when the failure reply message is received. In this case, the status of the SAN will be set to ERROR. For MDN transaction types, MTS sends a notification to IEE and sets the activity status to CLOSED.
Accept transaction. Valid for all transaction types. Accepts activities for which an acceptance/rejection has not already been sent and the status is not CLOSED.

Note: For VMDR transaction types, the MDN will be sent with the related Request ID, along with the current system data, to the requesting participant. However, if the Investigation Code contained in the VMDR is Recipient not responsible for the NMI, no MDN is required. Upon submission, the activity status is set to CLOSED.
Reject transaction. Valid for all transaction types. Rejects activities for which an acceptance/rejection has not already been sent and the status is not CLOSED. This action opens a dialog box with Event code and Reason drop-down menus (required fields). The status of the received transaction is set to REJECTED, and the processing of the transaction ends.

Note: For VMDR transaction types, the Reason field is mandatory except in the case of No data found. Upon submission, the activity status is set to CLOSED.
Submit to external system. Valid for the CDN, SAN, and MDN transaction types for which the status is not CLOSED. For CDN transactions, the transaction data is sent via the Push to CIS interface. Upon confirmation from the external system , the activity status is set to CLOSED.

Note: For SAN transaction types, if the update to the customer information system (CIS) is unsuccessful, a new activity entry is created for the SAN when the failure reply message is received. In this case, the status of the SAN will be set to ERROR. For MDN transaction types, MTS sends a notification to IEE and sets the activity status to CLOSED.
Resend accept transaction. Valid for the VMDR transaction type. Re-sends acceptance activities for which the status is not CLOSED. Upon submission, the activity status is set to CLOSED, and the VMDR status is set to COMPLETED.
Retry validation. Valid for a PMDR transaction for which the status is not CLOSED. Re-initiates transaction validation, sets the activity status to CLOSED upon successful validation, and sends an MDN. If validation is unsuccessful, a new PMDR activity is raised.
Update service order response. Valid for an SOR transaction type for which the status is not CLOSED. Opens a dialog box with an Exception code drop-down menu and a Service order response notes field. Upon submission, the activity status is set to CLOSED.