nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Disable DCR buttons

mansirastogi

Hi
I am new to Teamsite, my requirement is to disable the DCR buttons (Generate and Save As).
I have gone through the Form publisher guide and know that there is a way to hide them, but couldn't find anything about how to disable them.
Can anyone suggest what to do to disable them.

Teamsite site version : 6.7.1, Solaris 10

Thanks
Mansi

Find more posts tagged with

Comments

Faizi

Hi
I am new to Teamsite, my requirement is to disable the DCR buttons (Generate and Save As).
I have gone through the Form publisher guide and know that there is a way to hide them, but couldn't find anything about how to disable them.
Can anyone suggest what to do to disable them.

Teamsite site version : 6.7.1, Solaris 10

Thanks
Mansi

You have to just go to templating.cfg file and find that data type. Now add the following code:
[HTML]

[/HTML]
actionlist: Lists the links that display on the data form. The valid tokens are separated by a semicolon (, ). Valid tokens are save, saveas, preview, generate, settings. If this attribute is not specified, all links appear at the top of the form.
For more detail go through the Form Publisher Developer Guide.

mansirastogi

thanks Faizi

But as i mentioned, i dont want to hide them but to disable them, is there any way we can disable these buttons.

Thanks
Mansi

Faizi

thanks Faizi

But as i mentioned, i dont want to hide them but to disable them, is there any way we can disable these buttons.

Thanks
Mansi

If you want to show it and make disable then whats the meaning of it there??

You can disable (restrict) on user's role basis. For this you need to customize the TS UI.
Do you have knowledge of TS Customization? If not go through the Teamsite Customization Guide.

Adam Stoller

thanks Faizi

But as i mentioned, i dont want to hide them but to disable them, is there any way we can disable these buttons.

Thanks
Mansi

Nothing that is fully supported comes to mind - why would you want them disabled rather than hidden? I cannot understand the rationale for this (I could understand it in the reverse situation - if OOTB supported disabling and you wanted them hidden instead)

mansirastogi

This is a client requirement, they want buttons to be disabled rather then hiding them.

Thanks
Mansi

Files.txt

Adam Stoller

This is a client requirement, they want buttons to be disabled rather then hiding them.

Thanks
Mansi

You might be able to do this in a semi-supported way by modifying the CSS for the Edit DCR form - however it might be easier / quicker / better to just convince the client to let them be hidden instead of disabled....

Faizi

You might be able to do this in a semi-supported way by modifying the CSS for the Edit DCR form - however it might be easier / quicker / better to just convince the client to let them be hidden instead of disabled....

I am totally agree with Ghoti's suggestion. So, try to convince the client to real scenario.

Valentine

Have you tried adding the onPreview and onGenerate handlers and just
bailing out?

Adam Stoller

Have you tried adding the onPreview and onGenerate handlers and just
bailing out?

It's a little more complicated - because they want to disable Generate and SaveAs - and they want the items to appear grayed-out - not just non-functional.

Personally, I don't understand why they don't want the buttons removed from the interface if they're going to be inactive - but that's apparently the requirement that mansirastogi is attempting to support ...

ISCBorisB

It's a little more complicated - because they want to disable Generate and SaveAs - and they want the items to appear grayed-out - not just non-functional.

Personally, I don't understand why they don't want the buttons removed from the interface if they're going to be inactive - but that's apparently the requirement that mansirastogi is attempting to support ...

It gets even better. DCT "buttons" are in reality just cleverly formatted standard HTML anchors. In the DOM Model anchor
object does not have a "disabled" Property. So, what they want to do can not be done even with the reasonable hacking
like CSS Modifications or "Find and change Property" from FormAPI. Of course one can always create "Grey" counterpart
for the buttons' images and start modifying Vendor's JSPs - waste of time IMO.