Skip to main content

Solutions Studio

Getting around in the Solutions Studio

The 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 individual flows for their end-to-end process.

The Solutions Studio is built around the philosophy of enabling 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.

By default, the Solutions Studio displays the solution Overview and Business Outcome sections, which help keep your team aligned and moving in the right direction as they build and update the solution. In the Process panel on the left, you can access the solution sections, which contain your modules, and the workspace app pages. On the right side of the screen are a visualization of your overall business process in the Process Mapping section and highlights of the important people for this particular solution.

Solutions Studio Common Elements

solutions_studio_anatomy.png
  1. Solution name - A descriptive name for the solution that encompasses all of its parts.

  2. Flow - The solution modules, categorized into one or more sections that help organize your most complex processes for easy readability. Each section contains related modules that are dedicated to a different aspect of the overall solution. Select Flow or a solution section to view and open the modules in that section.

  3. Workspace App - The workspace app, separated into pages. The workspace app is a user experience for the solution, comprised of one or more pages that provide direct access to relevant solution information or important module actions. Select Workspace App or a workspace app page to access and edit a page.

  4. Solution Overview - 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.

  5. 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.

  6. 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.

  7. Makers - The users that build and maintain solution modules, as opposed to process contributors, who play an important role in the business process but do not have access to the module builder.

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

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

  10. Profile icon - Select this icon to view and update settings, invite users to your board, and access help and documentation.

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.

solutions_studio_module_anatomy.png
  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.