Activity Chart
From DocWiki
(Difference between revisions)
| Line 19: | Line 19: | ||
|1 | |1 | ||
|Forwarded | |Forwarded | ||
| + | |- | ||
| + | |Assigned(5000) | ||
| + | |in_progress(5900) | ||
| + | |Redirect Original(a1) | ||
| + | |100 | ||
| + | |1 | ||
| + | |1 | ||
| + | |Redirected | ||
| + | |- | ||
| + | |Assigned(5000) | ||
| + | |in_progress(5900) | ||
| + | |Reply Original(a1) | ||
| + | |100 | ||
| + | |1 | ||
| + | |1 | ||
| + | |Replied | ||
| + | |- | ||
Revision as of 07:03, 11 January 2011
Note:
- The table below gives the interpretations of various status and sub-status values in the EGPL_CASEMGMT_ACTIVITY table for a given activity that resides in the system. It will be very helpful for debugging retriever, workflow, dispatcher, and other activity based issues when you run SELECT queries (with filters) on this table to determine whether an activity actually made it into the system or why the activity failed to get processed, dispatched, etc.
| Activity Status | Activity Substatus | Action | Activity Mode | Activity Type | Activity Subtype | Last Action Reason |
|---|---|---|---|---|---|---|
| Assigned(5000) | in_progress(5900) | Forward Original(a1) | 100 | 1 | 1 | Forwarded |
| Assigned(5000) | in_progress(5900) | Redirect Original(a1) | 100 | 1 | 1 | Redirected |
| Assigned(5000) | in_progress(5900) | Reply Original(a1) | 100 | 1 | 1 | Replied |
