Some aspects of FinancialForce PSA are controlled by custom settings. From Setup, click Develop | Custom Settings. You must be signed in with System Administrator permissions to perform these tasks. See the Salesforce Help for information on how to maintain custom settings.
You can control the PSA ERP integration behavior using the ERP PSA Messaging Settings custom setting.
These fields are used to control aspects of both the FinancialForce HCM to PSA integration and the PSA Assignment API feature.
Key: * – Mandatory field.
| Field | Description | |
|---|---|---|
|
|
The field that filters HCM Absence Request messages used to create PSA Assignments, Schedules, Schedule Exceptions, and Timecards. If your organization uses a Worker Filter, this value must be a formula that includes the Worker Filter logic defined in the field used in the Worker Filter Field Key setting. If the key value is a field on a related object (via a lookup), add a lookup node to the message and include the field from the lookup. Set this field value as lookup:key. For example, if you have an absenceType Lookup containing an absenceTypeName key, the value is: absenceType:absenceTypeName. The key that filters third-party HCM time off requests used to create PSA Assignments, Schedules, Schedule Exceptions, and Timecards. Example: |
|
| Absence Filter Values | The message key values used to filter HCM Absence Request messages and PSA Assignment API time off requests. If the value contains multiple text or picklist fields, separate the list with semicolons. |
|
| Absence Request Project | * |
The Salesforce record ID to use when creating Assignments from Absence Requests through ERP. Declarative mappings override this field setting when using the FinancialForceHCM to PSA integration. |
| Field | Description | |
|---|---|---|
| Worker Filter Field Key |
The fields that filter designated HCM Workers that are used in ERP to create PSA Resources. Separate the list with semicolons when the key uses multiple values, such as multiple picklists, separate the list with semicolons. ERP applies an "OR" condition to each value (for example, picklist1 or picklist2). If the key value is a field on a related object (via a lookup), add lookup node to the message as a Map field and include the field from the lookup as a field within the Map. Set this field value as lookup:key. For example, if you have a position Lookup containing a name key, the value is position:name. |
|
| Worker Account Filter Field Key |
The fields that filter designated HCM Workers that are used in ERP to create PSA Resources based off of Accounts (Salesforce Person Accounts). Separate the list with semicolons when the key uses multiple values, such as multiple picklists, separate the list with semicolons. ERP applies an "OR" condition to each value (for example, picklist1 or picklist2). If the key value is a field on a related object (via a lookup), add lookup field to the message as a Map field and include the field from the lookup as a field within the Map. Set this field value as lookup:key. For example, if you have a position Lookup containing a name key, the value is position:name. |
|
| Worker Filter Values | The message key values used to filter HCM Worker messages. If the value contains multiple text or picklist fields, separate the list with semicolons. | |
| Worker Account Filter Values | The message key values used to filter HCM Worker messages for PSA Resources based off of Accounts. If the value contains multiple text or picklist fields, separate the list with semicolons. |
You can use the following settings to control how you want PSA to manage records that third-parties create and update via the Resource API.
You can use the following settings to control how you want PSA to manage records that third-parties create and update via the Assignment API.
Some fields in the PSA Assignment from HCM Absence Request Settings section also control some aspects of the PSA Assignment API feature:
For more information about these fields, see PSA Assignment from HCM Absence Request Settings.