What

On the evening of January 3rd, 2018, IAM enabled the Duo “remember me” function.  Duo users will now see a an optional use “remember me” checkbox on the Duo screen.  This sets a browser cookie that allows the Duo event to be remembered for 12 hours.

Since the remember me function is a browser cookie, it does not apply across different browsers or across private and non-private browsing windows.  The remember me function does not apply to password changes or the Duo device management console.

When

January 3rd, 2018

Note

If a user has enabled “auto-push” they will need to hit cancel on the blue bar at the bottom of the screen in order to access the remember me checkbox.  As long as the cookie is not deleted, the remember me checkbox will remained checked on future authentication events.  This issue with auto-push and remember me is the number one Duo related call at peer institutions who have enabled this feature.

Documentation

An KB article has been created in TeamDynamix for this feature, and a possible snag that customers could run into. That article is INTERNAL only at this point.

https://oregonstate.teamdynamix.com/TDClient/KB/ArticleDet?ID=45759

All

The “forms” within TeamDynamix have been updated so the “ticket type” is read-only.

This means when you create or edit a ticket and select “form”, the ticket type will be pre-populated and NOT editable. That will also load the attributes for that particular ticket type. Example – application/software support will load an attribute called Application/Software name(s). Filling out the attributes on the tickets will help us improve further.

Reminder – select a “form” when creating or editing a ticket, that will load/show the ticket attributes for that specific form/type.

All

TeamDynamix is seeking feedback about search in the Client Portal and the Tickets application.

OSU is on a customer focus group to help improve the search capabilities within TeamDynamix.

TeamDynamix is requesting the following information / assistance.

“We would also like your help identifying examples that we will use in our testing if you participate.

3 examples for Client Portal Search

• What text did you search?
• Where were the search terms included in the top several returned items?
• Where were the search terms included in the expected results?
• Did the expected result return at all? If it did, how far down the list was it?”

3 examples for tickets search

• What text did you search?
• Where were the search terms included in the top several returned items?
• Where were the search terms included in the expected results?
• Did the expected result return at all? If it did, how far down the list was it?”

I would appreciate any assistance you can provide with this investigation.

Please e-mail any examples you have for search within the Client Portal (KnowledgeBase, Services, etc.) to lucas.friedrichsen@oregonstate.edu

If you have any other feedback related to search, that would be appreciated also.

Feedback by Wednesday August 30, 2017 at 5pm please so that can be provided to the vendor.

Thanks.

What

Status “closed as junk” changed to “Junk e-mail – closed”

When

Monday, July 31, 2017 – 10:10am

Why?

More clear name, doesn’t indicate to a customer that their request is “junk’.

Group on board – IS Change Advisory Board

As of July 17th, the IS Change Advisory Board has been on-boarded to TDx.

The Drupal webform to submit changes to the IS CAB has been replaced/updated with a TeamDynamix form.

What this means?

• Intake for the IS CAB is now through a TeamDynamix webform
• Eventually tasks or approvals on existing TDx tickets might route to the IS CAB

The IS Change Advisory Board reviews “Significant” changes and provides feedback to the requestor to minimize potential disruptions to IS services delivered to the OSU community.