Skip to main content

This content has been archived and is no longer being updated.

Links may not function; however, this content may be relevant to outdated versions of the product.

Configuring the security deposit property in the Transfer line service case

Suggest edit Updated on September 10, 2021

Pega Customer Service for Communications offers predefined Transfer line service cases to allow a customer (an account owner) to pass ownership of a number to another person who is a member of his account. To use this service case, you must have the basic contact details of the person to whom the line is transferred. Only the active numbers linked to the primary customers can be transferred.

When this service case in initiated, a message is sent to the primary customer, and the assumer (the secondary customer) receives an email notification with the transfer line details and a link to the self-service portal from which the customer can either accept or reject the transfer.

As a part of the Transfer line case, a security deposit is taken from the secondary owner based on their credit history. To define the security deposit property in the Transfer line service case, complete the following steps.

  1. Log in to Designer Studio.
  2. In the Explorer panel, click App and then select the PegaComm-FW-CF-Work-TransferLine class.
  3. Click Decision > Decision Table > SecurityDepositAmount.
  4. On the Table tab, edit the Conditions and Actions columns based on your business needs.
  5. Click Save.
Integrate the Transfer line REST connectors with your implementation application. For more information, see the Customer Service for Communications Implementation Guide.
Did you find this content helpful? YesNo

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Ready to crush complexity?

Experience the benefits of Pega Community when you log in.

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us