.Service Remarks tab v2020.3

Remarks

Remarks Tab example

The Remarks tab provides the User the ability to add comments and Remarks to this Service. By default, a Remark cannot be edited or deleted once it is added. To alter this behavior, see the Configuration Option: REMARKS_EDITABLE.

Adding Remarks

After clicking the button, the data-entry form opens with two tabs. Users can review the Remark on the Remarks tab, or add/edit them on the Edit Remarks tab.

The text can be formatted with Bold, Italics, or with hyperlinks. Additionally, the User can add ordered lists or unordered lists. Click the button to add the Remark.

Note: Remember that depending on the system configuration Remarks may not be editable once added.

Use of HTML Tags

Some fields within PCR-360 allow Users to input HTML tags to make displaying that information a richer experience for those that are expected to consume it. For more information on HTML tag usage, please see the wiki entry for it.

Viewing Remarks

Selecting the View Remark button opens a read-only data-entry form that displays the text of the Remark.

Adding Via 360 View

Service 360 View form example

An alternative way to add a 'Remark' is from the 360 Search. If a User selects a matching Service from the 360 search results, the Service 360 View form opens. At the bottom of this form, there are a series of buttons. Users can find the 360 View version of the button. Clicking this button brings up the Add New Remarks form as well.

Aging a Remark

With Aging the general idea is that the data on the Service should be removed. This would include any Remarks. So the question of "What happens when a Phone Number is receiving harassing phone calls?" arises. Normally, an Administrator might add Remarks to the Service to explain why a number is set to Inactive. However, since the Aging process might remove the Remarks about the harassing calls, that data then gets lost.

So the real question here is how can an Administrator make it so that the Service is not reused after Aging to prevent the harassing calls from recurring for someone else?

The best way to handle this is to set the Service to a Service Pool with Services that are designated "Do Not Use". By adding the Service to this Pool, the Service will be designated to not be used simply by being in the "Do Not Use" Pool. Additionally, the Administrator can add a User Defined Field (UDF) that will persist through Aging as well, with the flag "Verify Field Data" set to call attention to UDF. Using the method provides a backstop to the need to not use the Service since a Remark could easily be overlooked when re-assigning the Service with an Add Action.