--- schema_version: "1" id: cfdfea5ef8bea0bb8542e94c4a18a8adb45a5a1ac0f62e27ae1bcadff4dff397 title: Set Up Funding Workbench for Users collection: admin version: current locale: en-us portal_url: https://docs.salesforce.com/admin/current/en-us/ind/264-0-0/auto_finance_funding_workbench_setup_for_admins.md canonical_url: https://help.salesforce.com/s/articleView?id=ind.auto_finance_funding_workbench_setup_for_admins.htm&release=264.0.0&type=5 source_site: help.salesforce.com content_type: documentation content_hash: 8030ef8a0ca3f7d497fb50e2a1ad23c0c68827529d7b968cadc9fe7530a05cde description: Set up components for enabling and accessing the capabilities of Funding Workbench for your financial managers and funding analyst users. products: - Automotive release: "264" --- # Set Up Funding Workbench for Users Set up components for enabling and accessing the capabilities of Funding Workbench for your financial managers and funding analyst users. ### Required Editions
Available in: Lightning Experience
Available in: Enterprise, Unlimited, and Developer Editions.
## Permissions and Features - Before you enable the features as an admin, make sure you have the Automotive Foundation User permission set assigned to yourself and you have the System Administrator profile. Clone the Vehicle and Asset Lending permission set, select the 'Digital Lending Admin User' and assign it to yourself. 1. Enable the Funding Workbench feature. See [Enable Features for Vehicle and Asset Lending](https://help.salesforce.com/s/articleView?id=ind.auto_finance_lending_setupprerequisites.htm&type=5&language=en_US). 2. Assign the required permissions to your users, such as financial managers who need to set up the Funding Workbench Console for funding analysts and dealers, and funding analysts. See [Permissions for Vehicle and Asset Lending](https://help.salesforce.com/s/articleView?id=ind.auto_finance_lending_setup_permissions.htm&type=5&language=en_US). ## Define Document Structures 1. Create document categories. 1. From Setup, in the Quick Find box, enter Document Category, and then select **Document Category**. 2. Click **New Document Category**. 3. Enter a label for the document category. For example, Proof of Address. 4. The API name is automatically filled based on the label and can be customized. Make sure that each document category has a unique API name. 5. Enter a description for the document category. 6. Save your changes. 7. Repeat the steps to create other categories. 2. Create document types. 1. From Setup, in the Quick Find box, enter Document Type, and then select **Document Type**. 2. Click **New Document Type**. 3. Enter a label for the document type. For example, National Identity Card. 4. The API name is automatically filled based on the label and can be customized. Make sure that each document category has a unique API name. 5. Make sure that the **Is Active** checkbox is selected. 6. Enter a description for the document type. 7. Save your changes. 8. Repeat the steps to create other types. 3. Create Document Category Document Types to link Document Types to Document Categories and establish relationships. 1. From Setup, in the Quick Find box, enter Document Category, and then select **Document Category Document Type**. 2. Click **New Document Category Document Type**. 3. Enter a label. The API name is automatically filled based on the label and can be customized. 4. Enter a Document Category. 5. Enter a Document Type to link it to. 6. Save your changes. ## Customize Document Decision Requirements 1. Create custom fields on the Document Decision Requirement object to define conditions for uploading documents. For example, Product ID or Account ID. See [Create Custom Fields](https://help.salesforce.com/s/articleView?id=platform.adding_fields.htm&type=5&language=en_US). 2. Similarly, create a custom field on the Document Decision Requirement object to associate Application Action Items with specific Document Category and Document Type. For example, Task Name. See [Create Custom Fields](https://help.salesforce.com/s/articleView?id=platform.adding_fields.htm&type=5&language=en_US). 3. Create Document Decision Requirement records. For example, for the Acme account, a NeoGen product would require a document category of Income Proof or a Document Type of Joining Letter. 1. From App Launcher, search for and select Document Decision Requirements. 2. Click **New**. 3. Enter a name. 4. Enter a document category or a document type. 5. Select a product and the relevant account. 6. Select a task name. 7. Enter other details as required. 8. Save your changes. ### Create Decision Tables 1. From the App Launcher, find and select **Lookup Tables**. 2. Click **New**. 3. Select **Decision Table**, and then click **Next**. 4. Enter a name. The API name is automatically filled based on the name and can be customized. 5. For Decision Table Type, select **Advanced**. 6. Click **Create Decision Table**. 7. Click **Save & Next**. 8. Select **Salesforce Object** as the source. 9. For Source Object, select **Document Decision Requirement**. 10. For Source Object Fields, select the custom fields created in step 1 of the Customize Document Decision Requirements section above. 11. Select condition type as **All conditions are met (AND)**. 12. For Source Object Field, select **DocumentReferenceObjectId** in the Results section. 13. Click **Save & Next**. 14. For Filter Result by, select **Output Order**. 15. Click **Save & Next**. 16. Preview the decision table and click **Finish**. 17. Activate the decision table. 18. Similarly, create another decision table to determine the tasks assigned to users, with the same steps but for the source object fields, select the custom field created in step 2 of the Customize Document Decision Requirements section above. ### Update the Create Review Tasks for Lending Flow 1. From Setup, search for and select **Flows**. 2. Select **Create Review Tasks for Lending**. 3. Click **Save as New Version**. 4. In the new version, for the Initialize Action Item Owner Variables assignment element, for the OwnerPlaceholder variable, select the Value as the user to whom the action item is to be assigned. Alternatively, you can create a custom decision table to dynamically determine the user based on the task name. 5. After the Create application Action Item step, add an Action element. 6. For the action, select the decision table created in the previous section. 7. Under Set Input Values, select Included for the custom field created in step 2 of the Customize Document Decision Requirements section, such as Task Name. 8. Select the value for the field as Fulfillment Step Name from Get Fulfillment Step. 9. In the Initialize Document Decision Requirement Collection assignment element, enter the value of the Document Decisions Requirements variable as the outcome list of your decision table from the action element added in the previous step. ### Update Integration Procedure 1. From the App Launcher, find and select **Integration Procedures**. 2. Open **FundingWorkbench\_GetDocumentListData**. 3. From the dropdown, click **Create Version**. 4. Modify the input parameters of the FetchAccountAndProductFromAFP data mapper to fetch the necessary fields for your Decision Table as required. 5. In the setDTInput step, click **Edit as JSON**, and enter the required field values to provide the correct input to the first Decision Table created in the Create Decision Tables section. 6. In the FetchValuesFromDT step, update the Decision Table ID to link to the Decision Table created in the section above. 7. Save your changes. 8. Activate the version. ### Set Up Stage Management 1. Set up stage picklist values. 1. From Setup, go to Object Manager. 2. Select **Application Form Product**. 3. Select **Fields and Relationships**. 4. Select **Stage**. 5. Under Stage Picklist Values, click **New**. 6. Enter these values and save your changes. - Funding Approved - Contract Submitted - Contract In Review - Funding Rejected 2. Enable Paths. 1. In Setup, search for and select **Path Settings**. 2. Click **Enable**. 3. Click **New Path**. 4. Enter a name and API name. 5. For object, select **Application Form Product**. 6. For picklist, select **Stage**. 7. Click **Next**. 8. Click **Next** again. 9. Select **Activate Your Path**. 10. Click **Finish**. 3. Create stage definitions. 1. In Setup, search for and select **Stage Definitions**. 2. Click **New**. 3. Select **New** and click **Next**. 4. Enter a name and API name. 5. For reference object, select **Application Form Product**. 6. For reference object field, select **Stage**. 7. Save your changes. 8. In the new stage definitions, from the stages select **Signature Complete**. 9. Click **+Add Stage Transition**. 10. For transition to, select **Contract Submitted**. 11. Click **Add**. 12. Click **Add Stage Transition Rules**. 13. Select **Add Step Definitions** and click **Add**. 14. Click **Add**. 15. Enter a name and API name. Make sure this name matches the task name defined in your decision table. 16. For step type, select **Autolaunched Flow**. 17. For flow definition name, select the version of the Create Review Tasks for Lending flow that you created in the previous section. 4. Create stage definition assignments. 1. In Setup, search for and select **Stage Definitions**. 2. Click **Stage Definition Assignments**. 3. Click **New**. 4. Enter a name and API name. 5. For stage definition, select the stage definition you created in the previous step. 6. Save your changes. 7. From the dropdown, select **Activate**. 5. Optionally, create a record-triggered flow to automatically trigger stage management when an action item is marked as completed. 1. In Setup, search for and select **Flows**. 2. Click **New**. 3. Select **Record-Trigerred Flow**. 4. For object, select **Application Action Item**. 5. For Configure Trigger, select **A record is updated**. 6. For Condition Requirements, select **All Conditions Are Met (AND)**. 7. For the conditions, select the field as **Type**, operator as **Equals**, and value as **Upload**. Make sure the picklist value for Upload is configured for the Type field on the Application Action Item object. 8. Add a condition, select the field as **Status**, operator as **Equals**, and value as **Closed**. 9. Add an Update Records element. 10. Enter a name and API name. 11. For How to Find Records to Update and Set Their Values, select **Specify conditions to identify records, and set fields individually**. 12. For object, select **Application Form Product**. 13. For the conditions, select the field as Application Form Product ID, operator as Equals, and Value as the Related Record ID of the triggering Application Action Item. 14. Under Set Field Values for the Application Form Product Records, select the field as **Stage** and the value as **Contract Submitted**. 15. Save your flow and enter a flow label and API name. 16. Activate your flow. ### Enable the Chatter Component 1. In Setup, search for and select **Feed Tracking**. 2. Select the **Application Form Product** object. 3. Select **Enable Feed Tracking**. 4. Select the fields you want to track. For example, Stage. 5. Save your changes. 6. From the App Launcher, search for and select **Funding Workbench**. 7. From the navigation menu, select **Application Form Products** and open a record. 8. From the Setup menu, select **Edit Page**. 9. From the components panel, drag and drop the chatter component onto the page. 10. Save and activate your changes. ### Set Up the Timelines Component 1. Set up a timeline configuration to view the order of interactions for an application form product. See [Set Up a Timeline in Salesforce](https://help.salesforce.com/s/articleView?id=ind.timeline_client_information.htm&type=5&language=en_US). 2. Edit the application form product record page to configure your timeline for the funding workbench console. See [Add Timeline to a Record Page](https://help.salesforce.com/s/articleView?id=ind.timeline_salesforce_users.htm&type=5&language=en_US). ### Set Up an Approval Workflow Create an approval process for contract funding as per your requirements. See [Create Approval Processes](https://help.salesforce.com/s/articleView?id=sfdo.ofm_create_approval_processes.htm&type=5&language=en_US).