Expensify policy
An Expensify policy contains the connection details that are used by an Expensify Request node when connecting to Expensify.
You can use an Expensify Request node in a message flow to connect IBM® App Connect Enterprise to Expensify and issue requests to update, create, retrieve, and download objects, including employees, expense rules, expenses, policies, and reports. The Expensify policy controls, at run time, access to the Expensify application.
The Expensify policy is created when you configure a
connection between an Expensify Request node and Expensifyb y using the Connector Discovery wizard. During
the process of discovery, account credentials are stored in the vault and connection details are
stored in an Expensify policy. The policy is created
with a type of Expensify, and the name of the policy is returned to the Expensify Request node and specified in the Connection tab of the
node, in the format
{policyProjectName}:policyName.
You can also create, update, or delete an Expensify policy by using the Manage Discovery Connector Policies and Credentials wizard, which you can access by right-clicking the policy project in the IBM App Connect Enterprise Toolkit and then clicking .
You must deploy this policy before message flows that use the policy are started. If you redeploy an Expensify policy, all message flows that are using the policy are stopped and restarted.
For more information about using Expensify policies, see Using Expensify with IBM App Connect Enterprise.
| Property | Property name in .policyxml file | Description of properties |
|---|---|---|
| Expensify Application type | applicationType | This property is reserved for future use and must be set to the value
online. |
| Expensify Application version | applicationVersion | This property is reserved for future use and must be set to the value
v1. |
| Expensify Authentication method | authenticationMethod | This property specifies the type of authentication that is used for the
connection between IBM App Connect Enterprise and Expensify. This property is reserved for future use and must
be set to the value BASIC. |
| Server URL | apiUrl | Select the URL for the API server that makes runtime calls. |
| Allow self-signed certificates | isTisEnabled | Set to true or false. Set to true if you want to be able to accept self-signed certificates that are trusted and used only in a nonproduction environment. The default is false. |
| Override server URL | endpointUrl | (Optional). Required if you want to connect to an endpoint in a private network by using the private network client, or if you want to override the server URL. Specify an override value for the host and port in the OpenAPI definition in the format <http or https>://<host_name>:<port>. If you are not using the private network client or do not require an override, leave this field blank to use the hostname and port in the OpenAPI definition. |
| Credential name | credentialName |
The specified credential can be defined during connector discovery and stored in the vault. Alternatively, you can specify an existing credential that was configured by using the mqsicredentials command or the server.conf.yaml file, or loaded through an external credential provider. |