IdStory Identity Manager

1. Only tasks with defined nextFireTime are listed
   • consequence: tasks without triggers or only dependent triggers are not listed (in the main list of tasks)
2. New field introduced to each task: dependentTasks
   • this new field contains list of tasks that are dependent on the task

• list of next fire times, limited by time (seconds from now) or count (total size)
  • whichever limit is lower will apply
• nextFireTimesLimitCount default value is 1
• nextFireTimesLimitSeconds default value is 1 day

• the main list only contains tasks with Cron or simple trigger (consequence of 1))
• each task contained in the main list is there only once (even when it is executed more than 1 time)
  • the information about multiple times of executions is in the triggers of the task

• It is not possible to say something like "I want all tasks that will be executed in next 24 hours"
  • the main list of tasks itself is unlimited - should I implement something like this?
  • it is only possible to limit cron triggers like that
• Since cron triggers received new field nextFireTimes which also contains nextFireTime as its first value, the field nextFireTime is redundant from the data perspective in most cases
  • I kept the field in there because it is used in a different way than nextFireTimes
    • The workaround would be too complicated if we wanted to get rid of the data redundancy IMO

Example response -> https://redmine.czechidm.com/attachments/download/1212
PR: https://github.com/bcvsolutions/CzechIdMng/pull/362

PR merged. Thanks