INBOX
The Inbox artifact
When the user opens the inbox application, all tasks and notifications for this user are listed:
Working on a case instance can be either done by means of the Work list(s) tab page or opening the Case(s) will list the different available case models and when selecting any of the case models, the inbox shows the different case instances based on that case model. From here, you can select a specific case instance and work on all task(s) available to you as part of that case instance.
From the inbox artifact you can perform different actions of the tasks that are presented in your inbox, for example, claiming a task and revoking a task, start, pause and resume a task, complete a task, adding notes and attachments, setting a reminder for the task, forwarding or delegating a task etc. For an overview of the actions refer to the online documentation of the OTPS platform: Working with Tasks in the Work List.
Forwarding and delegating a task
Users can forward and delegate task(s) that have been received. The difference between forwarding a task and delegating a task is the ownership of the task itself. When forwarding a task, the ownership of the task is transferred to the receiver as well. When delegating a task, the ownership of the task remains with the user who delegated the task. This means that the task is still visible in the task list of the initial user to whom the task initially was assigned. The associated forward and delegate messages are added as memos to the task and can be found in the Memos tab page of the task. By means of the option Task History, users are able to explore what has happened to the task.
The inbox artifact contains a number of vertical tab pages:
The inbox artifact is built through the user interface layer of the OpenText Platform and thus provides some of the functionality as supported by this layer:
Tasks are the common means for users to interact with the process and/or case instances. Tasks are represented by user interfaces as designed as part of an OTPS application. The inbox artifact provides a rich and supportive environment for users to participate in and work on the tasks that are modelled in a business process and case model.
List of abbreviations
Abbreviation | Description |
ANSI | American National Standards Institute |
BAM | Business Activity Monitoring |
BER | Business Event Response |
BPML | Business Process Modeling Language |
BPMN | Business Process Modeling Notation |
BPMS | Business Process Management Suite (or System) |
CAF | Composite Application Framework file extension |
CAL | Composite Application Logging (framework) |
CAP | Cordys / Composite Application Package (file extension) |
CARS | Cordys Admin Repository Server |
CMC | Cordys Management Console |
CRUD | Create, Read, Update and Delete, data manipulation operations with a relational database |
CWS | Collaborative Work Space |
DTAP | Development, Testing, Acceptance and Production |
ESB | Enterprise Service Bus |
HW | HardWare |
IDE | Integrated Development Environment |
IP | Internet Protocol |
JAR | Java ARchive file extension |
JVM | Java Virtual Machine |
KPI | Key Performance Indicator |
LDAP | Lightweight Directory Access Protocol |
OMG | Object Management Group |
OTPS | OpenText Process Suite |
PIM | Process Instance Manager |
PMO | Process Monitoring Object |
RDBMS | Relational DataBase Management System |
SCM | Software Configuration Management |
SCXML | State Chart XML |
SOA | Services Oriented Architecture |
SOAP | Simple Object Access Protocol |
SQL | Structured Query Language |
SSU | State Sync-Up |
SVN | SubVersioN |
SW | SoftWare |
W3C | World Wide Web Consortium |
WfMC | Workflow Management Coalition |
WSDL | Web Service Definition Language |
WSI | Web Service Interface |
WSO | Web Service Operation |
XML | eXtensible Mark-up Language |
XPDL | XML Process Definition Language |
Don't miss out on future blog posts! Subscribe to email updates today!