We hope you'll join us for our 4/23 webinar on using data tables to apply reference ranges and AE codes in OC4. For more information and to register, visit https://register.gotowebinar.com/register/2882170018956684555

Rule does not fire when data is changed in Administrative Editing

Hi,
my PV team requests to be notified by email whenever data is changed on AdverseEvent CRFs after initial data entry. For each section I wrote a rule with an expression like:
var1 ne "" or var 1 eq "" or var2 ne "" or var2 eq "" or ...
I set it up to run only in Administrative Editing to avoid unnecessary emails during Initial Data Entry. However, since Reason for Change is required it seems to overwrite the rule before it even fires. 
Am I doing something wrong or is there another way to receive email notification after initial data entry (preferably without having to set the CRF complete because some study sites are reluctant to do so).
Thanks 
Claudia

Tagged:

Comments

  • tkhajatkhaja Posts: 62 ✭✭
    via Email
    Hi Claudia,

    Please see the following JIRA ticket for more information on this issue.

    https://jira.openclinica.com/browse/OC-3106

    Best,
    Thasbiha

    On Mon, Jun 29, 2015 at 10:20 AM, ctrepte
    wrote:

    > Hi,my PV team requests to be notified by email whenever data is changed on
    > AdverseEvent CRFs after initial data entry. For each section I wrote a rule
    > with an expression like:
    >
    > var1 ne "" or var 1 eq "" or var2 ne "" or var2 eq "" or ...
    >
    > I set it up to run only in Administrative Editing to avoid unnecessary
    > emails during Initial Data Entry. However, since Reason for Change is
    > required it seems to overwrite the rule before it even fires.
    >
    > Am I doing something wrong or is there another way to receive email
    > notification after initial data entry (preferably without having to set the
    > CRF complete because some study sites are reluctant to do so).
    >
    > Thanks
    >
    > Claudia
    >
    > --
    > To manage your email notifications, please visit:
    > https://www.openclinica.com/forums#/profile/preferences
    >
    > Reply to this email directly or follow the link below to check it out:
    >
    > https://forums.openclinica.com/discussion/15690/rule-does-not-fire-when-data-is-changed-in-administrative-editing
    >
    >
  • ctreptectrepte Posts: 100
    Dear Thasbiha,
    thanks for the link which leaves only one question:
    Why is a bug that was discovered in July 2013 (that was almost 2 (two) years ago) still not fixed. The newest version is 3.5. In more that 4 releases it was not possible to fix this? At least I did not see any comment in the issue tracker that the bug was fixed in any of the releases since it was discovered. As much as I like some of the new features I don't think that this is how software development should work.
    Claudia
  • agoodwinagoodwin Posts: 131 admin
    via Email
    Dear Claudia,

    Sorry to hear that your rules aren't working as expected. Thasbiha was
    trying to be helpful in pointing you in a direction to see if you were
    experiencing the same issue or if it was a different one. From the sounds
    of it, you're running into something different but hopefully we can shed a
    little light on that too.
    Regarding the issue that you seem to be experiencing - this happens to be a
    great time to look into this further. We are currently do work in the rules
    engine and while what you are reporting doesn't seem to have been reported
    before (and I haven't been able to reproduce it yet), we can look into it
    and possibly fix it in an upcoming release. I would be curious to know if
    the rule executes if you have "forced reason for change" turned off. I will
    update the relating tickets and would appreciate any more information you
    can provide on the issue you're experiencing (more detailed information
    will help us identify it more quickly and hopefully find a solution).

    In response to your question "Why is a bug that was discovered in July 2013
    (that was almost 2 (two) years ago) still not fixed. ",
    The specifically reported issue that was referenced, is highlighting that
    it is not possible to turn off Show/Hide during data entry. We don't know
    of a good use to support this.

    However; it might be useful to describe how development works at
    OpenClinica - we are an open source project which means that we foster a
    community of users and developers and we try to encourage contributions
    (including knowledge, experience, code and anything else that adds benefit
    to the community). One of the fastest ways to get something into the
    software is to contribute it! Anyone that would like to contribute
    features, functionality or fixes can open a pull request here:
    https://github.com/OpenClinica/OpenClinica . If the contribution is high
    quality and is of benefit to the community, then we will include it. Of
    course, anything that gets included goes through our SDLC which means it is
    vigorously tested and automated tests are built for it to make sure it
    doesn't break anything else and that it is part of our regular testing
    forever after. OpenClinica community belongs to everyone in it.

    How does OpenClinica, LLC decide what to contribute to the community? We
    maintain a backlog of OpenClinica features and functionality which we
    prioritize by business value. Many factors go into this - what our
    customers need / want, what the community sees as a priority, feedback that
    we get from all stakeholders. We try to work smart. This means that we try
    to tackle issues in an organized way, and not just one-off. It makes the
    most sense to tackle a set of related issues when working on that area of
    code rather than choosing at random. We also try to work strategically - we
    know that some areas of the code are better served by building a newer,
    more modern solution than maintaining more archaic systems.

    Overall we are committed to contributing to and supporting the OpenClinica
    community and appreciate everyone else that does too! A great way to get an
    issue prioritized is to get support for it by discussing it on the forums
    and seeing if it is impacting others, or potentially someone may have a fix
    or may want to help.


    Best Regards,
    Alicia





    On Mon, Jun 29, 2015 at 1:15 PM, ctrepte
    wrote:

    > Dear Thasbiha,thanks for the link which leaves only one question:
    >
    > Why is a bug that was discovered in July 2013 (that was almost 2 (two)
    > years ago) still not fixed. The newest version is 3.5. In more that 4
    > releases it was not possible to fix this? At least I did not see any
    > comment in the issue tracker that the bug was fixed in any of the releases
    > since it was discovered. As much as I like some of the new features I don't
    > think that this is how software development should work.
    >
    > Claudia
    >
    > --
    > To manage your email notifications, please visit:
    > https://www.openclinica.com/forums#/profile/preferences
    >
    > Reply to this email directly or follow the link below to check it out:
    > https://forums.openclinica.com/discussion/comment/17010#Comment_17010
    >
    >
This discussion has been closed.