Work with policy hold actions

Before you begin

You must have sufficient permission to view and work with the Policy Holds screen. For more information, see Policy hold permissions.

About this task

These step-by-step instructions show you how the Actions > Policy Holds menu item affects a policy with a hold. For information about this menu item, see Policy hold actions in renewals.

The instructions assume that you have loaded the large sample data set, and that you are creating a commercial property policy.

Important: The Actions > Policy Holds menu items apply to policy transactions in automated processing only. Therefore, you do not approve or reject the policy hold because this would remove the policy transaction from automated processing.

Procedure

  1. As su, create a policy hold for commercial property policy renewals as described in Create a policy hold.
  2. As aapplegate, create a commercial property submission as described in Create policy effective in the past.
  3. Create a second commercial property policy as described in step 2.
  4. As su, run the Policy Renewal Start batch process as described in Renew policies through batch process.
  5. As aapplegate, go to each commercial property policy.
    On the Summary screen under Pending Policy Transactions, notice that there is a Renewal policy transaction with Quoted status. The Current Activities shows a Blocked - Pending Renewal activity.

    For each policy:

    1. Click the Blocked - Pending Renewal activity link.
    2. In the left sidebar of the renewal policy transaction, click Risk Analysis.
      Notice that the UW Hold 001 is blocking bind.
  6. In the second commercial property policy, select Actions > Policy Hold > Do not issue when hold released.
  7. Complete the activity.
  8. As su, delete the policy hold:
    1. Select Administration > Business Settings > Policy Holds.
    2. Click the Code link for the policy hold.
    3. Click Delete.
  9. Type ALT+SHIFT+T. On the Batch Process Info screen, run the Policy Hold Job Evaluation batch process.
    Note: In PolicyCenter, the user interface uses the term policy transaction to refer to submissions, policy changes, and other policy transactions. Policy transactions are implemented as jobs in the data model, and referred to as jobs in PCF files, Gosu classes, and other configuration files. Therefore, the configuration documentation refers to policy transactions as jobs.

    The batch process reevaluates both renewal policy transactions, and puts them back into automated renewal processing. The automated renewal processing binds and issues the first renewal policy transaction. Because this policy was issued one year ago, it expired today and appears in Policy Terms on the Account File Summary screen as an expired term.

    The automated renewal processing quotes but does not bind or issue the second policy renewal policy transaction. The policy transaction appears under Pending Policy Transactions on the Account File Summary screen. The processing generates a Policy Hold released activity reminding the user to issue the renewal.