I recently upgraded from OTRS 2.2 to OTRS 3.1. The new user interface is awesome, but on the overview page both panels "open tickets" and "new tickets" also show tickets already locked by other users (ie. those that are already being handled by other agents).
Is there a way to only show unlocked new tickets and those locked by me?
This is only a partial answer: I know how to make the "open ticket" and "new ticket" widgets on the dashboard to display unlocked tickets. To get the ones locked by you i am not sure.
login as admin and go to admin tab
Click on sysconfig and do a search for "dashoboard"
Choose the "Frontend:Agent:Dahsboard" belonging to group "Ticket"
Scroll down to DashboardBackend###0120-TicketNew (this is the new ticket widget)
Under Attributes add more attributes to meet your needs. For showing only unlocked tickets add "StateType=new;LockIDs=1;" so now you will have all new tickets that are unlocked. use LockIDs=2 for locked ones.
To view other attributes go to API -> OTRS cvs -> Kernel::System::TicketSearch
I do not know how to get unlocked ones && locked by me.
Maybe you can add code to view the owner or locked unlocked status of the ticket in the widget to meet your requirements? If so see here and here
Related
How can I hide the +NEW-Button in a subgrid of activities, when the parent records status is inactive? I tried already to hide this Button with RibbonWorkbench to see if hiding would generally work when I later implement a javascript hide-rule, but the +-Button is still visible. I tried to hide this button on the activitypointer as well as task entity but the +-Button is still visible.
Background: Customer should not be able to add new activities, when the paretn record's status is inactive.
I followed this tip How to unable create a new record button from sub grid but withou success.
Customer should not be able to add new activities, only view them
If you remove the create privilege for an entity in that user persona security role, then the Add New [+] ribbon button will be hidden automatically. That’s the right approach.
I am setting up a report on a page with multiple checkbox page items and start and end date page items. The user clicks a 'Run Report' button to generate a report region below on the page.
The default selections for the checkbox items are all items selected, and the Start and End Date items have default options based SQL queries.
I want to the report region to hide on the initial page load, and then show once the user clicks 'Run Report'. I tried the following solutions:
Set region condition to 'Never' and then use a dynamic action to show the region once the button is clicked. However, I think the 'Never' condition trumps the dynamic action.
Create two dynamic actions, one on page load to hide the region and on clicking the button to show the region. However, the show DA is always overwritten once the page loads again because of the first hide dynamic action, so the region never displays.
Has anyone else run into this problem? Any solutions? Thank you!
You may like to consider the 'lazy loading' described on Maxime's blog.
https://askmax.blog/2018/05/18/lazy-loading-report/
Like you said, a server side condition will trump and DAs that are showing/hiding on the browser, as the region would never render.
If you want to hide something on entry, you can do something similar to what you described, but I'm not quite sure what you've done.
on load dynamic action to hide region (or add
style="display:none;" to custom attributes of region.)
on click of your button, show the region (do not run on initialisation), and
refresh the region.
I want to create a list in SharePoint 2013 that can be access by multiple users but shows to each user their records only.
For example: Time and Attendance list to show the records of the user only. And only the managers to view all the records.
In this case each list item would need to stop inheriting permissions from the parent and only assign the permissions for those that can edit and read the record.
Are you trying to do this through the UI or Code?
To do that that through the UI do the following:
1. From the list view, click the ellipses for the list item
2. Click Shared With -> Advanced
3. Click "Stop Inheriting Permissions" in the ribbon
4. Remove/Add the permissions you need
You can create a view on the list and add filter to show only items for the current user only.Sample:1
Or if you want to display only the items that were created by the user. Go to List settings > Advanced settings and set the item-level permission. Sample: 2
If you using SharePoint Designer 2013.
1) Create a SP2010 Workflow Called "Set Item Level Permission"
2) Trigger = When Item Created/Change
3) Add "Impersonation Step" -> Replace "Read/Write" permission to Current Item.
4) in your list item, you can select multiple people picker field to grant them with different permission when item created/change.
Example: "Name of Employee" is a people picker for my case.
for Manager, you can hardcode the "Manager Group" (sp group)
I'm trying to find out if I can determine if and when a Sitecore item was published / un-published.
Some background: The issue was that an ECM recipient item in Sitecore was not published, preventing an ECM email from being sent. We've been told they have been sending emails using this recipient item, so I'm trying to determine if it was ever published, and if it was, then when it was un-published.
So far I've had a look in the PublishQueue, EventQueue, and History tables on Master - but couldn't see anything obvious - also couldn't find anything obvious in the logs by just searching on the item ID.
Cheers,
Henry
You could add the Publish Status of items to the Gutter.
Here is how: How to flag new items as unpublished items?
I think there are many options.
"Publishing Viewer" in "Publishing" tab
"Log Viewer" to see details
If you use workflow for items, check your "Work Box" if there is any queues.
It seems like when you delete an item it happens right away without going through workflow or anything. Is that right? Additions and edits I understand. But is there anyway to "mark an item for deletion" so that the next time there is a publish it will be deleted?
See the following blog post from John West -
"Manage Publication of Deletions with the Sitecore ASP.NET CMS"
I think you have to publish the parent item. This will publish the deleted status of child items but won't publish changes to sub items. Unfortunately I can't find any documentation confirming this but it seems to work for me…
I don't know how to reject deletions, but they should be visible in the Recycle Bin and can be restored from there (go into the SiteCore shell, click the sitecore menu and select Recycle Bin).