The solution was designed with the following in mind:
- Documents are ingested into OnBase and added to a custom Workflow life cycle.
- A Unity Script is used to programatically gather required properties to execute the launch of required Epic executables, and ingest needed information in order to execute required API calls.
- Workflow users click on an ad-hoc Workflow task to link the document to the corresponding Epic Tapestry module.
- The Epic Tapestry context the document is linked to is determined in one of two ways,
depending on your solution's configuration:
- The Epic Tapestry context the document is linked to is determined automatically by the Document Type Group when the user selects the Link to Epic/DocLink Workflow task.
- The Epic Tapestry context the document is linked to is determined by the Workflow task the user selects (Create Claim, Create CRM Request, and Create UB).