Revenue Forecasting Settings

Here is a description of the configuration options in the Revenue Forecasting configuration groupClosed A collection of configuration options contained in the configuration groups tab that defines behavior of a FinancialForce PSA object or feature..

Configuration Option Description

Default Value
forecast-scheduled-job-batch-size

A temporary configuration option you can set up that allows you to change the batch size of the RFP_EnqueuerBatch scheduled job, which

finds suitable projects and marks them as pending for Revenue Forecasting. For this configuration option to work, you must follow the instructions below precisely.

Warning:

We recommend you contact FinancialForce Support if you want to use this configuration option.

To set up this configuration option, take the following action:

  1. Create a new configuration group with the following attributes:
    • Configuration Group Name: Revenue Forecasting
    • Key: asm.revenue-forecasting
    • Version: 1
    • Description: This is a temporary configuration group that is not supported after Winter 2023. Contains configuration options related to Revenue Forecasting.
  2. Create a configuration option with the following attributes:
    • Name: forecast-scheduled-job-batch-size
    • Type: Number
    • Configuration Group: Revenue Forecasting
    • Version: 1
    • Description: This is a temporary configuration option that is not supported after Winter 2023. It allows you to change the batch size of the RFP_EnqueuerBatch scheduled job, which finds suitable projects and marks them as pending for Revenue Forecasting.
  3. Create a configuration value with the following attributes:
    • Configuration Option: forecast-scheduled-job-batch-size
    • Value: Enter your preferred value.
Note:

In Winter 2023, we plan to introduce a permanent solution for setting the batch size of the scheduled job that finds suitable projects and marks them as pending for Revenue Forecasting. This configuration option is intended to serve as a temporary workaround and is not supported after Winter 2023.

 200