Just a quick osservazzjoni li hemm differenza importanti ħafna bejn dawn iż-żewġ definizzjonijiet:

<FieldBind Field="InParam1" DesignerType="StringBuilder" Id="2" Text="Input parameter #1"/>

versus:

<FieldBind Field="InParam1" Id="2" Text="Input parameter #1"/>

L-ewwel turi bħal dan fil SPD:

filwaqt li dawn tal-aħħar turi bħal dan:

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 🙂

L-osservazzjoni hija din: StringBuilder jippermettilek li tibni string (ovvjament) billi jitħalltu flimkien Literali b'Sensiela u data workflow (via the "Add Lookup" buttuna fil-rokna tax-xellug t'isfel). When you use the Add Lookup button, it inserts a token in the form "[%token%]". When SharePoint invokes your custom action, (C # kodiċi fil-każ tiegħi), SharePoint jgħaddi l-token innifsu, not the value of the token. If you use the default designer type (it-tieni tip), SharePoint tespandi l-token u jgħaddi valur attwali tal-token għal azzjoni tiegħek.

StringBuilder = BAD, tip disinjatur default = TAJBA.

Of course, 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 (li inċidentalment huwa eżattament dak li wieħed ma toħloq suġġett dinamiku għall-azzjoni email, iżda li suġġett għad-dħul ieħor blog, għandha l-).

<aħħari />