This content has been marked as final. Show 7 replies
Why don't you simply distribute fields/groups into separate rules and construct your profiles by including just the rules (groups/fields) you need?
I could, just trying to see if there was a way to not make a whole new profile since what I'm doing is just a very cut down version of a profile I already made; and since I have metadata fields being turned info only based on where the item is in the workflow so it wouldn't have been a strech to just exclude the fields altogether.
when is <$dpPromote("xMetadata:isExcluded", "1")$> triggered?1 person found this helpful
do you pass additional parameters to full form for reusability?
You could also use Rules Activation condition (it kind of makes one profile dynamic).
I'd also recommend to read this paper: http://www.cs.utexas.edu/~EWD/transcriptions/EWD03xx/EWD340.html (very old, but still true)
<$dpPromote("xMetadata:isExcluded", "1")$> is triggered when the metadata field xDocType (which has fields a,b,c) is equal to c on the info page, and that seems to work, it is exlucded when xDocType is c but not a and b. It's just that group heading is still there.
Ok the metadata activation rule worked like a charm, thanks for that Jiri.
you could do what jiri suggested.1 person found this helpful
1) create 1 additional rule for hiding your xMetadata.
2)To this rule under General Tab select "Use Rule Activation Condition" --> go to custom tab and add
( (dpAction like "Info") and (dDoctype like "<value>"))
3) add the metadata and select hidden from dropdown.
4) Add this rule to your profile. Make sure this rule is after your original rule for displaying xMetadata.