Skip to main content


         This documentation site is for previous versions. Visit our new documentation site for current releases.      
 

Tables in Pega Academy

Updated on June 1, 2022

Use tables to organize and present information that users are likely to look up for a quick answer, for example, settings, error messages, and alerts.

Standard tables

Style and structure

To ensure that your tables are readable, concise, and consistent with our style, apply the following best practices:
  • Introduce the table with a full sentence and end the sentence with a colon. If the introduction is an entire paragraph, end that paragraph with a period.
  • In the introduction, describe what kind of information the table presents and how our clients can use that data to achieve their goals.
  • Create tables that have at least two columns and rows, and no more than four columns. Tables with more columns might be hard to read, especially on mobile devices.
  • Keep content in each cell brief. Ideally, each cell should contain a single sentence or phrase.

Language

Keep your table linguistically coherent by following these guidelines:
  • Use sentence-style capitalization for column headings and for the content in the table.
  • Exclude punctuation from column headings (no periods, no ellipses).
  • Enforce parallel structure of the content in the table so that all items in a single column have the same structure. For example, begin all items in the first column with a verb or a noun phrase.
  • List items in alphabetical order unless another order is more appropriate.
  • Use end punctuation correctly. Use periods only if the table cells contain complete sentences or a mix of fragments and complete sentences.
  • Use “Not applicable” or “None” for empty table cells instead of leaving the cells blank.
The following table describes the key access roles provided with the Pega Sales Automation for Financial Services:

Role

Description

Default portal

Sales Representative (Financial Advisor or Relationship Manager)

Sales Reps manage their Lead and Opportunity pipeline including all communications with prospects and customers.

Sales Rep Portal

Sales Manager

Sales Managers manage teams, monitor overall performance, and collaborate with their teams.

Sales Manager Portal

Sales Operations

Sales Ops are responsible for supporting the sales team by managing Territories and Users and administering data.

Sales Ops Portal

Action tables

Use an action table in challenges to describe steps for a single element when at least one of the items requires users to perform more than one substep. The table displays actions in a two-column table where you describe each action. In the first column, you list the element, for example, different sections in a case view or specific scenarios; in the second column, you describe the steps that users need to perform for each element or scenario.

Style and structure

To ensure that your tables are readable, concise, and consistent with our style, apply the following best practices:
  • In the step in which you want to add an action table, enter a meaningful introductory sentence that summarizes the available options in that step and end the sentence with a colon.
  • Create tables with two columns.
  • In the header of the left column, enter the relevant UI element description.
  • In the header of the right column, enter Actions.
  • In the right column, describe the actions to take by using the usual challenge step format. Orient the student by telling them where to select something and then what to select. Steps should include a location, the action, and the purpose.

Language

Keep your table linguistically coherent by following these guidelines:
  • Use sentence-style capitalization for column headings and for the content in the table.
  • Exclude punctuation from column headings (no periods, no ellipses).
  • Use end punctuation correctly.
  1. Add the following design blocks to the automation surface:

    Design block name

    Actions

    SelectedIndex property

    1. On the Palette tab, click Applications > BankerInsight > BankerInsight1, and then drag the tabAccountMgmt control to the automation surface. 

    2. In the Select action dialog box, click More.

    3. In the search field, enter selectedIndex.

    4. On the Property tab, select the SelectedIndex checkbox, and then click Add.

    PerformClick method

    1. On the Palette tab, click BankerInsight > BankerInsight1 > tabAccountMgmt, and then drag the tabDispute control to the automation surface. 

    2. In the Select action dialog box, click More.

    3. In the search field, enter PerformClick.

    4. On the Method tab, select the PerformClick checkbox, and then click Add.

    Text property

    1. On the Palette tab, click BankerInsight > BankerInsight1 > tabAccountMgmt > tabDispute, and then drag the txtBoxTxnID control to the automation surface. 

    2. In the Select action dialog box, click More.

    3. In the search field, enter Text.

    4. On the Property tab, select the Text checkbox, and then click Add.

 

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us