Pages: 1 2 3 4 5 6 7 8 9 10
 1 
 on: November 13, 2018, 02:34:56 PM 
Started by raj321 - Last post by Derek Read
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.

 2 
 on: November 12, 2018, 02:55:12 AM 
Started by KdG - Last post by KdG
Thank you for your prompt response.

I soved the issue. It is completely my mistake.
Last week it took me several hours to drill it down to the schema-reference, but it is not that!

! Sorry for bothering you unnecessarily.


(FYI: It had to do with a macro writing the "topic_HTML_Custom.xsl" to the roaming\softquad\..\display folder.)

 3 
 on: November 09, 2018, 06:54:41 PM 
Started by JRP - Last post by XMetaLOldTimer
There is no support for automatic event sink binding via the script engines within XMetaL.  You have to setup things manually and program APIs to receive XMetaL script engine objects. 

Fwiw, we have an old .NET 1.1 sample that demonstrates calling from XMetaL to a .NET control and vica versa....NET calling a Jscript object in XMetaL's script engine.

Regards,
Addam

 4 
 on: November 09, 2018, 06:29:18 PM 
Started by KdG - Last post by XMetaLOldTimer
Are your trying use the DITA XML schemas?  If so, you need to have DITA Options set to version 1.3.  And our out-of-the-box catalogs for DITA XML schemas are setup to match the OASIS DITA URNs such as this example below:


<topic xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
 xsi:noNamespaceSchemaLocation="urn:oasis:names:tc:dita:xsd:topic.xsd"
 xmlns:ditaarch="http://dita.oasis-open.org/architecture/2005/"
 id="topic_A9A9B50EA68A4FFA960272F6F65B7E16">


Regards,
Addam

 5 
 on: November 09, 2018, 06:17:09 PM 
Started by KdG - Last post by Derek Read
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.

 6 
 on: November 09, 2018, 06:11:57 PM 
Started by ashishkilledar2000 - Last post by Derek Read
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.

 7 
 on: November 09, 2018, 03:56:09 PM 
Started by raj321 - Last post by raj321
Hello,

I am trying to configure Kerberos Single Sign-On for Documentum DFS7.3 so that when I launch XMetaL Author Enterprise 12.0 with the URL http://server_name:9080/dfs/services, I am hoping to get logged-in automatically as long as the XMetaL user is a valid Active directory and Kerberos configured user.

I have done the things needed to do from DFS side with the help of OpenText support, but still the XMetaL12 shows up the login screen.

Just wondering if anyone has implemented SSO with above configuration? Any additional code snippet or something need to be added from XMetaL12 side?

Thank you in advance.

 8 
 on: November 09, 2018, 10:20:51 AM 
Started by KdG - Last post by KdG
[This issue has been solved, and appeared to have nothing to do with schema-reference. (see last message)]

We have a serious issue that occurs since XMetaL Author 13.0 x86 (Binary#: 13.0.0.038 Installer#: 13.0.0238)

When you open a file that holds a schema reference, XmetaL gives an unnecessary message "Path not found"
After the message the file opens correctly, and can be validated correctely against the schema.

Steps to reproduce:
1. Create an XML file with a schema reference like:
<topic xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" class="- topic/topic " xsi:noNamespaceSchemaLocation="c:\temp\schema\topic.xsd">

2. Place the schema in the correct location.
3. Open the file in XMetaL.

Where does this message come from, and how can it be avoided?


 9 
 on: November 09, 2018, 12:48:36 AM 
Started by ashishkilledar2000 - Last post by ashishkilledar2000
Hi,
We have a situation.
Customer currently uses Xmetal 9 with Teamcenter 10 on Windows 7

New situation is --- Teamcenter 11.2.3 on Windows 10

As per SPLM -teamcenter product integration information, Teamcenter only lists upto Version 10 for XMetal.
Upto and including Version 10 XMetal works only upto Windows 7.

Here in this case what the way out?? (XMetal version to work with Teamcenter 11 & Windows 10)

Regards,
Ashish P. Killedar

 10 
 on: October 26, 2018, 05:33:33 PM 
Started by bk - Last post by Derek Read
Rows are selected if they are highlighted with a grey-blue colour.
To select rows click to the left of the table at the first row then drag down.

Pages: 1 2 3 4 5 6 7 8 9 10