TOPIC : Reports

http://pegaclasses.weebly.com/courses.html videos
Questions

1. 2. 3. 4. 5. 6. 7. 8. 9. 10. 11. 12. 13. 14. 15. 16.

17. 18. 19.

What type of Reporting features are provided by Pega? What is the difference between ListView and SummaryView ? How to call a listview from an Activity? What is Paging in a listview? What is exposing a property? How to expose a single value property? How to expose aggregate property? Can we refer the property without exposing in Reports? What is the activity responsible for getting the data in List View? What the class of getContent Activity? Can or have you customize the getContent Activity? How to customize the getContent Activity? How do we get the data from the two different tables? How do we fetch the data from two different tables with out using two different tables? What is the use of HTML property in ListView? Consider this scenario: I need to generate a list view report of all the work objects created on a particular date and then I need to include this list view in a section. How this can be done? What is the difference between List View and Obj-List? Explain in brief the configuration of a list view? Explain in brief about the configuration of a summary view

Answers :

1. List View and Summary View 2. summary view :A summary view rule defines a two-level report display, presenting summary counts, totals or averages to be displayed initially, and allowing users to click a row to drill down to supporting detail for that row.Summary view rules support interactive charts, trend reports, and the use of AJAX for pop-up Smart Info windows.A summary view rule is an instance of the Rule-Obj-SummaryView rule type. This rule type is part of the Reports category.List View :A list view rule, an instance of the Rule-Obj-ListView rule type, defines a report. Users can personalize list view reports easily and interact with them.Use the Report wizard to define list view reports and link them to our portal. 3. In an activity, the Obj-List-View can execute a list view rule.

4. To divide the ListView in to different pages and set the number of records to be displayed in a page. 5. Exposing a property means to make a property as a separate independent column so that it can be used in sql queries and as a criteria in reporting. Steps are as follows 6. Process Commander stores the values of all aggregate properties and some Single Value properties in a BLOB column (the Storage Stream) usually in a compressed form. Such properties cannot support selection in list view and summary view reports, and can slow retrieval and processing in other operations Select Tools > Database > Modify Database Schema. A list of databases identified in Database data instances appears. Select a database and click Next . A list of tables in the selected database appears from Database Table instances. Select a table. Click Explore Columns . The resulting List of Classes window displays the number of rows in the table, the number of columns in the table and a list of the classes assigned to that table. The Properties Set to Be Visible value counts the properties for which the Column Inclusion value is Required or Recommended. This Column Inclusion value isadvisory, and does not indicate whether the property is exposed corresponds to a column. The Count column shows the total count of properties in this class plus those its parent classes. To see the columns currently defined in this table, click the numeric link labeled Number of columns in this table. The List of Database Columns window shows the column name, column data type, and column width in bytes for each column in the table. Declare Index rule is a better approach. Create a concrete class derived from the Index- base class. Create Single Value properties in the new class to hold values of the embedded values. Create a Declare Index rule with the appropriate embedded Page Context value that copies theembedded values into a new Index- instance. Save the Declare Index rule. It executes immediately, adding and deleting instances of the new class. Expose database columns corresponding to the Index- class. Reference the Index- properties in the list view rule. We can refer the propertys in Display tab without exposing. But we cant refer the property without exposing in Critera fields of the Content tab. getContent Activity. Embed-ListParams class. Yes Step1: Create Activity in Our Class and create the New page. Step2: write a query and store in variable. Step3: call the listview as Call Rule-Obj-ListView. Step4: Write the another activity in Embed-ListParams. Step5: create the parameter. This parameter get the sql query from previous activity Step6: write Java method The java code in this method is Get the page from pyContentPage if page already exists. If page is not available it creates the new Content-Page. In this code get the sql query from the above parameter and pass this query and above created ContentPage as parameters to this tools.getDatabase().executeRDB(query, pagename) method. Using Join tab in Reports Write a database View. In this view logically combine the Two different tables. Create class for this logically combined Table. Write the List View. Applies to class is class of the Combined table. So we can refer the properties of both the tables in list view.

7.

8. 9. 10. 11. 12.

13. 14.

15. HTML Property rules appear in list view and summary view rules to define the appearance of values in reports 16. Select .pxCreateDateTime ( an exposed property ) under criteria and give the value you are looking for.To include it in a section, check the embedded check box and customize the HTML of the section. In that we need to access the list view in a JSP tag or In section Property is DisplayAs ListView. 17. List view is generally used for complex queries where sorting is required and also we can retrieve less information using Paging. 18. List view (an instance of Rule-Obj-ListView ) is used to define a custom report or personal version of a report. A list view can be configured as follows: Applies to class of list view will be taken as the database table map for the search criteria. Display fields tab is used to depict the fields that are displayed along with category and to enable/disable Sorting Content tab is used to depict the criteria, fields to be retrieved, key of each row (if selected) and Report source activity to be called) (Page name where the values should be saved and the

In organize tab we specify to enable/disable paging, page size, mode, alignment etc. We can also configure additional buttons and their fragments here. Format tab is used to depict the formatting of the list (like even/odd coloring) and details on single click etc. List view can be accessed from an activity or html as follows: Call Rule-Obj-ListView.ShowView activity with classname and list view name as parameters <pega: ListView name= {name of list view} classname= {Class name of list view}> A list view can be used for complex retrievals from database by not specifying the display, format and Organize tabl. PyAction in that case would perform instead of refresh. 19. Summary views are used to create reports which are grouped by certain criteria and can be later drilled down. A Summary view can be configured as follows: Applies to class of summary view will be taken as the database table map for the search criteria Category is used to know under which . tab the report should come.Criteria is used in the where class (this can be asked to user by enabling prompt user)Group by and field . functions (like count) are used for initial display. If we have more than one group by it is Displayed one after another on clicking +

Drill down fields are used to display the fields when we click on the assignment. Format is used to tell how to format the display and charts can also be used. Summary view can be accessed from an activity or html as follows: Call Rule-Obj-ListView.ShowView activity with classname and summary view name as parameters. <pega: SummaryView name={name of summary view} classname={Class name of summary view}>

Agents 1. What is an Agent?

An agent is an internal background process operating on the server that runs activities on a periodic basis.Agents route work according to the rules in our application. Agents also perform system tasks such as sending e-mail notifications about assignments and outgoing correspondence, generating updated indexes for the full-text search feature, synchronizing caches across nodes in a multiple node system, and so on. 2. How do we create an Agent?

New->Sys Admin ->Agents Rule Set name is the Agent name Agent is instance of Rule-Agent-Quiee. 3. Do we need to create Agent Schedule?

No. Agent schedules cannot be created manually. The Agent Manager on our Process Commander system generate at least one agent schedule instance for each agents rule. By default, the Agent Manager checks for new or updated agents rule once every ten minutes. After we create an agents rule, the Agent Manager generates one Agent Schedule instance for each node running on your Process Commander system the next time it checks for new agents rules. 4. No 5. What are the Agent running time intervals? Do we need to migrate Agent Schedule to other environment?

Each agent activity runs individually on its own interval schedule, as a separate requestor thread. Periodic The agent runs the activity and then "sleeps" for the number of seconds entered in the Interval column. Recurring The agent runs the activity based on a specified calendar schedule (for example, every Monday at 5:00 P.M.). 6. What are the Agent Running modes?

Queue mode indicates whether the agent uses the agent queue capability to process items from

the agent queue. This feature allows the agent to temporarily skip over items that fail for example, because a needed resource is locked and try again later to process the item later. Standard Specifies that this agent processes items from an agent queue and that it relies on the system to provide object locking and other transactional support Advanced Specifies that this agent uses custom queuing Legacy specifies that this is an agent that was created in a version prior to V5.4 and has not yet been updated. This option is not available for agents created in V5.4 or later. 7. What is the use of referring Access Group in Agents?

Agent activity calls another activity. This called activity may not appear in agent rule set. So setup of the Rule set list and Roles by providing Access group in security Tab.Select the access group to use for the legacy and advanced agents listed in this rule. This field is ignored for agents with a type of Standard. 8. 1. How do we Troubleshoot or Trace an Agent? < env name="agent/enable" value="true" />

Verify above tag in prconfig file. Value of the above tag is true or false. 2. In Agent Schedule, schedule tab verify the check box Enable this agent is Checked or Not. And also verify the Enabled? Check box is checked or Not. 3. Same thing also check in Agents Rule. In Tracer we can trace the particular operator or particular Agent. In prsysmgmt portal, In Agent Management select the particular Agent and Delay the Agent and then run the Tracer. We can use the Agent Management link in the System Management Application to monitor and control agent processing. Agent runs on different nodes, select the particular node and run the Tracer. 9. What are the Agents for SLA and Correspondence?

The agents in the Pega-ProCom RuleSet process e-mail, service level rules, and assignments, archive work objects, and so on. The agents in this rule provide the following types of processing: Processing service level events and escalation Applying a flow action to assignments in bulk Sending out e-mail correspondence Archiving and purging work objects, attachments, and history Retrieving PDF files from the PegaDISTRIBUTION Manager Running tests defined through the optional Automatic Testing facility Checking incoming e-mail The activity System-Queue-ServiceLevel.ProcessEvents supports service level processing for both assignments and work objects. The activity Data-Corr-.Send supports outgoing e-mail if your system contains one or more Email Account data instances with a second key part of Notify. 10. Who will create Data-Agent-Queue?

The Agent Manager is a master agent that gathers and caches the agent configuration information set for our system when Process Commander starts. Then, at a regularly scheduled interval, it determines whether any new agents rules were created during the last period. If there are new agents rules, the Agent Manager adds them to its list of agents and generates agent schedule data instances for them for each node. 11. What are the Standard Agents?

our system includes three standard agents rules. Because these agents rules are in locked RuleSets, we cannot modify them. To change the configuration settings for the agents listed in these rules, update the agent schedules generated from the agents rule. Pega-IntSvcs, Five agents in the Pega-IntSvcs RuleSet process queued service and connector requests and perform maintenance for PegaDISTRIBUTION MANAGER (formerly called Correspondence Output Server, or COS). Pega-ProCom, The agents in the Pega-ProCom RuleSet process e-mail, service level rules, and assignments, archive work objects, and so on. The agents in this rule provide the following types of processing:

Processing service level events and escalation Applying a flow action to assignments in bulk Sending out e-mail correspondence Archiving and purging work objects, attachments, and history Retrieving PDF files from the PegaDISTRIBUTION Manager Checking incoming e-mail (deprecated in V5.3)

Pega-RULES The agents in the Pega-RULES RuleSet perform general system housecleaning and periodic processing. The agents in this rule provide the following processing: System Cleaner System Pulse System Indexer Rule Usage Snapshot Static Content Cleaner System Work Indexer 12. What is the use of Data-Agent-Queue?

When you need to modify the behavior of an agent listed in an agents rule in a locked RuleSet (any of the standard Process Commander agents rules, for example) you do so by editing one or more of the generated agent schedule instances. To monitor the Agents the url path is http://portNo:8888/prsysmgmt/