A CacheDT node (Cache DiveTab) is a Production process node that provides a clean, controlled method to pre-compute and cache data that improves Sync time for DiveTab apps.
Time to sync for DiveTab depends on data volume, network connections, and required computations. The CacheDT node seeds the cache and eliminates the computation time experienced when synching devices, which significantly improves the user experience.
NOTE: CacheDT only works when run on the same machine as the DiveTab URL.
The CacheDG node has 
two panes where you set attributes.
Node Attributes
You set attributes for the CacheDT node in the node attributes pane.
| Attribute | Description |
|---|---|
| Name | Specify a descriptive name for the node. Lower case names maximize usage of the available space. |
| DiveLine User (Required) |
Specify the DiveLine user name to log on for cache seeding. |
| DiveTab URL (Required) |
Specify the URL of the DiveTab to be cached. Use the same URL as the server URL that is displayed in Server Settings > General DiveTab section. Be sure that the URL is a valid address. |
| Email Object for failure |
Select a predefined mailing list to send an email to if the node fails. The pull-down list is populated with items that can be found in Project Settings > Mailing Lists > Email Templates. |
| Email Object for success |
Select a predefined mailing list to send an email to if the node succeeds. The pull-down list is populated with items that can be found in Project Settings > Mailing Lists > Email Templates. |
| Email Object for warning |
Select a predefined mailing list to send an email to if the node generates a warning. The pull-down list is populated with items that can be found in Project Settings > Mailing Lists > Email Templates. |
| Failure node | Select the next node upon failure. The pull-down list contains all nodes that are on the Task Flow. |
| Success node | Select the next node upon successful completion. The next node automatically populates if a connecting line is set on the Task Flow. The pull-down list contains all nodes that are on the Task Flow. |
| Working Directory |
Specifies the directory in which this node runs. If left blank, the Default Working Directory attribute that is set in the Start Control Node is used. When running a script, Production sets the working directory for the child process to the directory that contains the script, unless the node specifies a different directory. See Start Control Node. |
| Default Working Directory |
Displays the Default Working Directory that is set the the Start Control Node. If a Default Working Directory is not specified, this attribute is blank. Applies to all nodes. See Start Control Node. |
| External File Encoding |
Select the format for the node input files. If this attribute is blank, Workbench attempts to detect the type of encoding. This attribute is also used when saving log files. The encoding might need to be adjusted when using data with high bit Latin-1 characters or Unicode characters.
|
Comments
Each node has an area where you can enter comments.
It is a DI best practice to enter a note for every node in a Production script. These notes can help you or a coworker understand the intent of the node and troubleshoot issues in the future.
See also: