The Workflow component of the Integration for Epic Tapestry solution is the Tapestry Integration life cycle, which consists of the following queues:
- Initial
- Manual Link/Review
- Exceptions
- Exit
- Documents entering the life cycle are sent to the Initial queue and prepared for processing. The appropriate Epic system information is determined and set as property values.
- Documents are then sent to the Manual Link/Review queue so the
document can be linked to Epic by a user. Depending on your solution's
configuration, the user will either have access to a single Link to
Epic/DocLink task which automatically assigns the document to the
appropriate Epic Tapestry context based on the document's Document Type, or the user
will have access to the Create Claim, Create CRM
Request, and Create UB tasks which they can
use to manually specify the Epic Tapestry context the document should be linked to.
The user will also be able to send the document to the
Exceptions queue using the Mark as
Exceptions ad-hoc task.
The following errors can occur when this task is executed:
Error Code Description 1 This error occurs when an unexpected error has occurred when executing the Epic Hyperdrive Launcher script. This is a fatal error that prevents the document from being linked to Epic. When this error occurs, a note is added to the document describing the error and it is automatically transitioned to the Exceptions queue.
2 This error can occur for a variety of reasons: -
-
The Epic Hyperdrive Launcher was unable to find Epic Tapestry Organization ID in session properties, or the Epic Tapestry Organization ID is empty.
-
The Epic Hyperdrive Launcher was unable to find the Epic Tapestry Environment ID in session properties, or the Epic Tapestry Environment ID is empty.
-
The Epic Hyperdrive Launcher was unable to find the Epic Hyperdrive Launcher File Path, or the Epic Hyperdrive Launcher File Path is empty.
-
3 This error occurs when the Epic Hyperdrive Launcher File Path is invalid (this is the file path configured in the Unity Client app.config file. This is a fatal error that prevents the document from being linked to Epic. When this error occurs, a note is added to the document describing the error and it is automatically transitioned to the Exceptions queue.
4 This error occurs when a timeout occurs waiting for the Epic Hyperdrive Launcher to exit. 5 This error occurs when the Epic Hyperdrive Launcher fails to launch and returns an error code. See your Epic documentation for more information on Epic error codes. This is a fatal error that prevents the document from being linked to Epic. When this error occurs, a note is added to the document describing the error and it is automatically transitioned to the Exceptions queue.
6 This error occurs when an invalid JSON response is returned from the Epic Hyperdrive Launcher. This is a fatal error that prevents the document from being linked to Epic. When this error occurs, a note is added to the document describing the error and it is automatically transitioned to the Exceptions queue.
7 This error occurs when a new instance of Epic is detected. The user must authenticate with Epic before continuing. -
- Documents in the Exceptions queue are processed by users with higher privileges, usually because an issue occurred when a user attempted to link the document in the Manual Link/Review queue. Documents in this queue can be linked to Epic using the Link to Epic/DocLink task, returned to the Initial queue for reprocessing using the Reprocess Document task, or removed from the life cycle using the Remove From Lifecycle - ADMIN task.
- After documents have passed through the other queues they are sent to the Exit queue to be held for 7 days. Documents exit this queue and the Tapestry Integration life cycle after this period ends.