Setting Up ProcureSight Enterprise

The ProcureSight Enterprise (PSE) solution is as flexible as any application developed on the Appian Platform. To make sure your solution remains scalable and aligns with best practices, we have provided instructions to guide you through some of the most common changes.

After you have installed PSE, there are several configurations you will likely perform to customize the solution for your organization’s data, including:

• Configuring user groups and security
• Configuring records for Smart Search and Document Search
• Configuring relationships to Workspace and Collection records
• Configuring the Semantic Search record rule
• Performing optional configurations

This page outlines the order we recommend for configuring the default solution to work for your organization. However, all of these instructions can be used to modify the solution at any time. In addition, these steps utilize a sample Solution record that is included with your PSE solution as an example.

Step 1: Configure user groups and security

The first step to configure your PSE solution is to setup user groups.

You will need to know:

• If your organization has any additional business roles that are not covered in the default business groups:
  • AS PD Users
  • AS PD Administrators
• What users should be members of each business group.

For more information on groups and security, see Groups Management.

Step 2: Configure records for Smart Search

To be compatible with semantic search in your PSE solution, you need to configure your records with Smart Search by selecting specific record fields and document fields to use with Smart Search enabled.

For example, here we can see the Solution record type is configured with Smart Search on the Title and Description record fields.

Configure Document Search

As part of PSE, semantic search can parse through the contents of your documents when configured for your solution.

To enable semantic search on your documents, you need to save documents to the record specific folder so they can be stored on the record. Next, you need to select the related document fields for smart search and update the configuration rule to reflect the selected document fields.

See Document Record Type and Manage Documents with Record Types for more information about how to create and configure the Document Record Type to use with semantic search.

Step 3: Configure relationships to Workspace and Collection records

My Workspace and Collections are PSE features that will help you organize and analyze your record data. To ensure that your data displays more granularly with these features in PD, you will optionally want to add record relationships with your records to AS_PD_WorkspaceEntityMap_RecordType and AS_PD_CollectionEntityMap_RecordType.

Create a relationship between your record and the following record types: AS_PD_WorkspaceEntityMap_RecordType and AS_PD_CollectionEntityMap_RecordType.

Step 4: Configure the Semantic Search record rule

To set up the AS_PD_CONFIG_recordTypesForSemanticSearch expression rule, you first need to install the Solutions Hub. See Solutions Hub Installation Guide to get started.

After the Solutions Hub is installed, navigate to the Solutions Hub site to modify the AS_PD_CONFIG_recordTypesForSemanticSearch configuration rule. Follow the commented instructions in the expression rule to reference your records for search and display.

Step 5: Configure data for filters

When setting up single or multiple dropdown filters in the AS_PD_CONFIG_recordTypesForSemanticSearch rule, you have two choices for where the filter options come from:

1. Transactional Records: You can pull options directly from your main transactional table. If you do this, the dropdown will automatically display all unique values from that field, sorted alphabetically.
2. Reference Data Records: If you prefer to use dedicated reference data, keep these best practices in mind to ensure the filter options populate correctly:
   • Filter for Active status: Always apply a sync filter to your reference record so that users only see active values in the dropdown.
   • Organize your data clearly: You can either maintain one separate table for each data type or use a single shared table for multiple types. If you use a shared table, create a separate Appian record for each specific category and use a sync filter to isolate the relevant data.
   • Custom Sorting: If you want the dropdown to follow a specific order (using the refDataSortOrder parameter), you must you reference data records (not the transactional table).

Perform optional configurations

In addition to the required set up steps, you can extend your PSE solution by integrating ProcureSight Plus (PS+) to enable your team to seamlessly search public data sources of past procurements, vendors, protests, codes and Multiple Award Schedule (MAS) without leaving the PSE solution.

Additionally, the Solutions Hub allows you to customize your PSE solution to meet the specific needs of your organization, including the AI Document Builder.

This section provides guidance on integrating PS+ and customizing your PSE solution by configuring the AI Document Builder Record Context rule.

Integrating ProcureSight Plus

Integrating PS+ with your PSE solution transforms into a comprehensive procurement intelligence platform. This enhancement enables strategic and more informed decision-making through the utilization of both public and internal data sources.

To install the ProcureSight Plus (PS+) and integrate it with your PSE solution, follow the steps in Installing PS+.

Configure the AI Document Builder Record Context rule

Follow the steps in this section to set up the configuration rule for AI Document Builder Record Context configuration in the Solutions Hub for your PSE solution.

To configure the configuration rule:

1. In the Solutions Hub site, click the Edit button for Document Builder Record Context Configuration.
2. In the AS_PD_CONFIG_recordContextSearchSelect configuration rule, follow the commented instructions to reference your records as context for the AI Document Builder.

Next Steps

To get started immediately using your PSE solution, follow the steps in Accelerating PSE to preload sample data in your application.

Feedback