A while back I introduced the idea of Property Editor Features. They are add-ons to our existing property editors that make it easier to work with 'lookup' values.  For example, the Object Status to Keep parameter on the Compare Hierarchy Objects is a Stringlist that holds a set of these values: Same, Different, In1, In2, NotCompared, CantCompare.  As a workflow builder, you have to remember these values (including their case) and type them in. Now with property editor features I can lookup the possible values and select the ones I want from a check-list.  Here's the UI sequence in action:

First we open the Stringlist property editor.  It's empty.  Notice the Lookup button bottom-left.

Clicking the Lookup button opens this dialog:

 The dialog shows all the possible values that can be accepted in the parameter.  I've used a range-select feature (click the first item, shift+click the last item) to make it easy to toggle on a range of items.  When I click OK, the values are transfered into the stringlist property editor:

I can use the lookup feature over and over to edit the property values.  I can also edit them manually.

The lookup property editor feature is being added to all parameters where the possible values are known.  This includes the Read SAP Table action.  Once you've supplied the RFC Destination and Table Name, lookup can be used on the Columns to Read parameter.  Here's the dialog:

The editor triggered a lookup of the table definition (KNA1 in this example).  Now I can simply check the columns I want to be used.  In the past you'd probably use the QuickCompare wizard to examine the table definition and then one-by-one retype (or copy + paste) the columns you wanted.  The lookup function makes this much easier.

Property Editor Features also help when working with table datasets.  You may have tried to set up a Rows to Read parameter as input to the Compare Hierarchy Object action and found that it starts off with the default schema: NAME, TYPE which you have to change into: TABLE, FIELD, OP, LO, HI, IE.  I expect you wondered why LiveCompare didn't set-up the schema for you.  Now it does.

In summary, Property Editor Features covers the lookup of values that are either known (object status to keep) or can be computed (columns to keep).  It also defines the default schema for table parameters when the New> property editor feature command is invoked.

Comments welcomed.