- Provide statistics on workflow instances with errors, resolved or still in error status. These stats will be provided based on total instances of each workflow
showing priority of which workflow issues should be addressed first
- Evaluate workflow runtime environment to determine that scheduled workflow jobs are running appropriately and efficiently
- Archiving - provide statistics on workflow volume by workflow and year to build archiving strategy. Provide instructions for archiving/retrieving archived
work items.
- Research workflow instances that are inundating the system (e.g. multiple workflows are triggered by a batch program) and can implement the event queue so that the
workflow instances are queued and spread out evenly over a period of time
- Clean up SAP Inbox messages, many users may have thousands that have never been read
- Provide solution for orphaned work items (work items with no agent) that clog and slow down the workflow environment
- Will locate dialog tasks that do not have a default rule and implement solution that allows workflow specific administrators to receive the work item if no agent is
found
- Research all the emails that are sent out with a variety of known issues:
- Emails sent directly via code (e.g. unix scripts) that bypasses SAPConnect (T-Code SCOT)
- Email addresses hard-coded or obtained from ztables, not utilizing HR emails or SAPConnect emails
- Emails sent from non-standard methods that are obscure and difficult to report on (I’ve seen emails sent from a function module in an
agent rule)
- Inconsistent use of substitution; any emails that bypass SAPConnect will not automatically utilize substitution
- Convert any jobs running the program RSCONN01 to SAP Extended Notifications
- Evaluate all existing workflow definitions, looking for common issues and inefficient coding methods
- Unnecessary workflow instances – should utilize check function
- Hard-coding in agent determination
- Hard-coded text strings
- Wasteful steps
- No task agent
- Replace hard errors with temporary errors that can resolve themselves if issue is, for example, a locked object
- Errors in code
- General Task danger – work item could potentially be sent to entire SAP community
- Report on workflows that collect attachments within the workflow instance as opposed to storing the document via ArchiveLink and
providing a link to the document for workflow use. When work items are archived the attachments are lost, however, if there is a link to the document repository the attachment will always be
associated with the workflow instance
Print 