Profiling values and counts

When mapping a user table, you can choose to pre-compute the distinct values and frequency counts for specific fields, or allow users to perform real-time profiling of data in the base record table. Profiling enables users to see a table’s values when editing a flowchart, without having to view raw data and allows them to easily select from valid values when building a query. Pre-computed profiles provide quick and efficient access to the distinct field values and counts without querying the database. Real-time profiling provides access to the most up-to-date data and may be helpful if your database updates frequently. If you pre-compute profiles, you can control how often profiles are regenerated.

You can choose to both pre-compute profiles and allow users to dynamically profile in real-time, or you can choose to disable real-time profiling and force users to always use the pre-computed profiles. Enabling or disabling the Allow real-time profiling option applies to all table fields, not just the checked ones. If you disable real-time profiling and do not specify an alternate means for pre-generated profiles, users will not be able to view any values or counts for any fields in this table. If you disable real-time profiling and provide pre-computed profiles for one or more fields, users will be able to access the pre-computed profiles, which is for the entire table. Users will not be able to profile only the values for the input cell of a process. To provide the greatest flexibility, you should allow real-time profiling.