Forum Replies Created
Derek Read February 14, 2019 at 8:20 pm
Reply To: XMAX12: Could not get initialized if %appdata% is mapped to a network shareFebruary 14, 2019 at 8:20 pmParticipants 0Replies 2618Last Activity 1 year, 9 months ago
If you have time to test XMAX 13 now is a good time to provide feedback on it that might make it into version 14.Derek Read February 14, 2019 at 8:19 pm
Reply To: XMAX12: Could not get initialized if %appdata% is mapped to a network shareFebruary 14, 2019 at 8:19 pmParticipants 0Replies 2618Last Activity 1 year, 9 months ago
We have been releasing major versions annually for quite a while, but specific dates for XMAX are hard to nail down. “Summer” is a good guess.
XMetaL Author Enterprise typically comes out in March (this is the biggest selling product and is always released first) followed by XMetaL Author Essential (essentially the same product minus a bunch of features), then XMAX. All of those products have a large shared codebase.
XMetaL Developer (if we do one that year) and the CMS integrations that we maintain ourselves usually follow in the fall (XMetaL Author Enterprise for SharePoint and Documentum).Derek Read February 6, 2019 at 11:54 pm
Reply To: XMAX12: Could not get initialized if %appdata% is mapped to a network shareFebruary 6, 2019 at 11:54 pmParticipants 0Replies 2618Last Activity 1 year, 10 months ago
I have repeated the same test but this time without mapping the drive letter and instead using a network path similar to yours:
No problems in this case either.Derek Read February 6, 2019 at 11:44 pm
Reply To: XMAX12: Could not get initialized if %appdata% is mapped to a network shareFebruary 6, 2019 at 11:44 pmParticipants 0Replies 2618Last Activity 1 year, 10 months ago
This is what I see when testing with XMAX 13 and your solution, after having moved my %appdata% folder to a Windows share that is mapped to the O: drive (something I already have in place), and making sure there is no SoftQuad folder there (which there isn't by default of course since the “roaming” folder was just created by me and is new). After XMAX created it the first time I removed it again and XMAX had no trouble creating it again, nor writing into it.
In this dialog XMAX is telling us that it is writing out it's minimum set of customization files. I'm not sure if that is normal for your setup. I assume there is no document-level customization simply because this is a stress test. If for whatever reason you cannot work around this problem perhaps providing a full set of customization files will avoid XMAX having to write here (since it can simply load them all from the DTD location).
Here are some guesses:
1. Somehow (without knowing about this issue, nor knowing how to reproduce it) we have altered the way XMAX 13 accesses %appdata% and reads/writes to it. I think that is unlikely as we are using standard Windows APIs for this. It is possible that the Microsoft compiler or code that we used for XMAX 12 is different for 13 (some update has been applied or similar) though I don't think that is the case.
2. Somehow the folder you have pointed %appdata% to on your test system is not functioning the way Windows needs it to, or at least those APIs that we use to read/write files.
3. Something else is interfering with all of this, perhaps some additional 3rd party code is required to reproduce the issue that I do not have. This might be part of your own code, or perhaps it is something entirely separate, such an an anti-virus or other kind of security software, or perhaps the server where these files are stored is somehow behaving oddly when it comes to Windows client machine access.Derek Read February 6, 2019 at 8:15 pm
Reply To: XMAX12: Could not get initialized if %appdata% is mapped to a network shareFebruary 6, 2019 at 8:15 pmParticipants 0Replies 2618Last Activity 1 year, 10 months ago
I will have a look.
I am testing with XMAX 13 so that might be the difference. You should also try the current release of XMAX on your side to see if that helps. There isn't much point in testing with 12. If there is an issue with that version a fix for it won't be created. If the issue is reproducible in version 13 then (given current development workflow) it would likely be addressed in version 14.Derek Read February 5, 2019 at 10:52 pm
Reply To: XMAX12: Could not get initialized if %appdata% is mapped to a network shareFebruary 5, 2019 at 10:52 pmParticipants 0Replies 2618Last Activity 1 year, 10 months ago
I've followed your instructions, though not on a Terminal Server (I have no access to such a system) on a regular installation of Windows 10 Enterprise instead, and I do not see the issue.
Perhaps if you map the location to a drive letter that will help?
So, instead of having \data03USERNAMEroaming
Map “data03” to a drive letter so that the path is R:USERNAMEroaming
What kind of error is raised for you when it fails?Derek Read February 4, 2019 at 10:19 pm
Reply To: XMAX12: Could not get initialized if %appdata% is mapped to a network shareFebruary 4, 2019 at 10:19 pmParticipants 0Replies 2618Last Activity 1 year, 10 months ago
Each user needs to have their own separate %appdata% location for XMAX (which I think would typically be created for each user/account on a Terminal Server session, or maybe I don't understand how you can configure such a system). If a folder is being shared among users then temp files written there by each copy of XMAX might trigger a race condition and that is not something the software is designed to handle.
If that doesn't sound like the issue you are seeing we will need more information about the setup.
If a Terminal Server is involved and you are not using concurrent licensing then perhaps that is part of the issue?Derek Read February 4, 2019 at 10:07 pm
Reply To: XMetaL 12 enterprise repair issueFebruary 4, 2019 at 10:07 pmParticipants 0Replies 2618Last Activity 1 year, 10 months ago
This user will need to run the full (EXE) installer package again as the temp files that it unpacks (the MSI and other files) have been deleted from the system after the last time they ran it.
The EXE we provide is a self-extracting archive that unpacks a large number of files to a temp folder (by default the folder you have shown in the screen capture), effectively unpacking what used to be shipped out to users as a CDROM (and something you can still burn onto a CD if you want to back it up and share that around, though not many people have CD drives any longer). Once it has been unpacked the actual installer runs. If those files are deleted then a repair is not possible without re-running the full (EXE) installer package.Derek Read January 31, 2019 at 12:26 am
Reply To: XMetal Author 10: Entering Attribute ValuesJanuary 31, 2019 at 12:26 amParticipants 0Replies 2618Last Activity 1 year, 10 months ago
I recall this bug. It was introduced sometime between version 8 (?) and 10 and was corrected sometime between version 10 and 13, though I'm not sure exactly when. I think it was introduced with version 8 because of a conflict with the new feature added that slides windows out of the way (“pin” and “auto hide”).
I've tested the behaviour in 13 (current release) and see the expected behaviour.
A value entered in the Attribute Inspector should be set when you perform the following actions:
– move to a different attribute (in the Attribute Inspector) for the same element using the mouse or tab key
– press enter
– put focus back into the same document using the mouse
– put focus into a different document using the mouse
Pressing the Esc key will return to the document without setting the attribute.
Note that this applies to setting values directly in the Attribute Inspector only. If an attribute is set in a form (even one launched from the Attribute Inspector) the logic for how attributes are set is contained entirely within the form and may vary depending on the customization and how the form was designed to function.Derek Read January 10, 2019 at 12:13 am
Reply To: Controlled Drop-Down Lists for Attribute Inspector othermeta elementJanuary 10, 2019 at 12:13 amParticipants 0Replies 2618Last Activity 1 year, 10 months ago
The feature does not exist in version 12, it was added in 13, so…
Unless there is some technical reason (reliance on 3rd party integrations is really the only one) for not upgrading that's still your best option I think. Clients with “maintenance” (which is every customer we have aside from very specific exceptions) can upgrade for “free” (that's actually what you pay maintenance for), if cost is the concern.
Another technical reason for not upgrading of course would be that your company has tested version 12 and is happy that it is stable with everything else you are doing (not necessarily 3rd party software but processes, configuration settings, etc) and that upgrading might be considered a risk.
If this feature is important I would recommend testing it in the trial version to see if it meets your needs, then perhaps check to see if you can (ie: your organization “allows” it) to upgrade to 13.
Antenna House is a partner* and what they are showing on that page (the one you have referenced) seems to be the existing functionality for working with subject schemes in the Japanese edition of XMetaL Author Enterprise 12. If anything, support in 12 (Japanese edition and the regular edition that you have) would be limited to (I believe) editing files that use the subjectScheme.dtd. XMetaL Author can handle any DTD, so that would have been possible as soon as that DTD existed, though having XML template as a starting point makes it easier too so maybe we included templates in 12. It doesn't have any of the actual support for subject schemes, ie: using the content of a subjectScheme saved in one file to work with attribute values in a topic or map (which is the feature added to 13).
* We provide support for Antenna House Formatter as part of our integration with the DITA Open Toolkit to produce PDF using that engine — the “deliverables” for that in our UI are listed as “PDF via Antenna House Formatter and PDF5-ML plugin” and “Antenna House VIA PDF2” (and possibly other names in releases older than 13).Derek Read January 8, 2019 at 9:04 pm
Reply To: Controlled Drop-Down Lists for Attribute Inspector othermeta elementJanuary 8, 2019 at 9:04 pmParticipants 0Replies 2618Last Activity 1 year, 11 months ago
That forum example should work in versions up to 13 (and continue to work thereafter). In general, customizations for older versions will continue to work for newer ones (provided APIs are used in the way they were designed). However, for DITA, and because you are asking specifically about subject schemes, I don't think that's the best option. For non-DITA DTDs I would still recommend that demo as a starting point (but see “Non-DITA” below). The DITA authoring customization also does not generally support this level of modification (as it is easy to break existing features when adding script).
DITA Subject Schemes:
Your best option might be to upgrade to XMetaL Author Enterprise version 13. In version 13 we added support for working with DITA subject schemes. You can create them (as a DITA document), manage them, and attach them to maps and topics. Once you have attached one to a document the values for that scheme are listed in the Attribute Inspector for the particular attributes defined in the subject scheme. The resulting UI is the same as you see for an attribute with enumerated values (ie: when the DTD defines an enumerated list of values for the attribute and not simply CDATA). If you download the trial version from the xmetal.com website you will get the current release (which is as of this posting version 13). Two new items appear on the Reuse menu (“Apply/Remove Subject Scheme” and “Show subjectScheme Manager”) and the documentation discusses the feature as well. If you try this feature, I would recommend using the example subjectScheme listed in the DITA documentation for the
topic to start with (this is accessible via our F1 help, just search for “subjectScheme”).
If that post's example looks like it would help then base whatever you want to create on it. The form will need modification to match the attribute and it's values, and you might want to trigger the form another way, perhaps by letting the user double click on the element, select it from a toolbar/menu, open it with a shortcut key, etc.
Another option (assuming you have control of / permission to modify the DTD or W3C Schema) is to modify the attribute to be an enumerated list. In this case the Attribute Inspector will list only those values allowed by the DTD or W3C Schema. Of course, this pretty much rules out DITA specialization as it suggests basing new attributes on @props and @base, which are themselves CDATA.Derek Read December 3, 2018 at 8:07 pm
Reply To: Schematron validation produce empty box in XMetal 11December 3, 2018 at 8:07 pmParticipants 0Replies 2618Last Activity 2 years ago
This feature was completely rewritten for version 13 (after a lot of negative feedback on how poorly it functioned for most people in version 11 when it was first introduced). So, if you need it, I would highly recommend running XMetaL Author Enterprise or XMetaL Author Essential 13.
The help in version 13 has been updated as well. It provides more detail, including specific information about the versions of the various components that drive the feature and the various options available.Derek Read November 13, 2018 at 8:34 pm
Reply To: XMetaL12-Documentum DFS Single Sign-On SSONovember 13, 2018 at 8:34 pmParticipants 0Replies 2618Last Activity 2 years ago
The XMetaL QA team has not attempted to test such a setup and development has never worked with this. I currently do not know if this functionality is meant to “just work” without additional code added to our software or whether we need to implement something for this to function.
What I can say is that if we do need to add code to the XMetaL Author Enterprise for Documentum connector for this feature to function that would need to be in a future release.Derek Read November 10, 2018 at 12:17 am
Reply To: topic with schema reference gives "Path not found" (Solved)November 10, 2018 at 12:17 amParticipants 0Replies 2618Last Activity 2 years ago
Is this issue reproducible with the Journalist sample for you?
I can't seem to reproduce it, or I misunderstand the issue.
1. Select: File > New > Journalist (tab) > SchemaArticle (template)
2. No errors.
I would recommend sending a sample of any files needed to reproduce this issue to XMetaL Support so they can test with the same setup you have.Derek Read November 10, 2018 at 12:11 am
Reply To: Need Help on Xmetal Version selectionNovember 10, 2018 at 12:11 amParticipants 0Replies 2618Last Activity 2 years ago
The first version of XMetaL Author to support Windows 10 was XMetaL Author Essential 11 and XMetaL Author Enterprise 11. If you need to run an older version of XMetaL Author on Window 10 and you experience problems that appear to be specific to Windows you can try Windows 10's “compatibility mode”.
If Teamcenter 11.2.3 only works on Windows 10 then the ideal situation is to run XMetaL Author Enterprise 11, 12 or 13 (supported on Windows 10). If Teamcenter does not work with those versions of XMetaL Author Enterprise that isn't something we can fix, it is something Siemens would need to address.