Ken Norcross

[Ken Norcross]

We recently (end of August) renewed 4 out of 6 licenses, but this website says that our support has expired when I try to download the latest version.

With a support renewal would we have gotten new license keys?

Our purchase model ends up creating a few levels between myself (the end user) and the people who actually purchase the renewal, so they may have received new keys without me knowing. DO I need to use new license keys with a support renewal?

[Ken Norcross]

Upgraded eaDocX to v3.6.2.7 and Sparx to V12.0.1215 and everything is back to normal, thanks!

[Ken Norcross]

I just upgraded to 3.2.6.7 and as you predicted the Tag Value issue is gone. Thanks!

But now I have the “Error generating document” issue mentioned in the other thread (missing method error).

I will go through some of the suggestions there to see if I can fix that.

I am using EA V12.0.1211 and would have similar organizational issues for upgrading that to the latest of 1215, so hopefully there is a different fix that will work for me.

[Ken Norcross]

Thanks, we are working on getting access to upgrade, I will let you know the result. This may take a few days.

[Ken Norcross]

This the the content for the custom profile. Save the xml text below in a file and import into Sparx. (TestProfilePackage.xml)

————————————-

















——————————————–

[Ken Norcross]

This the the content for the custom tag reference data file, save the xml text below in a file to import it into Sparx.(TestTagValueTypeReferenceDataExport.xml)

——————————————-







——————————————-

• This reply was modified 8 years, 9 months ago by Ken Norcross.

[Ken Norcross]

New instructions to recreate the issue…

– import the custom tag as reference data

• Project>>Data Management>>Import Reference Data…
• file “TestTagValueTypeReferenceDataExport.xml”

– install the custom profile that uses the custom tag

• open the resources window View>>Resources
• right click on the UML Profiles folder and import the test profile package “TestProfilePackage.xml”

– create a model using the stereotype in the test profile

• add a Class element to a diagram
• set the stereotype to <> from the profile called “TestProfilePackage”
• click OK as needed to close the property dialog

– the Class element in your model should now have a new tab available in the profile dialog down where you see the Tags tab

– the custom test tag called “TestTagValueType” should be visible on this new tab, set the value to True (not really needed)

– create an eaDocX document that prints this element
– print the stereotype as a table with two columns, name and the test tag

I will include the contents of the custom tag reference data file and the custom profile file in further posts below…

• This reply was modified 8 years, 9 months ago by Ken Norcross.

[Ken Norcross]

Trying one more time to upload the files…

• This reply was modified 8 years, 9 months ago by Ken Norcross.

[Ken Norcross]

I am still working on getting access here to upgrade from 3.5.5.0, it may take a while longer. I don’t think this text would come from the tag value description.

I have constructed a simple example that demonstrates the issue.

I am attaching a file with a test custom tag and a test custom profile.

Here are the instructions to recreate the problem:

• This reply was modified 8 years, 9 months ago by Ken Norcross.

[Ken Norcross]

We were able to remove one of the Office updates, and this has solved the problem.

The update we removed is called: Security Update for Microsoft Word 2013 (KB2965307) 32-bit Edition

We will continue forward with this removed until the company wide migration to Office 2013 occurs in the next few months.

[Ken Norcross]

I am working through the process on my side to get this latest set of MS Office patches removed for our team, and it is taking longer than I expected.

Removing the patches will also only be a temporary fix on our side, eventually we will be required to apply the patches.

What can I do to help troubleshoot this problem for you? How can I help you to fix this from the eaDocX side?

[Ken Norcross]

Now it fails for me also, and I just received a mandatory push update of the Office software.

As far as I can tell we use Microsoft Office Professional Plus 2010.

About Microsoft Word says:

Version 14.0.7145.500 (32-bit)

The update I just received was called:

Microsoft Office 2013 Hotfixes – Jan 2015 Patches 1.0.2

This may be our internal name for this update. I am not sure why our organization is pushing out Office 2013 patches when we all use Office 2010. I will investigate on our side if we can remove these patches.

[Ken Norcross]

“…the eaDocX code which finds this data…”

So is there an eaDocX feature that can expose this information in an output document?

[Ken Norcross]

From my reading the attribute-to-attribute association information is stored in the “StyleEx” string for the association itself.

In this string Sparx stores the GUID of the attribute element(s) involved in the association.

The two ends of the association are still the regular elements, the extra attribute information is stuffed in this StyleEx string of the association.

I don’t see any easy way to translate the stored GUIDs when using eaDocx.

This should be doable using a script, and letting eaDocx invoke the script.

[Ken Norcross]

Just checking again, anyone have any luck getting the eaDocX scripting feature working with JScript?

I have a document formatting requirement I know I could easily solve with a script, that I cannot think of how to solve otherwise (at least yet), so has anyone had any luck with JScript?

[Author]

Posts