Geert Bellekens

[Geert Bellekens]

Would be nice if we can get this working by next week.
I’m trying to sell eaDocX to this client and I need to show them an example of a document based on a BPMN process.

[Geert Bellekens]

No, no script at all via eaDocX

(I fixed the TEST variable in the code snippet above to be “test”)

[Geert Bellekens]

No, it’s not the script. The script runs fine when triggered directly from EA. I even dumbed it down to
[code]function APITest
dim outputHTML ‘ a string which will contain the HTML
outputHTML = “

Repository connection string:” & “test” & “

”
‘put the HTML string into the return
APITest = outputHTML
end function

APITest[/code]
but that still generated the error.

• This reply was modified 9 years, 6 months ago by Geert Bellekens.

[Geert Bellekens]

Ian,

EA.Element.CompositeDiagram should return the composite diagram for an element.
Fun fact: EA doesn’t always store the composite diagram ID in the same place. Sometimes it in PDATA1, sometimes elsewhere. Always fun when using queries :huh:

[Geert Bellekens]

Hi Wayne,
I’m sorry about that. I’ve never tested the EA Navigator together with EAdocx,
I’m guessing the problem is that the EA Navigator keeps doing its job in the background when EAdoxc is generating a document; which leads to conflicts.
What you could to is turn the option “Track Selected Element” off in the EA Navigator. In that case it will only do something when you actually select a menu option from the add-in.
In the meantime I’ll try to figure out a real solution.

Geert

[Author]

Posts