1.5.0

Release Notes for Version 1.5.0

New Features

• Added a new option to usage data for "QUERY_TIMEOUT_IN_SECONDS", which provides a user defined timeout to the task collection query, in case the default of 3600 is not good.

1.4.0

Release Notes for Version 1.4.0

Fixes

• Fixed an issue where after an upgrade of OpCon, if running usage data locally (not connecting to the cloud for information), then 'core tasks' were not identified and showed a count of zero because the JSON file that lists the default core tasks got deleted during the upgrade. Now, we maintain a default list in the utility, so if the file is missing, we still can publish core task counts from the default list.

1.3.0

Release Notes for Version 1.3.0

New Features

• The task collection job is set to 'Do Not Schedule' when setup is complete. This allows users to configure it as needed before setting it to build in a released status.

Fixes

• Fixed an issue in the cloud application where customers that are east of UTC sometimes saw their task counts counted
  twice for a given day making the reporting on their daily tasks incorrect. NOTE: This fix was published as part of
  this release 1.3.0, but it will work even for previous versions of the application as the actual fix is in the cloud
  function.

• Fixed an issue where task collection application would fail for some European and other customers due to the date format
  used when collecting tasks.

1.2.0

Release Notes for Version 1.2.0

Fixes

• Fixed an issue where task collection would skip a day every alternate day of collection.

1.1.0

Release Notes for Version 1.1.0

Fixes

• Fixed an issue where an OpCon user assigned to a role with "inherit all schedules" privilege was unable to see the new task collection schedule.

1.0.0

Release Notes for Version 1.0.0

New Features

• Create a task collection application that when run from the command line without parameters, configures itself by creating an OpCon schedule/job that runs each day and produces a simple job output with the total count of tasks run each day.
• Allows the task count job to publish tasks data to a local JSON file in the application's "ProgramData" directory, which includes counts by day and by department and platform per day.
• The task count application is able to collect data only from the time since the job was last run, so it fetches less data and is hence better performing.
• Allow posting the task counts to the Azure cloud, so it can provide a better view of the tasks run each day/month at customer OpCon environments.
• The task count application is now able to self-update to the latest version from the hosting location.