Overriding the browser-client redirect on Forms Services

[infopath]

Hello,

My question is regarding the Forms Services smart-client detection and redirect,
when accessing a published xsn with or without InfoPath installed.

I have a custom aspx page, hosted on Forms Server 2007, that re-hosts the
XmlFormView web control. I would like to provide a similar user experience
to the default behavior provided by Forms Services, but when a client without
InfoPath attempts to access the xsn, the client should redirect to my custom
page, instead of the default _layouts/FormServer.aspx.

Is it possible to configure Forms Services to do this? Or is there some other
way...?

Thanks,
j

 

[Madhur]

but when a client
without InfoPath attempts to access the xsn, the client should
redirect to my custom page, instead of the default
_layouts/FormServer.aspx.

Hi

Can you tell me what are you trying to acheive? A client doesnt need to
have infopath installed to access xsn form via FormServer.aspx. XmlFormView
control itself uses FormServer.aspx to render infopath forms. Why are you
providing two scenarios which are itself same??

Hope it helps

 

[infopath]

Madhur,

To provide some background - I have an existing rich client InfoPath solution
based on a custom task pane.

What I hope to achieve, is to provide the same rich client functionality
to non-InfoPath users as well as those that have InfoPath installed. Since
custom task panes are not available in the browser environment, I have re-implemented
the task pane's functionality in my custom aspx page.

So esentially, we have two usage scenarios:

1. Where the user has InfoPath installed. When the user clicks a link to
the published xsn, InfoPath launches and the user can utilize the custom
task pane.

2. Where the user does not have InfoPath installed. When the user clicks
a link to the published xsn, their web browser is redirected to my page that
hosts the XmlFormView control, along with other stuff.

Ideally, I would like to configure a redirect URL that is specific to an
InfoPath form template, either within the xsn itself, or as a setting on
the forms library.

I assume that a driving factor for Microsoft's providing the ability to re-host
the web-based forms editing environment in a custom page, is that the default
page does not provide all of InfoPath's rich client functionality. Things
like custom task panes and app-level add-ins are clearly not available on
FormServer.aspx. Given this, it stands to reason that it should be possible
to extend the client-detection feature to redirect to a custom page that
_can_ provide substitutes for some of these rich client capabilities.

Thanks again,
jk

 

[Ben Walters]

Hey JK,
I understand what your trying to do the only suggestion I could make would
be to modify the FormServer.aspx on the server to do a basic redirect to
your form. You would have to back this up first incase of any corruption
also I'm not sure if this would then take affect gloabally throughout form
services.

I'll see if I can have a look into it and I'll keep you posted with what I
find

Cheers
Ben