Documentation - Permission Set "Activities"

Hi @Mathias Dahl, 

See my previous post here which ended up as this post after I entered an Internet Support Center “Request Case”.  As you can see, my post has nothing.

I’m aware of and have reviewed Foundation1/040_administration/210_security/020_permission_sets/reference_itd/ feature_activities.htm   Those have links within the application and can be understood via context.  What I’m trying to understand are the other 2/3’s, the activities which aren’t listed on the Foundation1 page.

My goal is to understand the tools I have as the Permissions Sets Administrator.  For example, a while back I spent 7 hr.s in trial and error testing until I found the four Activities necessary to solve:  “The URL ( ) of IFS Enterprise Explorer Feature for MS Reporting Services is incorrect or needs to be set”.   Management found it hard to believe I had to “Trial and Error” because there is no backing (Help) documentation.

Grouping Activities by Components we find a Document Management folder with over 45 activities.  As far as I can tell, there is no way to understand what each does or allows short of trial and error testing.  There are many folders like this, full of “mystery” activities.

• IFS training doesn’t cover this
• IFS training materials don’t cover this
• IFS HELP (F1) doesn’t include these activities
• These Activities do not have no associated link to follow
• These Activities are not list on  Foundation1/040_administration/210_security/020_permission_sets/reference_itd/ feature_activities.htm

Again, my goal is to understand the tools I have as the Permissions Sets Administrator, in particular,  those activities which aren’t listed on the Foundation1 page mentioned above.

Thanks, Troy

Hi, sorry for the late follow-up.

Like Nipun said, some, or many I would say, of those activities, are really technical building blocks in certain flows in IFS. They are not documented since, in general, they are not meant to be used by anyone that R&D. If we could we would actually hide them, but we can't do that the way that concept is built.

Having said that, it's of course important that, if you want to grant some functionality to a user in IFS, you should not have to guess how to do it.

I do not speak for all of R&D now (because I only work with some areas), but the approach we have taken for our different Attachments (which uses activities as the underlying API), for example, is to have pre-made permission sets, with good names and descriptions, such that you don't have to guess what activity to grant. In some cases perhaps we have solved the problem by documentation as well.

So, as Nipun said, let's discuss instead what use cases you have where you had to guess, and solve that the way we meant it to be solved (pre-made permission sets or specific documentation).

Or to put it in another way: if there is a feature you want to grant to users which you don't understand how to grant, and if we are not telling you via pre-made permission sets or documentation, report a case about it and we will either help you in the case itself, or make a new permission set or add some specific documentation.

Or, of course, ask your specific question here.

Thanks!
 

If it happens again, let's discuss here. It does not take much effort.

We're not going to document those that are not already documented, sorry. The names of them will have to be enough for you.

We need to focus on outcomes here, not to understand every little technical part of IFS. There are a lot of technical parts we could document in theory (all PL/SQL APIs, for example) which we don't. It would not hurt but it would probably also not be something that brings benefits to many, and it would mean we can spend less time on more important things.

Is there currently some feature or functionality in IFS that you need to grant your users but which you don't understand how to? If yes, let's discuss that.If not, I think we need to end the discussion here.

Thanks for discussing.