SHOW SECTION_START Dynamic?

crisg0112

Hi,

I have a form where the user can either choose : 'A' or 'B'

If the user chooses option A, I want my form to display a button.

Can I use
<<IF MyBO.Choice='A' THEN SHOW SECTION_START>>
......
<<SECTION_END>> ??

BenHayat

Cris, if you're talking about dynamically showing contect in an HTML block, then you're close.

<<IF MyBO.Choice='A' THEN SHOW SECTION_START>>
Content to show if "A" was selected
<<SECTION_END>>

<<IF MyBO.Choice='B' THEN SHOW SECTION_START>>
Content to show if "B" was selected
<<SECTION_END>>

crisg0112

BenHayat wrote
Cris, if you're talking about dynamically showing contect in an HTML block, then you're close.

<<IF MyBO.Choice='A' THEN SHOW SECTION_START>>
Content to show if "A" was selected
<<SECTION_END>>

<<IF MyBO.Choice='B' THEN SHOW SECTION_START>>
Content to show if "B" was selected
<<SECTION_END>>

Thanks for replying Ben! Will give that a try

crisg0112

still not working.

The button needs to show on the same form where the choices are.

I am expecting the button to appear under the 'Reason' attribute.

BenHayat

crisg0112 wrote
still not working.

The button needs to show on the same form where the choices are.

I am expecting the button to appear under the 'Reason' attribute.

Well, you had provided very limited info to work with.

tford

Cris,

I'm not seeing the images you tried to post. Not sure what you are trying to accomplish.

crisg0112

oops.. here is the image

If the user select Approved, then a button will appear at the bottom of the Reason attribute.

tford

Still can't see the image.

crisg0112

tford wrote
Still can't see the image.

just attaching the file 🙂

Rennur

My experience is that "SHOW SECTION_START" "SECTION_END" is only to be used in Document Generation .
I use it in all my HTML reports.

In forms, I use the "Separators" and define CONDITIONS (within separator options) to specify when they are visible or not.

Cheers

crisg0112

Rennur wrote
My experience is that "SHOW SECTION_START" "SECTION_END" is only to be used in Document Generation .
I use it in all my HTML reports.

In forms, I use the "Separators" and define CONDITIONS (within separator options) to specify when they are visible or not.

Cheers

Thanks Rennur. Issue with Separators is that there is a 'rectangle' around the buttons.

Have to find another way of displaying it then

Rennur

Are these HTML buttons?
Create a Plain Text Attribute (max length 32,000 or so) for each of your buttons, in the description, paste your button HTML code.

Place the attribute on the form, hide label and show description on the right. The button will work with Appendix D. Links. And other's like save form etc.. (there is a forum post on javascript links)

Then use READ PROTECT rules to hide/show buttons on the form depending if Accepted/Rejected.

tford

Wow, that's genius Rennur!

crisg0112

Rennur wrote
Are these HTML buttons?
Create a Plain Text Attribute (max length 32,000 or so) for each of your buttons, in the description, paste your button HTML code.

Place the attribute on the form, hide label and show description on the right. The button will work with Appendix D. Links. And other's like save form etc.. (there is a forum post on javascript links)

Then use READ PROTECT rules to hide/show buttons on the form depending if Accepted/Rejected.

Thanks Rennur! Learned another thing today

hpl123

Great solution Rennur 🙂.

Another solution that would solve this (I think) is using a text attribute called e.g. "ButtonX" and then use BO rules to populate this attribute with the HTML CODE per choice (i.e. if the user selects choice Approved, the system populates the attribute with the HTML CODE for the button. If the user selects choice Rejected, the system populates the attribute with nothing or a html space). Then create a html row on your form with a tag to the ButtonX attribute.

This solution would also enable you to place the button wherever you like (the solution posted by Rennuer would if i´m not mistaken HAVE TO be placed to the right of an existing attribute?).