Ut wisi magna vivos observatur differentia inter has duas definitiones:

<FieldBind Field = "InParam1" Excogitatoris Type = "String adipiscing" Id = "II" Text = "Input parameter # I" />

versus:

<FieldBind Field = "InParam1" Id = "II" Text = "Input parameter # I" />

Primo ostendit hoc in SPD:

haec ostendit sicut hoc:

I’m not sure how helpful these screen shots are but I put in the effort to make them so you have to view them 🙂

Hoc est, observetur: StringBuilder sino vos ædificare filum (Manifestum) commiscendo simul filum literals et notitia workflow (via the "Add Lookup" pyga in inferiorem sinistram angulo). When you use the Add Lookup button, it inserts a token in the form "[%signum%]". When SharePoint invokes your custom action, (C # code in causam meam), SharePoint transit signum ipsum, not the value of the token. If you use the default designer type (secundi generis), SharePoint dilatat actu et transit signum valoris signum actionis.

StringBuilder = BAD, Annum amet type = BONA.

Utique, that’s not what I really mean. Just don’t try and pass a parameter to your custom action when the designer type = StringBuilder. Use the default designer type and chain a StringBuilder to it up front if you need to build complex strings in your workflow (quod per accidens est prorsus quod facit subiectum creare dynamicam actionem email, sed quod est subiectum alterius ingressum blog, Har Har).

<Finis />