Difference between revisions of "SmartHCM Notification Sender Utility Release Notes 1.0.0.0"
Bilal.saeed (talk | contribs) |
Bilal.saeed (talk | contribs) |
||
| Line 1: | Line 1: | ||
== SmartHCM Notification Sender Utility 1.0.0.0 Release == | == SmartHCM Notification Sender Utility 1.0.0.0 Release == | ||
| − | <u>'''Release Date'''</u>: | + | <u>'''Release Date'''</u>: 22-Apr-2020 |
<u>'''Module Version'''</u>: 1.0.0.0 | <u>'''Module Version'''</u>: 1.0.0.0 | ||
| − | <u>'''Maturity Status'''</u>: | + | <u>'''Maturity Status'''</u>: Cancelled |
== Compatibility == | == Compatibility == | ||
| Line 26: | Line 26: | ||
* <u>'''General Work - General Work'''</u>: A new application has been created to send "Email / SMS" notifications against all the "System Date" (Custom Date, Retirement Date, Probation End Date, etc.) and "Late Attendance" notification types. | * <u>'''General Work - General Work'''</u>: A new application has been created to send "Email / SMS" notifications against all the "System Date" (Custom Date, Retirement Date, Probation End Date, etc.) and "Late Attendance" notification types. | ||
| − | + | Users can set multiple "DB Connections Strings" in it means by using this application users can send notifications at the same time against multiple clients. | |
| − | + | A single toggle button is available to "Start/Stop" the service. | |
| − | Also, | + | Also, a "Log" button is used to view the log of the "Successful/Unsuccessful" service run. |
| − | Also, | + | Also, a "Delete" button is used to delete the "DB Connection" record from the utility. |
| − | Also, there is a separate "Enable All / Disable All" check box which is used to enable / disable at the same time all the "DB Connection" records. Also, each record | + | Also, there is a separate "Enable All / Disable All" check box which is used to enable/disable at the same time all the "DB Connection" records. Also, each record has its own "Enabled" check box. |
| − | Also, separate "Scheduler" has been run against every "DB Connection | + | Also, a separate "Scheduler" has been run against every "DB Connection String"; if the "Scheduler" runs 1st time then it is not stopped till all the "Notifications" are not sent even "Iteration" is finished and the system is checking it if "Notifications" are available in the table then new "Scheduler" is not run. |
| − | + | The system has checked if data is not available in the table then it does not run "Scheduler" and when new data is available the next "Scheduler" is run and it is not stopped till the last notification is not sent. | |
Latest revision as of 12:19, 14 September 2023
SmartHCM Notification Sender Utility 1.0.0.0 Release
Release Date: 22-Apr-2020
Module Version: 1.0.0.0
Maturity Status: Cancelled
Compatibility
| Application | Version |
|---|---|
| SmartHCM MP23.3 | 4.0.6.5 |
| SmartESS MP23.3 | 3.0.6.4 |
| SmartHCM Webservice | 2.2.8.0 |
Enhancement
- General Work - General Work: A new application has been created to send "Email / SMS" notifications against all the "System Date" (Custom Date, Retirement Date, Probation End Date, etc.) and "Late Attendance" notification types.
Users can set multiple "DB Connections Strings" in it means by using this application users can send notifications at the same time against multiple clients.
A single toggle button is available to "Start/Stop" the service.
Also, a "Log" button is used to view the log of the "Successful/Unsuccessful" service run.
Also, a "Delete" button is used to delete the "DB Connection" record from the utility.
Also, there is a separate "Enable All / Disable All" check box which is used to enable/disable at the same time all the "DB Connection" records. Also, each record has its own "Enabled" check box.
Also, a separate "Scheduler" has been run against every "DB Connection String"; if the "Scheduler" runs 1st time then it is not stopped till all the "Notifications" are not sent even "Iteration" is finished and the system is checking it if "Notifications" are available in the table then new "Scheduler" is not run.
The system has checked if data is not available in the table then it does not run "Scheduler" and when new data is available the next "Scheduler" is run and it is not stopped till the last notification is not sent.
