Now, I’ve made this Cycle. I’m happy with it, I’ve made this template. And I’m happy with it, I can go into the settings here. I can look at changing whether we retry the individual call, if an error is encountered, whether we stop the integration or we stop the transaction, I can also lock my requests. So that allows me to see what is being sent out from Cyclr, as well as what is being returned, I can choose the shedule, or the scheduling of this cycle running. So I can choose to run this cycle every X number of hours or days or weeks.
For this I’ll just put it as one every hour, and then collection splitting, which we’ve already covered.
Now, for each cycle, I can set up variables. And these variables can be set up by the user during the auth process.
If it’s information that’s required across multiple fields, you can just put the variable in place of leaving the field user configurable, and it will take that variable option and push it into the customers field or push it into the Cycle so that the customer can then run the Cycle with their customizations and do not have to worry about them setting up the same information multiple numbers of times.
Data retention. By default, it’s set to 31 days, we understand that some people may work with sensitive information that can’t be on the platform for that long. So it gives you the option on a per cycle basis to determine how long information stays on the platform, whether it’s successful transactions or error transactions.
The audit log, now this shows you integration events and the user that has either triggered them or cause them to happen. So in this instance, you can see both times I activated the connector, deactivated and stopped isn’t associated with anyone. And that’s because the one time transaction has completed as it explains in the comment, and it gives you a timestamp. And if you hover over it, it gives you the UTC timestamp as well. So you can see when an action has happened or occurred.
And finally the connector installation. So when the connector is published, and it’s facing the API, if a customer is looking to install this template into their account, you have the option of choosing whether it uses an existing installation of Salesforce for that customer and existing installation of Google Sheets for that customer, or if each time the templates, and so it takes a fresh instance of that connector.
So for something like Klaviyo, which has a different API key for each shop, and users can have many shops, you would want to choose a fresh installation.
For something like Salesforce where users are typically only using their information. In that scenario, you would use the existing installation.