Using Callout with browser instance in DCT

When a browser is used as in an instance of an item, it creates a button and this can be used within the boundary of ceiling-dir or at most to the workarea. It can not go beyond it.

Now, when we use Callout as a subelement of browser, it calls an external program. This is outside the workarea. Is not this violation of the bowser limit that it can not go outside the workarea ?
Will it create two buttons (one for browser and one for callout) ?
why would one like to use callout with browser ?

Thanks

Find more posts tagged with

Comments

ISCBorisB

When a browser is used as in an instance of an item, it creates a button and this can be used within the boundary of ceiling-dir or at most to the workarea. It can not go beyond it.

Now, when we use Callout as a subelement of browser, it calls an external program. This is outside the workarea. Is not this violation of the bowser limit that it can not go outside the workarea ?
Will it create two buttons (one for browser and one for callout) ?
why would one like to use callout with browser ?

Thanks

You can use callserver with any instance, browser including. Yes, in this case you'll have two
buttons, "Browse" and "YourButtonLabel". "Callout with the browser" can provide some additional
GUI for the contributor to manipulate images, validate properties and Metadata or do whatever you like.

Migrateduser

Hi,

If needed, you could hide the default Browse button using CSS, therefore only displaying the custom callout button to users.

In TeamSite 7.2.1 for example, you could update the custom.css file in /ApplicationContainer/server/default/deploy/iw-cc.war/base/styles/ by adding something along these lines:

.iw-formspub-replicant-instance div table.iw-formspub-button {
display: none;
}

You may need to use a browser developer tool (like Firebug for Firefox) to help you write the correct CSS selectors.

As that will affect all forms, you may instead want to specify a custom CSS file specific to the DCT(s) you want to affect, and add the css attribute in templating.cfg.

Kind regards,

James

Attendace.zip