Hi, Thanks for posting on PSC.

Let's discuss your questions one by one:

    -  Table type validations are used to restrict the value a property(Single Value, Value List and Value Group) can have at runtime with either the predefined sets of values configured as Local list/Prompt list or pattern of values.

    - When the input value of a property isn't matched either of them an error message is set at the page level. When we have restricted or less number of known values to be compared with for that property like Days of a week, it's advised to local list otherwise Class Key or Remote Key.

    -  Local list: It's a set of limited number values configured at the property. Its used mostly when we use drop-down or radio button controls which have known lessor no of values. The designer has to add the list values in the property's general tab after selecting local list in the "Table Validation" and thus preconfigured list will appear in the UI.

    - Prompt List- It's little different from local list, it contains the key-value pair. When a designer has a requirement to show the value at UI differently in the drop-down or radio button controls than what needs to be saved in the database, we use prompt list. For ex- List of states should be displayed in UI, though we want to save state code. "New York" to be displayed as "NY" as prompt value to be persisted in the database. (Hope you got the difference between above two)

   - Class-Key- When there is a requirement to validate the input value for a property to already available data in the Pega's table, it's advised to use it. For ex- Like property is holding value for the operator I'd and it needs to be validated against the existing value available in table mapped to Data-Admin-Operator-ID table class.

    -  Remote List- It is similar to Class-Key with a little different as It validates against the particular instance of a class. I will attach configuration details afterwards in this thread.

    -  Auto-complete question: To answer your question, No, we have to specify source manually at every section where you want to configure that particular autocomplete. Pega doesn't tightly coupled controls and data type, such that user can change controls differently at section levels as well differ from what is defined at the property level.

Hope it answers all your queries. Kindly mark as answered if it does.

We do have https://academy.pega.com/ and https://collaborate.pega.com/ containing detailed explanation usually for every new feature.

Apart from it, you can always refer "Get Help" link available under "Action" menu of that particular rule. Also, new features are part of product release document.

Regards,

Asif