The following list provides information about the configurable properties defined in the config.json file. The config.json file contains several runtime parameters that must be defined by an administrator to work in live mode.
The default location for the configuration file is [drive:]\Program Files\Apache Software Foundation\[Tomcat Installation]\webapps\apapproval\packages\les-rdk-ap-invoiceapproval\src\config.
The configuration elements listed are in the order they appear within the config.json file.
dataProvider
This property defines the source from where the invoice data is retrieved and updated. Valid entries include the following elements.
- demoMode. The demo mode where Perceptive AP Invoice Approval App can perform all functionalities using a set of static data. You can set this value to true or false to toggle between demo and live modes, respectively.
- glAutoSaveIntervalInSeconds. Decides whether to save the modified invoice data after a certain time interval. You can define any integer value, which represents the automatic save frequency in seconds for modified GL data. “0” or any negative value turns the automatic save feature off.
- pcr. Perceptive Connect Runtime configuration with subelements named "approvalEndpointURL," "fpaServiceEndpointURL," "fpaServiceCachingEnabled," and "erp." The "approvalEndpointURL" subelement defines the URL for the Perceptive AP Invoice Approval Connector, which runs inside Perceptive Connect Runtime. Update the URL, replacing pcr_machine_name and pcr_port with the appropriate values for your Perceptive Connect Runtime environment. The "fpaServiceEndpointURL" subelement defines the URL for the FPA service, which runs inside Perceptive Connect Runtime. The "fpaServiceCachingEnabled" subelement defines whether data caching is applicable for data communication between the app and the FPA service. The "erp" subelement defines the ERP name based on which header and line field labels are displayed in the UI. Possible values include but are not limited to “Default,” “Dynamics AX,” “SAP,” “Oracle EBS,” “Infor Lawson,” and “PeopleSoft.” If you want to include a new ERP name then you must ensure that the corresponding label is present at the locales.json file.
userConfig
This property decides who to provide invoice data edit privileges. It contains a subelement named "glCoderGroupOperationPermission."
- glCoderGroupOperationPermission. Defines which permission is assigned for a group or a set of groups. Approvers belonging to these groups (in Perceptive Content) only have the privilege to view or edit invoice line item data as per the defined permissions. Supported privileges are: "viewOnly," "modifyOnly," and "fullEdit." Users who are not a member of any of the specified groups or users who are assigned any unsupported privileges enjoy "viewOnly" privilege by default. Users defined in multiple groups enjoy the highest assigned privilege. Users with "modifyOnly" permission can modify the invoice line item data, whereas users with "fullEdit" permission can additionally add or delete invoice line item data.