-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
8 changed files
with
50 additions
and
15 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
7 changes: 0 additions & 7 deletions
7
...content/docs/cross_application_workflows/employer_implementation_flow/gluedb.md
This file was deleted.
Oops, something went wrong.
27 changes: 27 additions & 0 deletions
27
.../docs/cross_application_workflows/employer_implementation_flow/gluedb/_index.md
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,27 @@ | ||
--- | ||
title: GlueDB | ||
description: > | ||
GlueDB's place in the implementation flow. | ||
build: | ||
list: local | ||
--- | ||
|
||
## Responsibilities | ||
|
||
GlueDB has multiple responsiblities during the implementation flow: | ||
|
||
1. Collect Employer Events into a batch, performing deduplication and filtering, and awaiting a signal to publish the Employer Event Digest. | ||
2. Publish Employer Event Batches. | ||
3. Request Enrollment Information from Enroll when appropriate, and transmit enrollment information to interested systems in the correct format. | ||
|
||
## Employer Event Collection | ||
|
||
Prior to the implementation phase, GlueDB is continually collecting and reducing Employer Events. | ||
|
||
 | ||
|
||
## Employer Batch Cut Flow | ||
|
||
During the implementation phase, an event is triggered to GlueDB that signals it is time to begin publishing and dealing with the Employer Events it has been collecting. | ||
|
||
 |
Binary file added
BIN
+104 KB
...lication_workflows/employer_implementation_flow/gluedb/employer_batch_build.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added
BIN
+141 KB
...plication_workflows/employer_implementation_flow/gluedb/employer_batch_flow.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
7 changes: 0 additions & 7 deletions
7
...docs/cross_application_workflows/employer_implementation_flow/hbx_enterprise.md
This file was deleted.
Oops, something went wrong.
22 changes: 22 additions & 0 deletions
22
...oss_application_workflows/employer_implementation_flow/hbx_enterprise/_index.md
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,22 @@ | ||
--- | ||
title: Hbx Enterprise | ||
description: > | ||
Hbx Enterprise's place in the implementation flow. | ||
build: | ||
list: local | ||
--- | ||
|
||
## Responsibilities | ||
|
||
Hbx Enterprise has multiple responsiblities during the implementation flow: | ||
|
||
1. Upload Employer Event Digests (in CV2 XML format) to the Oracle B2B for carriers. | ||
2. Convert Employer Event Digests (in CV2 XML format) to the legacy CV1 XML format acceptable to the Payment Processor | ||
3. Upload Employer Event Digests (in CV1 XML format) to the Payment Processor SFTP | ||
4. Upload Enrollment Information (in CV1 XML format) to the Payment Processor SFTP | ||
|
||
## Employer Digest XML Flow | ||
|
||
Upon recieving an Employer Digest XML in CV2 format, HBX Enterprise executes the transformation and delivery of the various forms of the digest. | ||
|
||
 |
Binary file added
BIN
+94.3 KB
..._workflows/employer_implementation_flow/hbx_enterprise/employer_digest_flow.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.