• Applying an "Alias" to State Name

    By Kevin Pettitt 2 decades ago

    I was thinking I would like to show different view icons next to documents based on their status, which got me thinking about the problem of "what if the status name changes?". If my column formulas are keyed off of status name, they will break in the likely even that some name change is requested down the road.



    Bear in mind that my "States" include things like "Awaiting Unit Manager Approval", which is almost guaranteed to change at some point.



    I was thinking of using the "Comments" field on the State document as a de facto "alias", that would never change and allow my column formulas to key off some stable field value somewhere on the document.



    Is there a "preferred" way to accomplish something like this that involves minimal kludginess?

    • a_RefNo

      By Mark Demicoli 2 decades ago

      Every workflow component has a unique reference number (computed when composed). Fieldname is a_RefNo. All programatic relationships use this field so there is no dependancy on component titles. You can use it in your column formulas, although you'd end up with pretty ugly formulas I concede :). I'll add an 'alias' field.

      • Kevin, Alias field added to State documents in V1.0 <EOM>

        By Mark Demicoli 2 decades ago