Skip to main content

Solutions Studio

Getting around in the Solutions Studio

Solutions Studio is where the business process solutions, and the modules they contain, are created and maintained. It includes the graphical no-code interface where makers create the individual flows for their end-to-end process. The solutions studio is built around the philosophy of enabling the business experts to define and maintain business logic without needing to concern themselves with technical nuances around programming syntax, constructs, or best practices. Instead, Tonkean abstracts these away and handles many of them automatically.

The solutions studio interface includes the different environments needed for development (build) and production. These different environments simplify the build, testing, and deployment into production since the applications and data that are connected using enterprise components are associated with their respective environments. This ensures that the correct relationships are always maintained and connected without requiring human intervention, helping to prevent possible errors.

Solutions Studio Common Elements

  1. Solution name - A detailed, descriptive name for the solution.

  2. Business Outcome - The target business outcome for the solution—that is, what the solution aims to accomplish and how the solution helps the organization. The best practice for this section is include the key performance indicators and metrics you want to improve with the solution. Writing the business outcome is an important part of the solution creation process.

  3. Solution Description - The high-level description of the solution, potentially including the general workflow and the applications or systems used. Writing this description is an important part of the solution creation process.

  4. Process Owners - The users that own the business process contained with the solution. Process owners are specific to your business process and do not have unique permissions or privileges in Tonkean.

  5. Process Mapping - One or more process maps for your solution. Process maps are visual representations of your process, including the various teams and stakeholders, as well as the relationship between them.

  6. Solution Outline - The overall structure of your solution, including the solution sections that contain related modules or modules that represent a particular phase of a larger process.

  7. Solution section - A portion of the solution, containing related modules or modules that comprise a particular phase of a larger process. The solution sections help organize your most complex processes for easy readability.

  8. Process participants - The user personas that play a role in the process. For example, a new employee onboarding process might have "New Employee" and "HR Rep" as process participants.

  9. Module tile - A module contains the custom logic and workflow that orchestrates a business process.

  10. Versions button - View the history of versions for the solution.

  11. Publish Version button - Select this button to publish the most recent version of the solution, moving it from Build to Production.

Module Builder Common Elements

The module builder screen is where you'll spend most of your time in Tonkean. It reads left to right, much like a flowchart. This structure reflects the multiple conditions and paths (or branches) that many business processes have, allowing you to quickly visualize and understand the overall flow and relationships. However, it's important to understand that modules are not static decision trees; they are state-based, always monitoring the input source and responding in real time.

  1. Tool tabs - These tabs provide access to the main elements needed to build a workflow in the module builder, such as fields, items, and forms.

  2. Input data source - The data source the module is monitoring.

  3. Items - A representation of the items moving through the module workflow.

  4. Workflow - The business logic that defines the process, including all the relevant actions and triggers.

  5. Trigger - A "when" statement that defines when an action occurs.

  6. Action - A piece of logic or behavior, represented as an action block.

  7. Environment picker - Select either Build or Production environments.