General Discussions

Has anyone had significant issues with iRIS lately?

It seems since November 2022 we have had significant issues in iRIS. Here is a list of what I would deem significant issues we've experienced:

<u1:p></u1:p>

·         Blank pages: Users cannot submit changes back when revising documents. When they click on the revised document link, they receive a blank page.  (Ticket #84624)<o:p></o:p>

<u1:p></u1:p>

·         iRIS is seizing: PIs have been reporting for over 3 weeks the screen will repeatedly flash for a considerable amount of time. They have to close out iRIS at this point. I've seen it occur and the flashing screen will stay for 20+ minutes. The only answer provided was to clear the cookies. This does not resolve the issue for users. This is the answer we've been provided by the support team, "We do not know why this issue is occurring." (Ticket 84130)<o:p></o:p>

<u1:p></u1:p>

·         Cannot approve attachments (IACUC module). Approving documents: The expiration date is greyed out. Tried to approve the document through the Approved Attachments instead. This does not work."Approve Attachment(s)": Information entered does not save. (Ticket 84393)<o:p></o:p>

<u1:p></u1:p>

·         Cannot add a new sponsor. The sponsor type list was gone and when I tried to add it back, the sponsor list data will not save. The response we received from support was, "The data is there and has always been there. Not sure why this did not display at the moment when you viewed this page. We will monitor this functionality for any issues moving forward." The ticket was closed without fixing the issue so study teams still cannot add new sponsors if the sponsor is not found via the lookup. (Ticket 84259)<o:p></o:p>

<u1:p></u1:p>

·         Data not viewable: When reviewing the submission history for an approved study, there was no history in the protocol's submission history file. Here's the response from support, "Protocol data is in the database but not displaying." No timeline on when this will be fixed. (Ticket 84502)<o:p></o:p>

<u1:p></u1:p>

·         Losing form settings: Fields set in the form designer as required get unselected as a required field. This seems to occur each time we take a patch. (Ticket 84279). I've submitted this ticket multiple times with no explanation or resolution provided. <o:p></o:p>

<u1:p></u1:p>

·         Mail merge functionality not working (Ticket 84394). <o:p></o:p>

<u1:p></u1:p>

·        Role access functionality not working. My chair role is set to be able to edit the meeting agenda. However, when the chair tries to edit the agenda, it is read-only. The answer we received is, "Thank you for this update, the ability to edit this section of the meeting agenda is reserved for coordinators or users with IRB Admin rights." I responded, "The individual cannot be a chair and a coordinator since this is a radial selection. And their role is chair. So that does not work. I do not want to give my chair system admin rights. That is not appropriate. If this is an all-or-nothing proposition, then what is the point of the setup role access? The setup role access was designed so we can make decisions on access based on roles. This is what was described in the RFP and during implementation. But based on your answer it doesn't matter what we select in the setup role access area because it has no bearing on setting a role's access. Is that correct? The setup role access area is no longer functioning to define access for each role." This is the answer we received back from support, "Thank you for your concerns, we will relay this to our management team for further evaluation in future versions." (Ticket 83874)<o:p></o:p>

Is anyone else having these types of issues? Have you experienced previous functionality now missing or no longer working? If yes, have you successfully gotten them resolved? If yes, please share how. 

Has anyone had significant issues with iRIS lately?

It seems since November 2022 we have had significant issues in iRIS. Here is a list of what I would deem significant issues we've experienced:

<u1:p></u1:p>

·         Blank pages: Users cannot submit changes back when revising documents. When they click on the revised document link, they receive a blank page.  (Ticket #84624)<o:p></o:p>

<u1:p></u1:p>

·         iRIS is seizing: PIs have been reporting for over 3 weeks the screen will repeatedly flash for a considerable amount of time. They have to close out iRIS at this point. I've seen it occur and the flashing screen will stay for 20+ minutes. The only answer provided was to clear the cookies. This does not resolve the issue for users. This is the answer we've been provided by the support team, "We do not know why this issue is occurring." (Ticket 84130)<o:p></o:p>

<u1:p></u1:p>

·         Cannot approve attachments (IACUC module). Approving documents: The expiration date is greyed out. Tried to approve the document through the Approved Attachments instead. This does not work."Approve Attachment(s)": Information entered does not save. (Ticket 84393)<o:p></o:p>

<u1:p></u1:p>

·         Cannot add a new sponsor. The sponsor type list was gone and when I tried to add it back, the sponsor list data will not save. The response we received from support was, "The data is there and has always been there. Not sure why this did not display at the moment when you viewed this page. We will monitor this functionality for any issues moving forward." The ticket was closed without fixing the issue so study teams still cannot add new sponsors if the sponsor is not found via the lookup. (Ticket 84259)<o:p></o:p>

<u1:p></u1:p>

·         Data not viewable: When reviewing the submission history for an approved study, there was no history in the protocol's submission history file. Here's the response from support, "Protocol data is in the database but not displaying." No timeline on when this will be fixed. (Ticket 84502)<o:p></o:p>

<u1:p></u1:p>

·         Losing form settings: Fields set in the form designer as required get unselected as a required field. This seems to occur each time we take a patch. (Ticket 84279). I've submitted this ticket multiple times with no explanation or resolution provided. <o:p></o:p>

<u1:p></u1:p>

·         Mail merge functionality not working (Ticket 84394). <o:p></o:p>

<u1:p></u1:p>

·        Role access functionality not working. My chair role is set to be able to edit the meeting agenda. However, when the chair tries to edit the agenda, it is read-only. The answer we received is, "Thank you for this update, the ability to edit this section of the meeting agenda is reserved for coordinators or users with IRB Admin rights." I responded, "The individual cannot be a chair and a coordinator since this is a radial selection. And their role is chair. So that does not work. I do not want to give my chair system admin rights. That is not appropriate. If this is an all-or-nothing proposition, then what is the point of the setup role access? The setup role access was designed so we can make decisions on access based on roles. This is what was described in the RFP and during implementation. But based on your answer it doesn't matter what we select in the setup role access area because it has no bearing on setting a role's access. Is that correct? The setup role access area is no longer functioning to define access for each role." This is the answer we received back from support, "Thank you for your concerns, we will relay this to our management team for further evaluation in future versions." (Ticket 83874)<o:p></o:p>

Is anyone else having these types of issues? Have you experienced previous functionality now missing or no longer working? If yes, have you successfully gotten them resolved? If yes, please share how. 

What release of iRIS are you on?  We are on 11.02 and not having any of the issues you report - so sorry to hear about those issues as I agree with you that they are major and should not be just ignored.  We have been talking about upgrading to 13.01 but have yet to get a stable version in our DEV environment so are in no hurry for the upgrade.  Please respond when you have time.  We are all in this together!  Thank you.

Has anyone had significant issues with iRIS lately?

It seems since November 2022 we have had significant issues in iRIS. Here is a list of what I would deem significant issues we've experienced:

<u1:p></u1:p>

·         Blank pages: Users cannot submit changes back when revising documents. When they click on the revised document link, they receive a blank page.  (Ticket #84624)<o:p></o:p>

<u1:p></u1:p>

·         iRIS is seizing: PIs have been reporting for over 3 weeks the screen will repeatedly flash for a considerable amount of time. They have to close out iRIS at this point. I've seen it occur and the flashing screen will stay for 20+ minutes. The only answer provided was to clear the cookies. This does not resolve the issue for users. This is the answer we've been provided by the support team, "We do not know why this issue is occurring." (Ticket 84130)<o:p></o:p>

<u1:p></u1:p>

·         Cannot approve attachments (IACUC module). Approving documents: The expiration date is greyed out. Tried to approve the document through the Approved Attachments instead. This does not work."Approve Attachment(s)": Information entered does not save. (Ticket 84393)<o:p></o:p>

<u1:p></u1:p>

·         Cannot add a new sponsor. The sponsor type list was gone and when I tried to add it back, the sponsor list data will not save. The response we received from support was, "The data is there and has always been there. Not sure why this did not display at the moment when you viewed this page. We will monitor this functionality for any issues moving forward." The ticket was closed without fixing the issue so study teams still cannot add new sponsors if the sponsor is not found via the lookup. (Ticket 84259)<o:p></o:p>

<u1:p></u1:p>

·         Data not viewable: When reviewing the submission history for an approved study, there was no history in the protocol's submission history file. Here's the response from support, "Protocol data is in the database but not displaying." No timeline on when this will be fixed. (Ticket 84502)<o:p></o:p>

<u1:p></u1:p>

·         Losing form settings: Fields set in the form designer as required get unselected as a required field. This seems to occur each time we take a patch. (Ticket 84279). I've submitted this ticket multiple times with no explanation or resolution provided. <o:p></o:p>

<u1:p></u1:p>

·         Mail merge functionality not working (Ticket 84394). <o:p></o:p>

<u1:p></u1:p>

·        Role access functionality not working. My chair role is set to be able to edit the meeting agenda. However, when the chair tries to edit the agenda, it is read-only. The answer we received is, "Thank you for this update, the ability to edit this section of the meeting agenda is reserved for coordinators or users with IRB Admin rights." I responded, "The individual cannot be a chair and a coordinator since this is a radial selection. And their role is chair. So that does not work. I do not want to give my chair system admin rights. That is not appropriate. If this is an all-or-nothing proposition, then what is the point of the setup role access? The setup role access was designed so we can make decisions on access based on roles. This is what was described in the RFP and during implementation. But based on your answer it doesn't matter what we select in the setup role access area because it has no bearing on setting a role's access. Is that correct? The setup role access area is no longer functioning to define access for each role." This is the answer we received back from support, "Thank you for your concerns, we will relay this to our management team for further evaluation in future versions." (Ticket 83874)<o:p></o:p>

Is anyone else having these types of issues? Have you experienced previous functionality now missing or no longer working? If yes, have you successfully gotten them resolved? If yes, please share how.