Create
The Create logic block is used in the Integrate logic block to insert successfully integrated records into another table. To create this type of logic block for your integration table , you must create a new logic block with the following configurations:
| Action | Type | Table Name | Security Option | Use NATE container |
|---|---|---|---|---|
Create<hd table name> | Transaction | <hd table name>Integration | Private | False |
In the Logic Builder, build your logic block according to the steps outlined below:
The requirements below cover if the records being integrated have an IntegrationAction of Create and will handle creation of the record in the system if one does not already exist. Optionally, it can be coded in a way to give the ability to update records. How to code the update of records depends on various factors. For example, does the table use table triggers or an action block, is the action block coded in a way to handle this scenario, or does the logic block mode need to be used. If the ability to update existing records is desired, the IntegrationAction of Create should still be used. This allows for logic to be written in a way to handle inserts and updates in the same data set. The requirements below do not cover if the IntegrationAction of Update is passed in. While this is a possible use case, this would require that ALL records being integrated are known to already exist in the system.
| Requirements | Pseudo-code |
|---|---|
|
|
Integrate
The Integrate logic block is used in the Process Run list form action of the integration application to begin the integration process. To create this type of logic block for your integration table , you must create a new logic block with the following configurations:
It is important to note, that while these standards are written to incorporate using the queue parallel processing action, we always need to think about table contention. Parallel processing can only work when there is no contention. If your process could be updating the same record on another table for multiple records that are being imported, you could have contention issues. This means there would be multiple threads that are spawned that are all trying to update the same record at the same time which will lock each other out or cause a time out. To eliminate this type of contention you can use a bucket in your parallel processing action. Define your bucket so that all rows that will update the same record will run sequentially in the same thread and ensure there is no contention. The order of processing records is not guaranteed.
| Action | Type | Table Name | Security Option | Use NATE container |
|---|---|---|---|---|
Integrate<hd table name> | Background Task | <hd table name>Integration | Public-Secured | False |
In the Logic Builder, build your logic block according to the steps outlined below:
| Requirements | Pseudo-code |
|---|---|
|
|
Process Group
The Process Group logic block is used in the Integrate logic block and is used to process each group. This logic block calls the Create logic block and performs the error handling. To create this type of logic block for your integration table , you must create a new logic block with the following configurations:
| Action | Type | Table Name | Security Option | Use NATE container |
|---|---|---|---|---|
Process<hd table name>Group | Background Task | <hd table name>Integration | Private | False |
In the Logic Builder, build your logic according the steps outlined below:
| Requirements | Pseudo-code |
|---|---|
|
|
Integration Summary
The Integration Summary logic block is called by the Queue Parallel Processing action once all groups are processed in parallel. To create this type of logic block for your integration table , you must create a new logic block with the following configurations:
| Action | Type | Table Name | Security Option | Use NATE container |
|---|---|---|---|---|
Integration<hd table name>Summary | Transaction | <hd table name>Integration | Private | False |
Note: This logic block could also be Transaction type if a popup notification is needed.
In the Logic Builder, build your logic according the steps outlined below:
| Requirements | Pseudo-code |
|---|---|
|
|
Reset status
The Reset status logic block is used in the Reset Run Status list form action and Reset Group Status row action of the integration application to reset record statuses. To create this type of logic block for your integration table, you must create a new logic block with the following configurations:
| Action | Type | Table Name | Security Option | Use NATE container |
|---|---|---|---|---|
Reset<hd table name>IntegrationStatus | Background Task | <hd table name>Integration | Public-Secured | False |
In the Logic Builder, build your logic according the steps outlined below:
| Requirements | Pseudo-code |
|---|---|
|
|
Purge
This logic block is called from both the Purge Run action on the UI and when Purge Processed is set to true. When called from the UI we ignore the PurgeProcessed flag and Purge all records for the run number. When called from the integration, only Processed records are Purged. To create this type of logic block for your integration table, you must create a new logic block with the following configurations:
| Action | Type | Table Name | Security Option | Use NATE container |
|---|---|---|---|---|
Purge<hd table name>Integration | Transaction | <hd table name>Integration | Public-Secured | False |
In the Logic Builder, build your logic block according the steps outlined below:
| Requirements | Pseudo-code |
|---|---|
|
|