scope of using DXL in DOORS next G

When would we expect to see some documentation (e.g. DXL API spec or something less formal) that defines the scope of what can be scripted / customised with DXL in DOORS NG?

We make extensive use of DXL customisation for integration with other tools - so understanding the impact of this change will determine when we upgrade.

Regards, Dan Hall

@DanHall you asked:

When would we expect to see some documentation (e.g. DXL API spec or something less formal) that defines the scope of what can be scripted / customised with DXL in DOORS NG?

We understand this is a prerequisite to you being able to consider moving a highly customized DOORS 9 environment to DOORS NG. That's one reason we are focusing on interoperability scenarios in this first DOORS NG release: exchange of data using ReqIF and linking between DOORS 9 and DOORS NG via normal OSLC mechanisms. We hope this will provide opportunities for you and/or your teams to explore DOORS NG with your own data and determine if there are teams, sub-projects, etc that would benefit from DOORS NG even without customizations based on DXL. The answer will vary greatly in different organizations and kinds of projects.

Supporting customer-written DXL is a high-priority item in the DOORS NG product backlog. After we close out this first release and publish plans for a 2013 release you will get a first look at whether that release is likely to give you enough capability in this area. It's too soon to say at the moment (we haven't done the necessary detailed planning yet).

@DanielMoul so is the DOORS Next Generation rich client now available with 5.0.2? Also is DXL now available for customer's to use?

This information is more than 4 years old now, and as far as I understand there is no DNG rich client and DXL will never be available for use. Can some Jazz Dev please confirm?