A checklist to guide the planning of your BDK Book project, covering key requirements and considerations.
Ensure you have access to the following software requirements.
Designing a Book involves defining these procedures to ensure they align with the automation’s objectives. To guide this process, take into account the following considerations:
Identify the specific procedures needed for the Book. Each procedure should have a clear and specific automation purpose.
What actions does the user need to automate in Kognitos?
Can the actions be broken down into individual steps?
Consider these procedures for a Weather Book:
Get the current temperature in a specific city.
Check the current air quality index (AQI).
Determine delays or disruptions caused by severe weather for shipping and transportation.
Notify attendees of weather-related changes for events.
Clearly define each procedure's inputs, outputs, and processing steps.
What input or parameters are needed for each procedure?
What output or data should each procedure return upon completion?
How will data be transformed, manipulated, or processed in each procedure?
Consider an procedure that gets the temperature in a specific city:
Input
City name
Output
Temperature (°F)
Timestamp when the temperature was recorded
Processing Steps
Validate the city name.
Use an API request to get weather data for the specified city.
Parse the response to extract the temperature value and timestamp.
Format the temperature reading to the appropriate unit (Fahrenheit).
Consider common error scenarios and define how they will be handled.
What are the potential error scenarios that could occur?
How will these errors be handled and/or logged?
Consider the following error scenarios for a Weather Book:
1. Invalid Input
A user enters a non-existent city name (e.g., "Atlantis").
The system receives a blank input for the city name.
2. API Unavailability
The weather API is temporarily down or unreachable.
A network timeout occurs during an API call.
If you plan to integrate with an external API in your Book, it’s important to assess the target service's requirements, limitations, and authentication mechanisms. The following considerations will ensure your chosen API aligns with your automation needs and integrates seamlessly into your BDK project.
Understand the authentication requirements for your target integration. BDK supports standard API authentication methods, including API keys, OAuth 2.0, client credentials, etc.
Does the API require authentication? If so, what kind?
Are there specific permissions or roles required to access certain API endpoints?
Can you obtain the necessary access and permissions for all required credentials?
Identify which API endpoints will be used and define the data that will be exchanged.
Which API endpoints will your Book use?
What data will be sent or received?
Review the API’s rate limits and usage quotes. Ensure they can handle your expected request volume and check for additional costs or restrictions.
Are there API rate limits or usage quotes?
Does the API’s rate limit support the expected request volume for your workflows?
Are there additional costs or restrictions for exceeding usage limits?
Evaluate if the API documentation is clear and if provider support is accessible.
Is the API documentation comprehensive and easy to follow?
Does the API provider offer support?
Plan for future scalability and consider how the API will handle growing request needs.
Can the API handle increasing request volumes as workflows grow?
Does the API support additional functionality that might be required in future Books?
Prepare to deploy and manage a Docker container
Ensure the required infrastructure is in place to deploy a Docker container in the cloud, on-premises, or in a hybrid environment.
Plan strategies for:
Managing the container lifecycle, including scaling, networking, and security.
Implementing logging to track container activity
Monitoring container health and performance
Updating Docker images for new releases with clear versioning and testing practices.