new:implementation_of_alerts_and_automated_tasks
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
new:implementation_of_alerts_and_automated_tasks [2015/01/18 16:17] mueed |
new:implementation_of_alerts_and_automated_tasks [2015/12/01 03:34] (current) asok |
||
|---|---|---|---|
| Line 3: | Line 3: | ||
| Accessible through Home» System Administration» Automation and Resources. \\ | Accessible through Home» System Administration» Automation and Resources. \\ | ||
| - | **Alerts**\\ | + | ===Alerts=== |
| Alert can be generated when user performs any action say, clicking Add/Update or Confirm on screen. | Alert can be generated when user performs any action say, clicking Add/Update or Confirm on screen. | ||
| And associated recipients are notified via E-Mail,SMS or DreamApps message as preferred in the Alert Setup.\\ | And associated recipients are notified via E-Mail,SMS or DreamApps message as preferred in the Alert Setup.\\ | ||
| Line 23: | Line 23: | ||
| \\ | \\ | ||
| - | **Automated Tasks**\\ | + | ===Automated Tasks=== |
| Tasks can be automated without user doing any action n DreamApps. A method is scheduled to run periodically.\\ | Tasks can be automated without user doing any action n DreamApps. A method is scheduled to run periodically.\\ | ||
| To setup an Automated Tasks we need to know:\\ | To setup an Automated Tasks we need to know:\\ | ||
| Line 31: | Line 31: | ||
| - Time Scheduled. Starting Time of execution (e.g.:17:00) | - Time Scheduled. Starting Time of execution (e.g.:17:00) | ||
| - Time Interval. Interval between two executions. (e.g.: 00:30.) | - Time Interval. Interval between two executions. (e.g.: 00:30.) | ||
| - | \\ System will execute chkdob method after every 30 mins starting from 17:00.\\ | + | System will execute chkdob method after every 30 mins starting from 17:00.\\ |
| + | |||
| + | ===Combination of Alert and Automated Tasks=== | ||
| + | Generating Alerts even without the user performing any action is also possible by combining Automated Tasks and Alert. | ||
| + | Say, stakeholders needed to be notified if a Sales quotation is not Approved within 3 days of creation. | ||
| + | To achieve that: | ||
| + | * An Automated Tasks is prepared using appropriate method and time schedule. e.g.: opqotnotify at an interval of 3 hours.\\ | ||
| + | * | ||
| + | An Alert entry should be prepared selecting: | ||
| + | * Page: *Custom*. As no screen/page is responsible for the alert to trigger | ||
| + | * Command|Tab should contain the #alert name specified under the automated method. As no tab and command button triggers the alert, rather an automated task does. | ||
| + | * Select Sender (e.g.:asok@dreamapps.com) | ||
| + | * Select appropriate notification format. (e.g.: opqotnotify) | ||
| + | * Method should be cadummy. | ||
| + | * Recipient list should be prepared as per specification. \\ | ||
| + | After every 3 hours, system will check for any quotation which is not approved within 3 days of creation and notify the specified stakeholders. | ||
/srv/www/htdocs/wiki/data/attic/new/implementation_of_alerts_and_automated_tasks.1421597866.txt.gz · Last modified: 2015/01/18 16:17 by mueed
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International
