Configuration¶

This section describes how you configure Task Starter.

Lime admin config¶

If you want to be able to start a task as a diffirent user, select the correct user and press save. Feel free to change this user whenever you want, it only affects tasks started after the change.

impersonate-user

Application Config¶

You need to add all tasks that should be visible in lime-admin in the application-config file.

Application Config on-premise¶

Open the application config @ %ProgramData%\Lundalogik\LIME Pro Server\application_config.yaml.

Add the limepkg_task_starter section under config without breaking the format of the file if there are other configurations in that file.

Add tasks under tasks section, you can add them as all in one package/solution, all tasks from a task file or specefic tasks in a task file. The most common is to load all the tasks from your solution with - "solution_my_customer"

lisa_application_name:
    config:
        limepkg_task_starter:
            tasks:
                - "solution_my_customer"
                - "limepkg_another_package.tasks.example_tasks.dummy_task"
                - "limepkg_other_package.tasks.integration_tasks"

The option task_history is optional and states how many tasks runs that will be saved (result visible in lime admin), if you dont have this in the config the default value will be 10.

lisa_application_name:
    config:
        limepkg_task_starter:
            tasks:
                - "solution_my_customer"
                - "limepkg_another_package.tasks.example_tasks.dummy_task"
                - "limepkg_other_package.tasks.integration_tasks"
            task_history: 20

Application Config Cloud¶

Same as above but in cafe instead. Add limepkg_task_starter in the config window to the left in cafe.

Application Config Local development¶

If you don’t have the file application_config.yaml in the .lime folder in your solution, create the file first. Add the same info as for on-premise. Remember that lisa_application_name is always the limepkg/solution name when you develop with docker.