I created a template with the idea that when a user adds a document to the repository, they would select values for a 'document type' field and also a 'document subtype' field if applicable. Whether or not the 'subtype' drop down box would appear is controlled by a rule. This part seems to work fine.

If I select 'Appointment letter' as an option for the 'doc type' there is no 'subtype' field.


If I select 'Recommendation for Personnel Action' for the 'doc type' then the option to select a 'subtype' appears. Let's say I select 'Retirement.'

But then I change my mind and realize that for this document, I should have selected 'Appointment letter' all along. I go back and change the 'doc type' to 'Appointment letter' and the 'doc subtype' disappears as expected.

The problem is, unfortunately, Laserfiche apparently remembers the value previously selected for 'doc subtype' and dutifully passes it along to Workflow anyway.



This is a problem because my workflow uses these tokens in the Destination Path when itmoves the file from the *Incoming folder to its new home. There should never be a Retirement folder under the Appointment letter folder so the document is misfiled in the repository.

I know there are ways to work around this. I could add some logic to my workflow to filter out the unwanted token value, I suppose. Or, I could just go back to using Dynamic Fields. It would be nice to have the option natively in the new metadata designer though.