Skip to main content

Automatic Contract Agreement Document Generation

Updated

Introduction

Our system supports automatic contract agreement document generation that allows storing the generated document in the PGM member profile as well as in the Documents section on the Client Portal.

Before you start 

A company has ContractAgreemt RDLC file (/Pgm/#/Settings/ContractAgreementDocuments)

This feature is supported only for Contract Agreements. User Agreements are not supported. 

Instruction

Automatic document generation in PosWeb and PGM:

  • Settings AgreementDocuments.AutomaticGenerationWithoutSignature must be set to True.
  • This setting can be found here: PGM > System Settings > Customers > Agreement documents > Allows agreement documents generation during member creation.

Contract agreement document will be generated during user registration, contract upgrade, contract adding or cession. The document will be generated for ContractAgreement RDLC which has set language the same as the language currently selected in PGM or PosWeb. If there won’t be RDLC file with the selected language then the system will try to generate a document for the default RDLC.

Automatic document generation in ClientPortal2 

To have this function, the following requirements should be met:

  • A company has a Contract Agreement available on Cp2
  • (no applications marked at all or CP application selected in Applications filed) (Pgm/#/Settings/ContractAgreements)
  • Is client signature required checkbox is marked
  • Document type is User Agreement or Contract Cancel Form. It can not be empty.
  • An agreement could be required or not, even if the user didn't accept this agreement on CP2 during contract purchase, if the needed setting is on, a contract document still will be generated
    (applied to ClientPortal.Policy.AgreementSignatureProvider setting)
  •  Proper CP2 screens selected on Groups list

 

 

If all these conditions above were taken into account, we have the following options to generate/not generate Contract document:

  • Setting ClientPortal.Policy.AgreementSignatureProvider  value = None - no document generation (is default value)
  • Setting ClientPortal.Policy.AgreementSignatureProvider  value = Empty - contract document will be generated with empty sign (you need to select the option Empty, which is not the same as leaving the field with no value)
  • Setting ClientPortal.Policy.AgreementSignatureProvider  value = IP - user IP address will be used as a contract signature

Setting ClientPortal.Policy.AgreementSignatureProvider works in all CP2 modes (desktop, tablet, kiosk).

  • Settings ClientPortal.Feature.AgreementsSigning or ClientPortal.Kiosk.Feature.AgreementsSigning (for CP2 Kiosk mode) - possibility to sign an agreement in CP2 by mouse

 

The document will be generated only if a member will finish the whole registration process. It means if there will be payment required during registration then the member has to pay it otherwise process won't be successfully finished and the document won't be generated. You can change this behavior by setting ClientPortal.Contract.SignContractAgreementBeforePayment to True. In this configuration, a document will be generated before the payment regardless of the payment status.

Summary

The generated document is stored in the User documents section in the PGM member profile. 

Could be visible on the Cp2 Documents section as well as ClientPortal.Feature.UserDocuments feature is on. 

Related articles