Jul 04, 2017 - 03:08 AM
>Next, you need to decide on the scope. : ->You have three options for the scope: ->thread : ->useful when the data page is context-sensitive to a particular case. ->For example, if a customer service representative (CSR) is simultaneously working on several cases belonging to different customers, the data page must be defined as thread scope since the customer data should be limited to a specific case. ->Setting the scope to thread ensures that the CSR sees only the data relevant to an individual customer's case. If the data can be shared across cases, then a broader scope, such as requester or node, should be chosen. ->requestor : ->allows you to share data pages for a given user session and is often used when the data page contains data associated with the logged in operator. ->The work list or local weather information are both examples of data associated with the logged in operator. ->node : ->makes a single data page instance accessible by all users of the application and other applications running on a given node. ->On a multinode system, each Java Virtual Machine instance has one copy of the node level data page. ->Node level pages reduce the memory footprint by storing only a single copy of the data available to all users. ->Node level pages are an excellent option for storing common reference data such as currency exchange rates. >Then, you need to configure the data sources : ->For list structures the sourcing options include: ->connector : Use a connector to obtain data from an external data source as specified by the connector type. ->Data transform : Use the data transform option to populate a data page using a data transform. ->Report definition : Use a report definition to return a list of data objects mapped in the application. ->Load activity : The activity can be used for special situations where none of the other options are suitable. ->For page structures the sourcing options include the same options as list except report definition: ->For page structures, the look-up data source replaces report definition as an option. ->Look-up : ->Use the look-up to return a specific data object mapped in the application. >The Request Data Transform and Response Data Transform allow you to map the outgoing and incoming data to the application data structure. ->You configure the Refresh strategy on the Load Management tab. ->The available reload options depend on the scope of the page. ->For requestor or thread pages, you can reload the data for each interaction or upon a when rule evaluating to false. ->The data page can also be marked for refresh based on an elapsed time interval calculated from the last load time. ->If you combine the Do not reload when and Reload if older than options, the data page refreshes as soon as either condition is met. ->Note ->The refresh strategy for a node level page reloads per interaction and does not reload when options are not available. ->Node level data pages are not executed in the context of a logged in operator since they are available for all applications on the node. ->Instead an access group is specified to provide the requestor context used by the system when loading the node level data page. ->Data pages load to memory on demand. ->A data page remains in memory, on the clipboard, to serve requests without reloading the data until marked to be reloaded.