nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Special characters

asha1

Hello,

Whenever we enter few special characters like & , ", >,< in the job description of the workflow instantiation screen, we get an error "Failed to instantiate workflow model."

Did any one come across such an error or if you know of any fix for the issue, please comment.

Find more posts tagged with

Comments

ISCBorisB

Hello,

Whenever we enter few special characters like & , ", >,< in the job description of the workflow instantiation screen, we get an error "Failed to instantiate workflow model."

Did any one come across such an error or if you know of any fix for the issue, please comment.

Good chances are, XML Syntactical elements make your WF Specifications (WFT, WFM?) malformed.

To fix that you can either teach your contributors to use XML Entities (like & instead of just &)
or better yet, take care of that automatically in your WF Instantiation code.

asha1

Thanks for you reply Boris. We are using WFM. & works fine.

I would like to address this at the workflow end. How to address this issue on the instantiation code? Any suggessitons here?

Adam Stoller

Thanks for you reply Boris. We are using WFM. & works fine.

I would like to address this at the workflow end. How to address this issue on the instantiation code? Any suggessitons here?

You need to do two things:

ISCBorisB

Thanks for you reply Boris. We are using WFM. & works fine.

I would like to address this at the workflow end. How to address this issue on the instantiation code? Any suggessitons here?

Actually, for the WFM's out of the box WF Description Property you do not have to do anything.

WFM Engine will automatically convert applicable characters to XML entities. If your "Description"
is something else or if you are processing it yourself (thus perhaps breaking conversion), we will
have to know more details to provide help.

asha1

Actually, for the WFM's out of the box WF Description Property you do not have to do anything.

WFM Engine will automatically convert applicable characters to XML entities. If your "Description"
is something else or if you are processing it yourself (thus perhaps breaking conversion), we will
have to know more details to provide help.

Hi,

We are using customized workflows that is NOT OOB. What additional details would you need ?

thanks.

ISCBorisB

Hi,

We are using customized workflows that is NOT OOB. What additional details would you need ?

thanks.

Note that I did not say "out of the box Workflows...". I did say "out of the box WF
Description Property..." which you can use with any Workflow, customized or otherwise.

Garth McMillan

We also encountered that issue with an older version of TeamSite (I think it was fixed in 6.7.2 SP2).

However, we now have a similar issue in TeamSite 7.3.1 in that it strips any whitespace after ampersands.

In 7.3.1's case, it is a bug within XMLBEANS (which is used by TeamSite) that was corrected in July 2006 (https://issues.apache.org/jira/browse/XMLBEANS-274). Unfortunately TeamSite uses a very old version of XMLBeans that still contains the bug. We have a support case open with Autonomy.

asha1

Note that I did not say "out of the box Workflows...". I did say "out of the box WF
Description Property..." which you can use with any Workflow, customized or otherwise.

Thanks Boris. Your suggesstion worked for me.