For a while now we are getting JAXB errors in several different process models with the following error or similar to this error. Difficulty is that even if it will return the same error; where the error happens might be in different parts of the same process model (see below), but mostly it will break on the start process nodes from what I can see.
We tried removing special characters or smileys from any fields that are passed to the process with clean(), since we feel like this might be causing the errors, but so far no luck yet. Any help would be appreciated!*Please note that I have redacted a large piece of the errortext for privacy purposes. Including parts that might contain the possibly disallowed characters/smileys etc. In this specific example I think it might have been the character ü, but we have found that it is also possible that the character that will break the process is only visible in our main database (not in the MariaDB) as a blank space which makes finding the issue near impossible for a lot of cases.JAXB failure trying to convert value ProcessInfo{{pp={id=2474165, name=SCD Generic Create Transacties 22024049276, priority=1, initiator=UserRefImpl{id=xxx, uuid=null}, startTime=2024-06-14 14:59:23.91, deadline=null, timeZone=Europe/Amsterdam, starred=false, parentId=null, parentName=, execId=2, status=0, endTime=null}, pm={id=877, uuid=0006eab2-dc07-8000-3aec-7f0000014e7a, name=SCD Generic Create Transacties, description=, version=7.0, creator=UserRefImpl{id=adm.deployment, uuid=null}, timeZone=Europe/Amsterdam, starred=false, parentId=null, parentName=}, pv={TypedValue[it=3,v=archivedDossier]=TypedValue[it=4612,v=<null>], TypedValue[it=3,v=archivedTransacties]=TypedValue[it=4541,v=<null>], TypedValue[it=3,v=dossier]=TypedValue[it=3880,v={TypedValue[it=3,v=b1eb750b-11cb-43d6-8c84-e6dc3ad218e3]=TypedValue[it=3,v=22024049276], TypedValue[it=3,v=8d379549-6797-434f-a877-
......
52a844984530]=TypedValue[it=3606,v= TypedValue[it=3,v=7dc0de83-596a-4372-add8-64c6c36e3380]=TypedValue[it=57,v=<null>], TypedValue[it=3,v=a2ca2f28-a7e3-4119-8bfa-b4776cd63395]=TypedValue[it=3,v=xxx], TypedValue[it=3,v=0f10b481-e93a-48d3-b785-2e41bb618fd2]=TypedValue[it=3,v=J]}], TypedValue[it=3,v=errorText]=TypedValue[it=3,v=], TypedValue[it=3,v=parentObjectName]=TypedValue[it=3,v=DEC Send Email From Module - 22024049276], TypedValue[it=3,v=runSyncAsSubprocessBool]=TypedValue[it=26,v=<null>], TypedValue[it=3,v=standardChecks]=TypedValue[it=3,v=], TypedValue[it=3,v=transacties]=TypedValue[it=4085,v={{TypedValue[it=3,v=e56a58c2-d951-4f35-bd2c-d8ee9e9829ad]=TypedValue[it=3,v=TRN#BRIEF]}}], TypedValue[it=3,v=writeErrorBool]=TypedValue[it=26,v=<null>]}}} to Appian type ProcessInfo (id=2728)
Discussion posts and replies are publicly visible
I think that is not related with special characters but with the structure of the data. JAXB is a library designed for binding to XML your data structures.
If the strcuture of your data does not fit with overlying xsd schema, you will receive this kind of errors (JAXB Exception)
Thank you for your answer David! How would you go for resolving errors like this? Since the processes will break at different nodes and for dictionaries with different data types might there be an underlying problem with the Record Types we provide as input? For this example the input for the node was a dictionary with data for 2 record types and pp!name. From what I can see all the errors are in nodes where a dictionary is the input data for a startprocess.The data that goes in the dictionary are data types for which you would not expect errors like this e.g. Record Types, text, boolean etc.