Skip to main content

Dear all,

For some time now I'm facing an issue that keeps bugging me: some Workflow tasks (using Nintex Task with multiple outcome) do not show the outcomes (Approve/Reject).

The Flexi Task used has some extra Task description text with some workflow and item properties included. Nothing fancy. Most of the time, clearing the Description field and adding the text again works fine to resolve the issue for new task.

It seems that the Nintex engine somehow messes up the HTML for rich text content sad.png Also for task notification email bodies sad.pngsad.png

If possible I would like to avoid to build the texts in strings (including HTML/CSS), as that would be a major inconvenience and annoyance.

Is there a way, apart from LazyApproval (luckily enabled), to still get access to the outcome of the messed up workflow tasks?

>UPDATE] This happens at runtime. In the screenshot below the blurred regions in the red box are part of the Description ending in a user on the left with the presence awareness icon.

NB: I've blurred the task description for customer privacy reason..

Thanks,

Jean-Pierre

I'm not sure from your description, is it missing in designer or at runtime in task form?

could you post an example, just to get into picture?

Hi Marian,

Description above updated happy.png

ok, I see.

have you directly edited description's HTML source?

since you have there active user presence control, I guess you have done so...

it's quite known that if one edits directly HTML source, some HTML attributes and/or (valid) constructs are removed by reach text edit controls.but that happens immediately once you save your changes. so it shouldn't happen it sometimes works and sometimes not.

I'm not sure whether it's nintex's or sharepoint's "feature"

as well it's known that if you edit existing content within reach text editor, HTML markup behind gets broken sometimes. it's simply because with reach text editor you can not for sure determine whether you make edits of HTML tag itself (attributes...) or tag's value. of course it shouldn't behave this way, but from my experience the editor is not reliable.

I prefer to prepare the content into text variables and then insert variables into description/body. I found it much more reliable myself.

the last reason might be that data to be shown contains some sensitive characters that may break HTML markup. have you checked for these?

Thank you ‌. In that case I'll adopt the "best practice" to build messages as a string first and use that instead of modifying the task description. And most likely do the same for (workflow) task notification emails.

Reply


View our Community Site Map

Nintex Community Sitemap
Terms & ConditionsCookie settings