<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin-top:0in;
margin-right:0in;
margin-bottom:8.0pt;
margin-left:0in;
line-height:105%;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle18
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:#1F497D;}
span.EmailStyle19
{mso-style-type:personal;
font-family:"Arial",sans-serif;
color:#1F497D;}
span.EmailStyle20
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoNormal">In preparation for the upcoming transition to <b><i>Workday</i></b>, DAS OSPS has been working to bring payroll related security into a more user friendly environment. Part of this change included updating the connection for OSPA Datamart
security on May 30. <o:p></o:p></p>
<p class="MsoNormal">In order to make this update, OSPS sent a message out to Agency Security Officers requesting confirmation of all OSPA Datamart users without OSPA Mainframe access. The intent was for OSPS to update users with existing OSPA Mainframe profiles
through an automated process, while users confirmed by the Agency Security Officer would need to be manually updated by System Security on May 30. However, there were some unexpected issues with the automation which resulted in a loss of access to OSPA Datamart
in several groups.<o:p></o:p></p>
<p class="MsoNormal">System Security has restored OSPA Datamart access to users with an OSPA Mainframe profile and users confirmed by the Agency Security Officer. As directed by OSPS,
<b><u>users without an OSPA Mainframe profile will only be granted OSPA Datamart access with confirmation from the Agency Security Officer</u>.
<u><o:p></o:p></u></b></p>
<p class="MsoNormal">If you could process OSPA Datamart queries prior to May 30 and are currently unable to do so,
<b><u>please contact your Agency Security Officer for assistance</u></b>. They will be able to follow up and submit the appropriate form to allow System Security to restore your access.<span style="color:#1F497D">
</span>A list of your agency’s Agency Security Officer can be found here:<span style="color:#1F497D">
<a href="https://www.oregon.gov/das/Financial/Acctng/Documents/Agency_Security_Officer_Contact_List.pdf">
https://www.oregon.gov/das/Financial/Acctng/Documents/Agency_Security_Officer_Contact_List.pdf</a></span><o:p></o:p></p>
<p class="MsoNormal">Thank you for your patience during this update.<span style="color:#1F497D"><o:p></o:p></span></p>
</div>
</body>
</html>