Calendly policy
A Calendly policy contains the connection details that are used by a Calendly Request node when you connect to a Calendly application.
You can use a Calendly Request node in a message flow to connect IBM® App Connect Enterprise to Calendly applications and issue requests to create, retrieve, update, or delete objects such as event invitees, event types, events, and users. The Calendly policy controls, at run time, access to the Calendly application.
The Calendly policy is created when you configure a
connection between a Calendly Request node and Calendly by using the Connector Discovery wizard. During the
process of discovery, account credentials are stored in the vault and connection details are stored
in a Calendly policy. The policy is created with a type
of Calendly
, and the name of the policy is returned to the Calendly Request node and specified in the Connection tab of the
node, in the format
{policyProjectName}:policyName
.
You can also create, update, or delete a Calendly 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 a Calendly policy, all message flows that are using the policy are stopped and restarted.
For more information about using Calendly, see Using Calendly with IBM App Connect Enterprise.
Property | Property name in .policyxml file | Description of properties |
---|---|---|
Calendly Application Type | applicationType | This property is reserved for future use and must be set to the value
online . |
Calendly Application Version | applicationVersion | This property is reserved for future use and must be set to the value
v1 . |
Calendly Authentication method | authenticationMethod | This property specifies the type of authentication that is used for the
connection between IBM App Connect Enterprise and Calendly. This value is reserved for future use and can be
set to BASIC or BASIC_OAUTH . |
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. |