Shared actions - action\subaction1, action\subaction2, etc?

HCL Domino Domino Forum
1

Hm…

Ok, so now they’re making us use ‘insert action with subaction’ instead using "".

What about shared actions with subactions???

Thanks,

Rachel

2

Subject: Shared actions - action\subaction1, action\subaction2, etc??

Backslashes still work; it’s just that the older method of cascading wasn’t exactly obvious. The “action with subaction” thing was supposed to be a usability improvement.

3

Subject: RE: Shared actions - action\subaction1, action\subaction2, etc??

Actually, backslashes don’t work anymore (you get an error – at least I do).

You can’t make a shared action which is inherently a cascading (sub) action as it sits in the shared actions library/view/area, but shared actions can be dragged into submenus.

4

Subject: RE: Shared actions - action\subaction1, action\subaction2, etc??

Bruce, I don’t know what version you are talking about but they work perfectly in 6.5.1!

5

Subject: RE: Shared actions - action\subaction1, action\subaction2, etc??

Thanks for your posts, everyone!

I am with Bruce on this one. I had 3 shared actions with the labels “Document Options\Approve”, “Document Options\Reject”, “Document Options\Reassign”. Saved the shared options with no error.

When I insterted them into a form though, they came in as 3 separate buttons, labeled “Approve”, “Reject”, and “Reassign”.

The dragging worked though, Bruce. Thank you.

Shiva, shared actions work exactly in 6.5.1 for as they did in R5?

Thanks for your time!

Rachel

6

Subject: RE: Shared actions - action\subaction1, action\subaction2, etc??

yea, my mistake. I might have confused you when I said “they work prefectly”. I was talking about the system accepting backslash() (refering to Bruce’s point that the system gives an error while entering). but you are right that they don’t become sub-menus inherently but have to be dragged.

anyways, it was a good point to discuss and we had something to learn from it. thanks Bruce, Rachel.

-Shiva.

7

Subject: RE: Shared actions - action\subaction1, action\subaction2, etc??

I’m pretty sure that I remember getting the same error message (below) in 6.5.1, but I’m using 6.0.3 today, and here’s what I get:

I’d stay away from using backslashes even if your R6 Designer is allowing them; I’d wonder if they’d cause a problem later. (Probably not; I’m sure that the R6-sub-action-vs-R5-cascading-action paradigm difference is merely the way the client presents the action to the developer.)