In the Properties of the SO Processor Activities page, we can see that this is a PageType of CardPart tied to SourceTable SalesCue:
Next, we want to Design the referenced table, Sales Cue, to see how it is constructed:
As we see in the preceding screenshot, there is a simply structured table, with an integer field for each of the action Cues and a decimal field for the information Cue, all of which were displayed in the Role Center we are analyzing. There is also a key field, two fields identified as Date Filters, and a field identified as a Responsibility Center Filter.
When we display the properties of one of these integer fields, Sales Orders - Open, we find it is a FlowField providing a Count of the Sales Orders with a Status of Open:
If we inspect each of the other integer fields in this table, we will find a similar FlowField setup. Each is defined to fit the specific Cue to which it's tied. If we think about what the Cues show (a count) and how FlowFields work (a calculation based on a range of data records), we can see this is a simple, direct method of providing the information necessary to support Cue displays. Clicking on the action Cue (the count) opens up the list of records being counted. The information Cue is tied to a decimal field, which is computed by means of a function, as shown in the following screenshot, in the Cue table that is invoked from the Role Center page when the Cue is displayed:
The following screenshot shows the list of Cue tables. Each of the Cue tables contains a series of FlowFields and other fields that support a set of Cues. Some Cue tables service more than one of the Role Center pages:
