Details

    • Type: Task
    • Status: Done
    • Priority: L3 - Default
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 2.2.0-alpha1, 2.2.0
    • Component/s: frontend
    • Labels:
      None

      Description

      We currently only have the data we import from the invoice demo process. We should add some more demo data in the dev environment to enable manual testing for different scenarios

        Activity

        Hide
        johannes.heinemann Johannes Heinemann added a comment -

        As an addendum to Sebastians, because I was just using the front-end dev environment:

        • please add a date variable, so we can test if date variables are imported and can be displayed in the front-end
        Show
        johannes.heinemann Johannes Heinemann added a comment - As an addendum to Sebastians, because I was just using the front-end dev environment: please add a date variable, so we can test if date variables are imported and can be displayed in the front-end
        Hide
        sebastian.stamm Sebastian Stamm added a comment -
        • the directory of the engine is dynamically constructed based on the configuration in the ./config.js file. So something like const bpmPlatformXmlDir = path.resolve(tmpDir, 'engine_8050/server/apache-tomcat-8.0.47/conf/bpm-platform.xml'); will break when the port is changed in the config.js
        • also, the tomcat version should not be hardcoded. Check line 77 for an example of an alternative way to find a file path
        Show
        sebastian.stamm Sebastian Stamm added a comment - the directory of the engine is dynamically constructed based on the configuration in the ./config.js file. So something like const bpmPlatformXmlDir = path.resolve(tmpDir, 'engine_8050/server/apache-tomcat-8.0.47/conf/bpm-platform.xml'); will break when the port is changed in the config.js also, the tomcat version should not be hardcoded. Check line 77 for an example of an alternative way to find a file path
        Hide
        sebastian.stamm Sebastian Stamm added a comment -
        • the dataPreparationPlugin variable could be constructed using a template string to avoid explicit \n and whitespaces
        • data.split('<plugins>') could be precalculated
        • the flow node ids could be more descriptive
        Show
        sebastian.stamm Sebastian Stamm added a comment - the dataPreparationPlugin variable could be constructed using a template string to avoid explicit \n and whitespaces data.split('<plugins>') could be precalculated the flow node ids could be more descriptive

          People

          • Assignee:
            Unassigned
            Reporter:
            sebastian.stamm Sebastian Stamm
          • Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: