Lotus Notes :
We have a support Department that use the support agents in the actions Agent list, and they also have access to use Other Agents with editors access.
The problem is the users/clients have the same access as support and can also see and make use of these agents, which we don't want to allow. I had a look at the agents security options, and know that you can set the access to an admin group or person within the access control.
What I am not sure about is by not allowing the users to have access to these agents, and some features on the forms or views calls one od the agents, would it prevent the functionality from working ? and if so, does any one know about a work around ?
Don't put the agents on the Actions menu. I.e., set them to "Agent list selection" instead of "Action menu selection".
Then create a mechanism that can launch the agents but can only be seen by the admin group. For example, create View Actions that use #Command([RunAgent];"agent nanme"); and set up a hide-when formula in the properties for the Actions - something like (!#UserRole = "[Admin]"). If you don't like that option, you could create a Page that is hidden from regular users, and turn that page into a menu for the admins, using hotspots or buttons to trigger the agents.
Related
I cannot find a way to do this in the UI: I'd like to have distinct query tabs in the BigQuery's UI attached to the same session (i.e. so they share the same ##session_id and _SESSION variables). For example, I'd like to create a temporary table (session-scoped) in one tab, then in a separate query tab be able to refer to that temp table.
As far as I can tell, when I put a query tab in Session Mode, it always creates a new session, which is precisely what I don't want :-\
Is this doable in BQ's UI?
There is 3rd party IDE for BigQuery supporting such a feature (namely: joining Tab(s) into existing session)
This is Goliath - part of Potens.io Suite available at Marketplace.
Let's see how it works there:
Step 1 - create Tab with new session and run some query to actually initiate session
Step 2 - create new Tab(s) and join to existing session (either using session_id or just simply respective Tab Name
So, now both Tabs(Tab 2 and Tab 3) share same session with all expected perks
You can add as many Tabs to that session as you want to comfortably organize your workspace
And, as you can see Tabs that belong to same session are colored in user defined color so easy to navigate between them
Note: Another tool in this suite is Magnus - Workflow Automator. Supports all BigQuery, Cloud Storage and most of Google APIs as well as multiple simple utility type Tasks like BigQuery Task, Export to Storage Task, Loop Task and many many more along with advanced scheduling, triggering, etc. Supports GitHub as a source control as well
Disclosure: I am GDE for Google Cloud and creator of those tools and leader on Potens team
I would like to have in my OTRS the functionality that when a ticket is in a specific state ("comment") this ticket will not be visible anywhere in Dashboard/Orders for all agents except for the Admin agent.
Is there a way to show/hide tickets based on the TicketState for specific Agents only?
Thank you.
You can build custom dashlets for groups, which show only certain tickets. For this you need to create an xml-File and place it in your Kernel/Config/Files/ directory as it is described in this blog post.
In your case you would need to replace the standard dashlets with custom ones, which exclude the state, which is admittedly a little tedious...
We use SharePoint to allow users to request changes that could be made to our system. When adding a new item to a list, there are certain fields they are required to fill in. We want this behaviour to remain. One of these fields is Release Phase, where we have a list of release phases they can select from. We still want them to be able to select a release phase, however recently the release phase names have been changing and we want to stop users having access to the list settings so they are unable to edit the options shown.
We still want them to be able to contribute to items, just not edit some of the selectable fields we have.
Any ideas of what can be done to stop this?
Thanks in advance!
You need to configure custom permissions on your list to ensure that only a set few people have access to edit the list, but others can edit the items in the list.
If you are fine with users being able to delete these items, you can set their permission to Contribute which will allow them to add, update, and edit list items, but they will not have any permissions to manage the lists themselves.
If you want to avoid deleting items as well, you need to create a new permission level.
So, there are steps to solve your problem.
1.) Break inheritance on the list to give it unique permissions and apply the appropriate permissions.
2.)Create a new permission level to ensure users only have the level of permission that you want for the list.
1.) Navigate to the list settings for the list in question. Choose "Permissions for this list." You should see a button in the top ribbon that says "Stop inheriting Permissions".
Once you have broken inheritance, this list will no longer be affected by permission changes to its parent site. Only the permissions you define on the list will have affect. Select all the permissions that were defined before, and delete them, so that you will have a clean slate to start with.
You can then grant permissions to the specific users/groups you want. If you have a large base of users, you will find it easier to manage and control permissions by groups.
2.) To define a custom permission level, you need to navigate to the parent site that the list belongs to and go the Site Permissions. This will give you the ability to create new permission groups, and permission levels. There is a ribbon option for each. Select permission levels.
Have a look at each of the predefined options, and see if those will suit your needs first. You can click on each permission level to drill down and see all the specific permissions that it gives. If none of the predefined options work, then Add a new Permission Level, and assign the permissions as needed. Then go back to step 1, and assign your users/groups to your newly created permission level.
Ensure that this option is deselected to prevent users from editing list settings
We have a company program designed to help us get control over data. It has feature to group all the application of one Client. If I want to take a look at them I click on the Client and I see a list of all applications made for him. Take a look at the picture below:
I was wondering if Microsoft Access can do the same? If yes where should I start looking?
I did some internet search and no solution found.
That is built in, and it is called Subdatasheet. You have relationships properly set between Clients and Order, for instance, when you open the Clients table you will see such small "+" allowing to view the Orders of the current client. You may have to set the Subdatasheet Name property of table Clients to "Orders" in this case.
If you want to work with forms, you can build a continuous from for Clients, then one for Orders, then insert the Orders subform in the Footer of the Clients form. Access might tell you you can't do this, just ignore, it works.
In Access that would simply be a continuous form with a filter. Typically opened from a list of clients, setting a filter for the applications of the selected client.
Unless I'm misunderstanding the question.
Is there a way to allow users to see workflow, but only allow them to see their own items within the workflow?
This seems like a problem that would be common. You have a large number of content creators and you only would want them to see how their content is moving in workflow, not the content created by others.
Possible (approximate and messy) solution:
The only possibility I could think of would be to turn off rights inheritance so that I could explicitly deny viewing rights to workflow. Then with a custom action in workflow I could explicitly turn on view rights to each item a user submits.
Am I on the right track? I hope not. ;)
Question Clarification:
I want approvers to see everything, but I want authors to open workflow and only see their own items, not dozens of items from other authors.
This is not the default behaviour as the common use of workflow is for an approval process. In that case the approval team would log in and see the items waiting for approval from the authoring team, if they could only see the items they created then they wouldn't see anything at all.
One way I can think of doing this would be to override the codebeside for the workbox application. Take a look at this file Website\sitecore\shell\Applications\Workbox\Workbox.xml and it's codebeside class Sitecore.Shell.Applications.Workbox.WorkboxForm. If you put your own class in here you could probably add all the logic you need to the 'GetItems' method.
Attacking this from another angle, given you want visibility to the authors on if their items have been approved or not, instead of giving them access to the workbox, why not add a customised email action to the approved status (or the approve command) so that the authors receive an email when their item has been approved. You could also customise the email so that it includes a link to the approved item or includes details of the item so that the author can identify the individual item if they have authored multiple items.
There is a sample email action in the Sitecore.Workflows.Simple.EmailAction class in the Sitecore.Kernel assembly that you can use as a base to your customisations.
If you want to make sure that all items are being approved within a certain timeframe, you could also use the ASR shared source module to generate reports on items that have not been approved within a certain timeframe and have it automatically email this report on a regular basis.