Schedule Reporting Periods Flow


The Schedule Reporting Periods Flow customization process has been simplified from Indus (v1.31) and later releases. Contact your Vera POC for customization steps if your organization is using Fornax (v1.27).

The “Schedule Reporting Periods” flow enables users to create multiple Reporting Periods through a screen flow. It is active by default on installation, and since it is a template flow, it can be cloned and modified based on your organization’s requirements. It can also be deactivated if it is not required. 

A system administrator can clone the flow and modify the naming convention if required. Follow the steps below to complete this:  

  1. Click on the gear icon in the top right corner and click on Setup.

  2. Search for “Flows” in the “Quick Find” box, click on it, and then click on the “Schedule Reporting Periods” flow label.

  3. Once the flow loads in a new tab, clone it to allow for editability. For additional directions on how to clone a flow, please refer to the Cloning a Flow section below. 

  4. Navigate to the “Manager” section of the interface, found on the left-hand side.

  5. Save your flow and Activate. Ensure the Amp Impact managed flow (API name: ampi__Schedule_Reporting_Periods) has been deactivated. 

  6. The next step is to enable an on-screen “Quick Action” button for the user to activate the flow. Navigate to the object you wish to add the button to via the Object Manager.

  7. Locate the “Buttons, Links and Actions” option in the left navigation bar and select “New Action”.

  8. To create a “New Action”, select “Action Type” as “Flow” in the screen that appears, and then populate the displayed fields, including the selection of the newly cloned flow name in the “Flow” picklist.

  9. Add the Action to the relevant page layout of the object where you wish to display the button by dragging it into the page layout as shown below. Click “Save” and assign the page layout to pertinent profiles.

To translate or change the static text in the duplicate Header resource of the flow, override using translation workbench, or clone the templated flow and edit the resource or add in their own custom label.