 | basenine 12/21/2013 2:30:31 AM Hi Nathan - just thinking...is it possible to have a Custom Rule on the User table Property? I've had instances where I've tried something, expecting it to not really work because of the security/user role...but it can sometimes open up when it needs to, then close back up again.
The other option/workaround would be to open it up for them to modify, then use Form behaviour and User roles to make them either hidden or readonly where required. I agree - this method is a workaround rather than what you're after.
|
| basenine 12/21/2013 3:57:03 AM When I say User table property...I don't mean the User Property table..I mean the affected table, using the Manage access for Table Records....then the Allow Modify via Custom Rule. Just so it's clearer! 😉
Definitely worth a shot
|
 | Liquid Rapid 12/21/2013 12:06:39 PM Thanks for the thoughts. Yeah, I can use a Custom Rule to Allow Modify conditionally. But that still opens up the Edit button.
What you said above - control the form with behavior - is what I'm doing now. Like you said, it's a workaround.
1) I think it's a little confusing for users to hit Edit, and find they can't edit anything.
2) If I have a huge number of columns on the form, setting this up is time-consuming.
|
| basenine 12/21/2013 4:39:53 PM ah - yes...I see. I just tried too and was able to do a custom rule on the user at the table level - this obviously hides the Edit button...but then the custom Button doesn't show...
I just tried Action scripting too - and this will work for you - yay.
1) Go to Custom Actions
2) Create New - Select Modify "XYZ"
3) Call the new Action "Edit"
4) Select "Replaces Standard Action"
5) Go back one page (You'll see your New action here and it will look like this; Edit: Modify XYZ)
6) Go to Actions access and de-select who you don't want to have access to.
What I'm thinking this does is it will show table XYZ that there are 2 Edit buttons - the one you created overrides the built in one. Then when you hide it's access, it won't show for that role.
The Workflow buttons still show and they work - I just tried it and got it to work 😉
Cheers
|
| Liquid Rapid 12/21/2013 5:07:30 PM Thanks again for the idea. I actually used to do that with Custom Actions. (Along with other cool things!)
But they've been deprecated, so I'm not using them any more. I really need a way to do it without Custom Actions.
|
| basenine 12/21/2013 5:24:14 PM Why should they be avoided? I was unaware...
|
| Liquid Rapid 12/21/2013 5:29:32 PM Custom Actions were always something that needed to be activated specially. My understanding is that they were experimental, and never released generally.
ForeSoft has told me that they're trying to avoid the use of Custom Actions. I suspect they may take them out completely one day. They're the only thing left that's tied to the old form layout. Who knows what changes to forms will come that won't make sense for the old forms.
|
| basenine 12/21/2013 5:39:41 PM Yes - I noticed that the default form displayed in the old format.
I've got quite a bit relying on Custom Actions - a Mass record Create (a Picklist for a Bill of Materials - on two different tables), hiding "Add Similar" on a few Tables...
|
| Liquid Rapid 12/21/2013 5:47:50 PM I don't anticipate they'll wipe them any time soon. I think they just want to avoid enabling them for new people.
My guess is they'll make the things you can do with them available in new functionalities over time, and eventually get everyone completely moved over.
Bottom line for me is, I want something that works in any application, current or new, on dbFLEX or the main TeamDesk platform. So Custom Actions are out for me.
|
| basenine 12/21/2013 5:48:49 PM Yep - makes sense
|
| basenine 12/21/2013 6:03:10 PM So really, what you need is an enhancement and revamp of the Action Scripting to allow the new form layout (and other sophisticated, easy to setup functions) and a commitment that Custom Actions won't be deprecated?
|
| Liquid Rapid 12/21/2013 6:08:25 PM No, that's more than I need.
All I really need here is either:
1) Some way to enable Custom Buttons when Modify is disabled.
or
2) Some way to disable the Edit button when Modify is enabled.
Either of those little features would satisfy it.
|
| basenine 12/22/2013 6:59:25 PM I'm still thinking about this for you!
Firstly, let me apologise for teaching you how to suck eggs, above!! hahaha 😀
Secondly: Have you tried setting up a view for the people that you don't want to edit the record directly, and then uncheck the Edit (and View if required) in that view and add the Workflow Button in it's place? You could do either a Multi Edit or Table View button. So obviously, you allow them to be able to edit the record in Table Management, but then only show them views. The drawback is you can't see the View or it's related records without still seeing the Edit button.
Dunno - might get you out of a jam in some way.
|
| Liquid Rapid 12/22/2013 9:47:13 PM Yeah, that wouldn't work for me. I do need the view form available.
|
 | Kirill Bondar 12/23/2013 2:16:39 PM We are planning to extend table access rights with options to hide add similar/edit/print/send/export buttons - per user role.
|
| Liquid Rapid 12/23/2013 2:21:39 PM Awesome, Kirill! Thanks. I can use all of those abilities.
|
| basenine 12/23/2013 4:14:38 PM That was easy! lol
|
 | Slava Shinderov 12/25/2013 6:57:32 AM |
