BizTalk Server General - BIZTALK 2004 wish list.

Author

BIZTALK 2004 wish list.

TacitTurn

2004-05-18, 1:05 pm

The following is a initial list of
features/enhancement/issues with BTS2004, as promised for
Scott.

1.The code window in orchestrations should be resizable.

2.The orchestrations should be exportable to visio and
Visio should have template to support all of the
Orchestration types. This would make documentation easier.

3.The Orchestration designer should have a zoom facility
and more collapsable areas. Even at 1600 by 1200 I run
out of space too easily.

4. The Orchestrations shapes should be resizable so the
text within them is readable.

5. Something should be done about the memory leak that
occurs each time a compiliation is done. This is
particularly bad for projects with maps and
orchestrations, ie all of mine.

6. Many of the properties should be configurable from
popups, ie the schema selection in map in a map. If the
schema is called
Microsoft.Biztalk.Examples.Contusa.PurchaseOrder it can be
difficult to read the end of the name.

7. The design framework for adaptors is very powerful
which is great when I have time to right a full commercial
adaptor but it takes a considerable amount of effort to do
something simple.

8. Customers I have spoken to I not entirely happy with
the new division of responsibilities between development
and operational use. Previously customers would upgrade
there own schemas and maps, but this is no longer possible
without Visual Studio and an increase base of knowledge.

9. All of the schema properties should be available from
within the schemas designer. Having to drop into notepad
to set them is prone to error, especially if like me you
save the schema as an ascii by mistake.

10. The help is much better in SP1 but many of the
properties and methods are still undocumented.

11. More examples of correlations and convoys are required.

Thats it for today.

Chris Holliday

2004-05-18, 1:05 pm

Thats a Great start! I would also like to add:

12. Business Rules message types should be assigned via a wizard. Its a pain
to open up the orch and copy/paste the message type.

13. Allow variable/message/etc types to be typed in (via a keyboard)
instead of selected from combo-wizard-agig

14. Automatic generation of variables from expression editor (via flag or
other method). If you know that there not there... can't you just create
them for us?

Thanks,

C.

"TacitTurn" <anonymous@discussions.microsoft.com> wrote in message
news:eb4101c43cf0$151a28b0$a301280a@phx.gbl...
> The following is a initial list of
> features/enhancement/issues with BTS2004, as promised for
> Scott.
>
> 1.The code window in orchestrations should be resizable.
>
> 2.The orchestrations should be exportable to visio and
> visio should have template to support all of the
> Orchestration types. This would make documentation easier.
>
> 3.The Orchestration designer should have a zoom facility
> and more collapsable areas. Even at 1600 by 1200 I run
> out of space too easily.
>
> 4. The Orchestrations shapes should be resizable so the
> text within them is readable.
>
> 5. Something should be done about the memory leak that
> occurs each time a compiliation is done. This is
> particularly bad for projects with maps and
> orchestrations, ie all of mine.
>
> 6. Many of the properties should be configurable from
> popups, ie the schema selection in map in a map. If the
> schema is called
> Microsoft.Biztalk.Examples.Contusa.PurchaseOrder it can be
> difficult to read the end of the name.
>
> 7. The design framework for adaptors is very powerful
> which is great when I have time to right a full commercial
> adaptor but it takes a considerable amount of effort to do
> something simple.
>
> 8. Customers I have spoken to I not entirely happy with
> the new division of responsibilities between development
> and operational use. Previously customers would upgrade
> there own schemas and maps, but this is no longer possible
> without Visual Studio and an increase base of knowledge.
>
> 9. All of the schema properties should be available from
> within the schemas designer. Having to drop into notepad
> to set them is prone to error, especially if like me you
> save the schema as an ascii by mistake.
>
> 10. The help is much better in SP1 but many of the
> properties and methods are still undocumented.
>
> 11. More examples of correlations and convoys are required.
>
> Thats it for today.

Tatyana Yakushev [MSFT]

2004-05-21, 5:55 pm

Can you please elaborate on the point 9. What properties are you not able to set from BizTalk Schema Editor?

Thanks,
Tatyana

--------------------
>Content-Class: urn:content-classes:message
>From: "TacitTurn" <anonymous@discussions.microsoft.com>
>Sender: "TacitTurn" <anonymous@discussions.microsoft.com>
>Subject: BIZTALK 2004 wish list.
>Date: Tue, 18 May 2004 08:52:11 -0700
>Lines: 50
>Message-ID: <eb4101c43cf0$151a28b0$a301280a@phx.gbl>
>MIME-Version: 1.0
>Content-Type: text/plain;
> charset="iso-8859-1"
>Content-Transfer-Encoding: 7bit
>X-Newsreader: Microsoft CDO for Windows 2000
>Thread-Index: AcQ88BUX1Sgbzg5qRua91ZHJSZeOXg==
>X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300
>Newsgroups: microsoft.public.biztalk.general
>Path: cpmsftngxa10.phx.gbl
>Xref: cpmsftngxa10.phx.gbl microsoft.public.biztalk.general:15377
>NNTP-Posting-Host: tk2msftngxa11.phx.gbl 10.40.1.163
>X-Tomcat-NG: microsoft.public.biztalk.general
>
>The following is a initial list of
>features/enhancement/issues with BTS2004, as promised for
>Scott.
>
>1.The code window in orchestrations should be resizable.
>
>2.The orchestrations should be exportable to visio and
>Visio should have template to support all of the
>Orchestration types. This would make documentation easier.
>
>3.The Orchestration designer should have a zoom facility
>and more collapsable areas. Even at 1600 by 1200 I run
>out of space too easily.
>
>4. The Orchestrations shapes should be resizable so the
>text within them is readable.
>
>5. Something should be done about the memory leak that
>occurs each time a compiliation is done. This is
>particularly bad for projects with maps and
>orchestrations, ie all of mine.
>
>6. Many of the properties should be configurable from
>popups, ie the schema selection in map in a map. If the
>schema is called
>Microsoft.Biztalk.Examples.Contusa.PurchaseOrder it can be
>difficult to read the end of the name.
>
>7. The design framework for adaptors is very powerful
>which is great when I have time to right a full commercial
>adaptor but it takes a considerable amount of effort to do
>something simple.
>
>8. Customers I have spoken to I not entirely happy with
>the new division of responsibilities between development
>and operational use. Previously customers would upgrade
>there own schemas and maps, but this is no longer possible
>without Visual Studio and an increase base of knowledge.
>
>9. All of the schema properties should be available from
>within the schemas designer. Having to drop into notepad
>to set them is prone to error, especially if like me you
>save the schema as an ascii by mistake.
>
>10. The help is much better in SP1 but many of the
>properties and methods are still undocumented.
>
>11. More examples of correlations and convoys are required.
>
>Thats it for today.
>

--

This posting is provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm

Note: For the benefit of the community-at-large, all responses to this message are best directed to the newsgroup/thread from which they originated.

Wor Tony

2004-05-30, 10:46 am

Set the receive/send locations without having to press the (...) button

Why can't the refresh from within VS be better (I have to constantly right
click on
Management DB and select refresh)

AP
Nottingham - UK

Matthew Roche

2004-06-26, 10:51 am

I'll elaborate on this one, as no one else seems so inclined.

There are directives that can be added to BizTalk schemas, such as the suppress_empty_nodes attribute of the <b:schemaInfo element, that cannot be added directly using the BizTalk Server tools. The only way to do this is to manually edit the XSD file usin
g Notepad.

To make matters worse (to add injury to insult, as it were) all of the XML editors included with Visual Studio will corrupt the XSD files by saving them as ASCII text instead of unicode. There is no warning until the next time you open the file using the
BizTalk schema editor, at which point it is too late. I have personally lost many hours of work because of this...

"Tatyana Yakushev [MSFT]" wrote:

> Can you please elaborate on the point 9. What properties are you not able to set from BizTalk Schema Editor?
>
> Thanks,
> Tatyana
>
> --------------------
>
>
> --
>
> This posting is provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the terms specified at
> http://www.microsoft.com/info/cpyright.htm
>
> Note: For the benefit of the community-at-large, all responses to this message are best directed to the newsgroup/thread from which they originated.
>
>

Sam Vanhoutte

2004-06-26, 10:51 am

> There are directives that can be added to BizTalk schemas, such as the
suppress_empty_nodes attribute of the <b:schemaInfo element, that cannot be
added directly using the BizTalk Server tools. The only way to do this is to
manually edit the XSD file using Notepad.

That would be great, yes. (and there are other attributes too)

> To make matters worse (to add injury to insult, as it were) all of the XML
editors included with Visual Studio will corrupt the XSD files by saving
them as ASCII text instead of unicode. There is no warning until the next
time you open the file using the BizTalk schema editor, at which point it is
too late. I have personally lost many hours of work because of this...

Just open the ascii file in notepad and save it as unicode. Your schema
shouldn't get lost?

Tatyana Yakushev [MSFT]

2004-06-26, 10:51 am

Thank you very much for your reply.

Tatyana

--------------------
>From: "Sam Vanhoutte" <sam.vanhoutte@unilin.com>
>References: <eb4101c43cf0$151a28b0$a301280a@phx.gbl> <Eq#akn3PEHA.1924@cpmsftngxa10.phx.gbl> <9A4F71F8-7FFA-4AF3-
9BA8-9A1F22744FD5@microsoft.com>
>Subject: Re: BIZTALK 2004 wish list.
>Date: Tue, 22 Jun 2004 08:15:20 +0200
>Lines: 17
>X-Priority: 3
>X-MSMail-Priority: Normal
>X-Newsreader: Microsoft Outlook Express 6.00.3790.0
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
>Message-ID: <OzqDLBCWEHA.3596@tk2msftngp13.phx.gbl>
>Newsgroups: microsoft.public.biztalk.general
>NNTP-Posting-Host: net.unilin.com 193.121.62.242
>Path: cpmsftngxa10.phx.gbl!TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP08.phx.gbl!tk2msftngp13.phx.gbl
>Xref: cpmsftngxa10.phx.gbl microsoft.public.biztalk.general:16464
>X-Tomcat-NG: microsoft.public.biztalk.general
>
>suppress_empty_nodes attribute of the <b:schemaInfo element, that cannot be
>added directly using the BizTalk Server tools. The only way to do this is to
>manually edit the XSD file using Notepad.
>
>That would be great, yes. (and there are other attributes too)
>
>editors included with Visual Studio will corrupt the XSD files by saving
>them as ASCII text instead of unicode. There is no warning until the next
>time you open the file using the BizTalk schema editor, at which point it is
>too late. I have personally lost many hours of work because of this...
>
>Just open the ascii file in notepad and save it as unicode. Your schema
>shouldn't get lost?
>
>
>

--

This posting is provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the terms specified
at http://www.microsoft.com/info/cpyright.htm

Note: For the benefit of the community-at-large, all responses to this message are best directed to the newsgroup/thread from which they
originated.