Performance monitoring on Processes hows that the processing power used to implement processes.

Proposed design:

1. Consolidate jobs so there are fewer calls to the database
2. We should not touch processes that are not due to run based on the next run date
3. Cleanup the "Company Administration ~> Process" form
   1. Place Template description and Process code in the Details field
   2. Add Process Group to consolidate jobs
   3. Default sort should be:  Module "SYS", followed by other modules

Proposed Design

1. Create a single group for processes so that we minimise the number of DB Calls
2. On each process, we add the duration of the last run. Users can use this to determine if processes should be seperated
3. The group name will be editble

PART A - Development work for this case has been completed.

1. The change will be available in version:12.30.1211

2. The following changes were made(Include Database object names, Program classes and any other relevant information):

1. Add a new field named: ProcessGroup to "Company Administration ~> Processes"
2. Process Groups allows processes to be grouped together. Having multiple process groups allows users to control how many parallel processes can run. Keep in mind that this will also add a processing load to your system.
3. LinkSOFT by default will have "Process Group" as Blank, therefore all processes will run under a single SQL Agent Job in a single thread
4. When a user enters a value in "Process Group", the LinkSOFT system will create a separate agent job using the "Process Group" Name.
5. Replication processes will have a separate "SQL Agent Job" with the name "Replication" at the end.
6. SQL Agent jobs will be added and deleted based on "Process Group" names
7. Process group names are not affected by the "Windows Process Service" as the Process service is single-threaded.
8. During the upgrade, all jobs will be deleted and a single job created named Link Technologies - {DatabaseName} - LinkADMIN

3. Affected Areas:

1. "Company Administration ~> Processes"

4. The issue was caused by:

1. Performance Improvement

5. Notes: Users should create a separate "Process Group" for processes that consistently take more than 5 seconds.
6. Next Step: UAT

----------------------

PART B - Development Reference:

1. Changes implemented was according to the approved design (Y/N): Yes

2. Variations to the approved design: Added column to show how long the last execution took, so users can create a separate group is a process that takes too long or for Urgent Processes, such as Replication.