BPM General Configuration

Note: If you are interested in using BPM and you do not have this feature yet, please submit an extranet case or contact your ClientSpace representative. The use of BPM requires an App Settings permission that can only be enabled by a ClientSpace representative.

General configuration for BPM consists of:

  • BPM Site Configuration

  • BPM Business Rules

  • BPM Entity-Based Role Permissions Assignment

Also refer to the BPM Workspace and Batch-Related Configuration article for workspace-related and Benefits Batch-related configuration topics.

BPM Site Configuration

Before you start using BPM, configure the BPM Welcome and Login pages to make them your own. This is where you can:

  • Add a custom portal name.

  • Add additional login instructions.

  • Edit "welcome text.

  • Add your company logo.

This page also contains a field named Do Not Show on BPM . This multi-lookup field allows you to always hide one or more of the following plans in BPM if you do not offer them: HSA, FSA, Commuter Plan.

See BPM Site Configuration for details.

BPM Business Rules

Most BPM business rules are pre-configured for you.

Two BPM business rules are used to automatically set the value in the Open to BPM field to Yes or No on a Benefits Batch. When the Status of the Benefits Batch is set to Client Review, Open to BPM is set to Yes and your customer receives an email notification that benefits are ready to review.

Another preconfigured business rule, Reject OBPs, is a Save operation rule that uses the BPM pipeline and the BPMSubmit Header Action(HdrAction). It is use to manage rejected OBPs. The BPMSubmit HdrAction one of the six HdrAction triggers that you can use to create additional Save operation business rules in BPM. The HdrAction rules are covered in the topic referenced below.

See Configuring BPM Business Rules for details.

Internal BPM Entity Role Permissions Assignments

Internal BPM access permissions are controlled by View, Edit, or Admin access to the BPM_Access entity assigned on the Benefits_Member role. View, Edit, and Admin access all currently work the same for the BPM_Access entity. These access permissions make the Internal BPM Access link available and functional on a Benefits Batch where Open to BPM = Yes. By default, the BPM_Access entity is added to the Benefits_Member role with View permissions enabled. Removing the entity hides the Internal BPM Access link.

See Internal BPM Access Permissions.

Topics in this chapter