Page Comparison

...

To delete an existing Phone Service, simply highlight the item(s) to be removed and click the 'Delete Selected' button located on the Grid Toolbar above the Phone Services grid.

Aging

While Users can Image Added Services manually, Services will undergo the Aging Process automatically based on their Service Catalog.

There are a few requirements before a Service can be aged manually:

1. The Service must be 'Inactive'.
2. There cannot be any active recurring Charges. If there are active recurring Charges and the Service is Inactive, the status of the Services will first have to be made 'Active' to stop the Charges. Then the Service can be set to Inactive once again.
3. There cannot be any unbilled Charges. If there are, the billing process must run first to ensure proper billing for the Service.

The History Report of a Service will still show all the old data of the Service.

Once a Service has been "Aged" successfully, PCR-360 will change the status to available so that the Service ID can be reused on Service Orders for a new Owner.

There may occur a situation where a Service is desired to no longer be available after it has been "Aged" (such as if the number was receiving harassing phone calls). The best way to handle this is to set the Service to a Service Pool with Services that are designated "Do Not Use." Adding the Service to this Pool will be designated not to be used simply by being in the "Do Not Use" Pool. Additionally, the Administrator can add a UDF that will persist through Aging, with the flag "Verify Field Data" set to call attention to UDF. This method provides a backstop to the need not to use the Service since a Remark could easily be overlooked when re-assigning the Service with an Add Action.

The Aging Process in PCR-360 is an automated data removal process that will delete old information from Inactive Services. Examples of data that will be removed are the Owner, Service Host, and Location fields. Some information can be deleted or remain on the Service for future use on the Service ID. An example is the User Defined Fields (UDFs) can have the option to have their data persist or be scrubbed on Aging with the Aging Persist flag. Another example is the Configuration Option DELETE_CHARGES_DURING_AGING which will allow you to delete old Charges or leave them on the Service. Sometimes it can be necessary to manually "Age" a Service to make it active again. This process is normally handled automatically by either the setting on the Service Catalog or the Tenant Management Aging fields.