Case Store Output nodes are Analysis end points. Bringing a Case Store Output node into an Analysis is how you can populate a Case Store with header records.
Display Name
This parameter simply sets the node's display name in the diagram.
Case Store
Here, a drop down will allow you to select a predefined Case Store into which to push data. Note that unlike a Data Store Output, there is no option to create a Case Store Output on the fly. In order to use a Case Store Output node, you must have already created the Case Store, and given it the appropriate field structure to which you can map.
Field Mapping Tab
Fields from your Analysis must be mapped to appropriate fields in your Case Store Output. Mapping requires that Incoming Fields have the same data types as Case Store Fields.
Update Tab
If you would like to update records within a Case Store based on a unique set of key fields that identify each record, you can do so by checking the Update Data in Case Store check box available in the Field Mapping Tab.
Whenever a Case Store Output node with Update configured receives new data, it will check to see whether the values in a record's Key Fields already exist in a record within the Case Store. If they do, the Case Store will update all other fields for that record, rather than create a new record.
For example, suppose Update were configured with id set as the Key Field, and the following record existed in the Case Store:
id |
value |
---|---|
001 |
123 |
Since Update is configured, the next time this Case Store loads, it will check to see whether newly loaded records have an id = 001.
Suppose there are records that do:
id |
value |
---|---|
001 |
456 |
001 |
789 |
Rather than create more records for id 001, the Case Store will update the pre-existing record using the last new record with a matching Key Field value that it finds. This will assign the pre-existing record where id = 001 a value of 789.