Uploaded image for project: 'Camunda Optimize'
  1. Camunda Optimize
  2. OPT-5936

Include Optimize with Identity into Camunda getting started guide

    • Icon: Task Task
    • Resolution: Done
    • Icon: L3 - Default L3 - Default
    • 3.9.0, 3.9.0-alpha4
    • None
    • documentation
    • None
    • 2
    • Not defined
    • 3 - Expected

      Context

      I'm trying to market Optimize by saying it requires no additional setup and you can immediately get process insights. It's always there, collecting data for analysis. However, the "camunda-cloud-get-started/docker-compose.yaml" file doesn't include Optimize, nor does the "Setting up your first development process" instructions. In addition, describing "Setting up your first development process" only focuses on the development process. We should consider the entire process automation lifecycle in our getting started documentation.

      The desired user journey is as follows:

      1. Decide to automate the first process
      2. Download all necessary files in 1 step, including Optimize
      3. Easily set up Camunda applications
      4. Model the first process, create a user task form, and automate a service task
      5. Execute the process a few times
      6. View resulting data in Optimize

      Acceptance Criteria (Required on creation):

      • Include Optimize and Identity into camunda-cloud-get-started/docker-compose.yaml
      • Documentation communicates that the getting started process also includes analyzing their new process in Optimize
      • The Optimize section in the Getting Started part communicates the desired workflow, shown above

      Hints (Optional):

      • joshua.windels has volunteered to help with the docker-compose section
      • Retitling the "Integrating Optimize" section should be pushed to the public-facing branch

        This is the controller panel for Smart Panels app

            [OPT-5936] Include Optimize with Identity into Camunda getting started guide

            Within Cloud docs, I've clarified instructions in the set up portion of the Optimize guide itself. I also updated the Optimize guide I previously wrote up with some of the recent updates, and will add alerts information into the PR shortly.

            Additionally, I'm pulling in sebastian.menski regarding the get-started repo and docker-compose file as he owns this one. Given these instructions are for those working in self-managed, with docker running locally, is this the best experience for new Optimize users who may have limited process instances to work with? Is there a way to ease these "limited process instance" users into Optimize so they can see its potential? Just a few thoughts.

            Christina Ausley added a comment - Within Cloud docs, I've clarified instructions in the set up portion of the Optimize guide itself. I also updated the Optimize guide I previously wrote up with some of the recent updates, and will add alerts information into the PR shortly. Additionally, I'm pulling in sebastian.menski regarding the get-started repo and docker-compose file as he owns this one. Given these instructions are for those working in self-managed, with docker running locally, is this the best experience for new Optimize users who may have limited process instances to work with? Is there a way to ease these "limited process instance" users into Optimize so they can see its potential? Just a few thoughts.

              Unassigned Unassigned
              eric.lundberg Eric Lundberg
              Christina Ausley Christina Ausley
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: